jPCT-AE - a 3d engine for Android > Bugs

difficulty targeting a 3D object with release V1.30

<< < (3/4) > >>

jaco robier:
data for all test:   
ClickX=   864   
ClickY=   164   
Camera.getPosition=(0.0,-30.0,150.0)   
   
      
results:

Interact2D.reproject2D3DWS (cam, fb, Clickx, clicky) .normalize () always return  (-0.4566984,-0.121633224,-0.8812672) in V1.29 & V1.30

      
                 V1.29                                V1.30
N° Click     CalcminDistance=               CalcminDistance=
1               "2.3096227645874023"   "2.3096227645874023" =>  it's always Ok in V1.30 when first click !!
2               "2.3096227645874023"   "9.99999995904E11" :o => Second click and the next click are bad in V1.30
3               "2.3096227645874023"   "9.99999995904E11" :o
4               "2.3096227645874023"   "9.99999995904E11" :o
5               "2.3096227645874023"   "9.99999995904E11" :o
6               "2.3096227645874023"   "9.99999995904E11" :o
7               "2.3096227645874023"   "9.99999995904E11" :o
8               "2.3096227645874023"   "9.99999995904E11" :o

EgonOlsen:
Now it's getting really strange...and this happens on Samsung S4 Mini only or on all devices?

EgonOlsen:
Ok...I've triple checked all my changes between the versions and this behaviour makes no f!"/("/()'##ing sense. Can you please try this jar (it reverts the float->double changes): http://jpct.de/download/tmp/jpct_ae.jar. If that doesn't help, than I don't know what will. However, even if it does, it's not a proper solution. In addition, please try this one as well: http://jpct.de/download/tmp/2/jpct_ae.jar

jaco robier:

I see this problem only on my Samsung S4 Mini. And I see no problem in v1.30 on my second SmartPhone Samsung J5.


I tried your new  Jar V1.31  from http://jpct.de/download/tmp/jpct_ae.jar
and .... it's work fine on all my device  ;D


I tested too your jar from http://jpct.de/download/tmp/2/jpct_ae.jar and it does not work.

thank you for your help!

EgonOlsen:
So, it's obviously an issue with the double/float stuff. I really think that this is actually a bug in the VM or, more likely, in the JIT compiler (because it works fine in the first iteration). I'm not sure how to counter this...the version that you are using now reverts back to float, which actually isn't what I want to do. I might make this optional, so that you can revert to the old behaviour (that works for you) by setting a Config switch.
I'll report back later...

Navigation

[0] Message Index

[#] Next page

[*] Previous page