Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jaco robier

Pages: [1]
1
Support / Re: Crash (native)
« on: September 27, 2018, 09:37:19 pm »
Me too, I sometimes had the crash error :
"GC_FOR_ALLOC freed 1030K, 10% free 38859K/42784K, paused 5ms, total 5ms
Fatal signal 11 (SIGSEGV) at 0x97319048 (code = 2), thread 1217 (otic.industrial)".
it was sometimes at the start of my app when I loaded a file "factory.SER".

Since then I used another 3D software to convert and generate "factory.obj" file and started serialization again. it fix this problem and i do not understand why my old "factory.obj" file was bad ? serialization issue ?  format Wavefront .obj incompatible ?

2
Bugs / Re: Points are always microscopic in OpenGL 2
« on: January 09, 2018, 06:43:44 pm »
Yesterday I tested your version 1.32 on my Genymotion emulator on PC. :o

today, I test on my Samsung tablet and it works.


It's solved with your version 1.32
thank you very much.

3
Bugs / Re: Points are always microscopic in OpenGL 2
« on: January 08, 2018, 05:47:05 pm »
I tried your version 1.32 and I saw no difference : the points must measure 1 pixel.

What is surprising is that the thickness of the lines work fine in OpenGL1 and OpengGL2 with JPCT version 1.31, when i use  Polyline1.setPointMode(False)


4
Bugs / Points are always microscopic in OpenGL 2
« on: January 07, 2018, 10:38:41 am »
Hello,
I use the class PolyLine and i have problem with the method SetWidth in mode Point in OpenGL 2

   mGLView.setEGLContextClientVersion(1); //  OpenGL 1
   ...;
   Polyline1.setPointMode(True); // mode point
   polyline1.setWidth(35);
=> the width of the point is correct.


   mGLView.setEGLContextClientVersion(2); //  OpenGL 2
   ...;
   Polyline1.setPointMode(True); // mode point
   polyline1.setWidth(35);=> The Width of the point never change and are always microscopic ? see photo openGL2.jpg

thank you for your support !.


5
Bugs / Re: difficulty targeting a 3D object with release V1.30
« on: January 01, 2016, 04:21:26 pm »

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!

6
Bugs / Re: difficulty targeting a 3D object with release V1.30
« on: December 31, 2015, 06:17:38 pm »
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

7
Bugs / Re: difficulty targeting a 3D object with release V1.30
« on: December 31, 2015, 02:55:20 pm »

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

8
Bugs / Re: difficulty targeting a 3D object with release V1.30
« on: December 30, 2015, 09:03:15 pm »
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.


9
Bugs / Re: difficulty targeting a 3D object with release V1.30
« on: December 29, 2015, 11:26:59 pm »
these 2 functions are used in the render thread :
SimpleVector dir = Interact2D.reproject2D3DWS (cam, fb, Clickx, clicky) .normalize ();
float res=Cube.calcMinDistance(cam.getPosition (), dir);

and ClickX and ClickY are calculated in the touch event method/thread.

I checked the first function (Interact2D.reproject2D3DWS (cam, fb, Clickx, clicky) .normalize () by projecting a 3D ball from the click : it's seems correct ...(see picture). http://www.jpct.net/forum2/Smileys/default/huh.gif

10
Bugs / difficulty targeting a 3D object with release V1.30
« on: December 29, 2015, 08:52:00 pm »
my menus in 3D does not work with the v1.30 release:
the problem is that if you click on a 3D object, the 3D object is not selected. Sometimes it works after 3 clicks ...

I only use these 2 functions:
SimpleVector dir = Interact2D.reproject2D3DWS (cam, fb, Clickx, clicky) .normalize ();
float res=Cube.calcMinDistance(cam.getPosition (), dir);

In v1.28+v1.29 works fine: It's always return res=25 when i click on the 3D object.
in V1.30: it's return res=9.99999995904E11 when i click on the 3D object ?!?

Have you got any ideas?
Cordialy

11
Projects / This app is not written in Java !!
« on: December 14, 2015, 04:24:00 pm »
Because I'm tired of crashes in Java when my application starts:
I use Basic4android and this library http://www.b4x.com/android/forum/threads/jpct-ae-3d-engine-wrapper.29546/

Advantages:
JPCT + Basic4android: only 4 crashes !! with 23000 Download.
JPCT + Basic4android: multiThread works fine.

Disadvantage:
JPCT + Basic4android : Loss of 10% fps


12
Projects / 3D Robotics industrial
« on: September 20, 2015, 05:56:18 pm »
Hello,

This is my application https://play.google.com/store/apps/details?id=robotic.industrial for those who want to discover industrial robotics .

I program and installs industrial robots ( ABB and Universal Robots ) .So If you spend one minute on this application, you can live my job everyday...

video with 3D menus = https://www.youtube.com/watch?v=dFOYzDO9kyg

a big " Thank you" for the work of EgonOlsen  ;).


13
Bugs / PolyLine and line width
« on: July 26, 2015, 07:39:23 pm »
Hello,
I use the class PolyLine and i have problem with the method SetWidth

   Polyline1.setPointMode(True); // mode pixel
   polyline1.setWidth(35);
=> the width of the pixel is correct.


   Polyline1.setPointMode(False); // mode line
   polyline1.setWidth(35);
=> The Width of the line is incorrect: the width never change and always the line width=1 ?


Bug or Normal ?



14
Bugs / Getbounds return always 1.401298464324817E-45
« on: March 28, 2015, 05:47:23 pm »
I Tested a getBounds() method to World
array is minX, maxX, minY, maxY, minZ, maxZ.

MinX is correct
MaxX is correct
MinY is correct
MaxY is incorrect if the max.y of All objects < 0 then return always 1.401298464324817E-45 !?!
MinZ is correct
MaxZ is correct
 
Thank you for your work!
Modify message

Pages: [1]