Posted by gouessej on May 17, 2016; 3:00pm
URL: https://forum.jogamp.org/Ardor3d-JogAmp-Performance-issue-under-Ubuntu-tp4036694p4036710.html

Hi

Stefan wrote

Perhaps the difference between Windows and Linux has to do with the Nvidia Optimus support by the NVidia drivers.

This is the most important information. Optimus is NOT supported by JogAmp and by numerous similar APIs. It's possible to use NV GPU affinity in C to force a software to use a particular GPU but it's not supported in JOGL and anyway, Optimus is a huge source of trouble as it allows a program that starts by using a GPU to switch to another one at runtime whereas almost no program is designed to support such changes as it would be like starting by running a Ferrari Testarosa and ending with a Trabi. Nothing will be done to support Optimus.

You can simply call your own redraw mechanism (or directly FrameHandler.updateFrame()) in your event listeners, it's not up to JogAmp's Ardor3D Continuation to do it for you.

When Optimus switches to the Intel GPU, don't expect good performance especially on large meshes.