Posted by gouessej on May 21, 2016; 10:16am
URL: https://forum.jogamp.org/Ardor3d-speed-jogl-vs-lwjgl-tp4036731p4036734.html

Hi

At first, keep in mind that we do our best on our spare time, we're not paid to do that. You can ask something, you cannot and mustn't demand it. The pressure is for you, not for us even though I don't want to abandon you.

JogAmp's Ardor3D Continuation is actively maintained (and supports only JOGL) whereas the legacy Ardor3D was abandoned several years ago. Your boss wants you to use an abandoned piece of software, there is no way back to the other set of bindings you mention.

Moreover, the legacy Ardor3D relied on an obsolete version of L****, it doesn't support L**** 3. If something goes wrong, you'll have to port the old semi-broken legacy version to L**** and you'll have to maintain it yourself.

Have you tried other SWT canvases provided by JogAmp's Ardor3D Continuation? com.ardor3d.framework.jogl.swt.JoglNewtSwtCanvas?

I cannot find the culprit without seeing your source code.

N.B: No, JogAmp is about 3% faster than L**** but there is probably something not working correctly elsewhere.

P.S: Please don't mention L****, this is none of my concern.