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

difficulty targeting a 3D object with release V1.30

<< < (2/4) > >>

jaco robier:
I  tested the menu 3D on this devices:
Genymotion with android 4.4.2 and JPCT v1.30 : It's works
Samsung S4 Mini with android 4.4.2 and JPCT v1.29: it's works
Samsung S4 Mini with android 4.4.2 and  JPCT v1.30: it's does not works  ???
Samsung J5 with android 5.1.1 and Jpct v1.30 : it's works


I tried  calcMinDistance ( cam.getPosition (), dir , 1000)" and i see no change.

EgonOlsen:
I really don't see what should cause this. It's the same calculation. As long as the VM behaves the same (which it has to), the outcome should be deterministic regardless of the device. It's just math, there's no gpu/driver specific code involved.
Just to be sure: Have you double checked that your input parameters are correct in all cases?

EgonOlsen:
Here's a version that reverts the change in the constant: http://jpct.de/download/tmp/jpct_ae.jar

Please let me know, if that changes anything or not.

jaco robier:

with this version 1.31, i see no change  ???

EgonOlsen:
I really don't know what it's supposed to be then. Can you please try this: Loop over some x,y coordinates (instead of the ones taken from the touch events), run your code on each set and see what happens...does it fail at all? If it does, does it fail for all values? If not, does it always fail for the same values or is it 'random'?

Navigation

[0] Message Index

[#] Next page

[*] Previous page