Posted by Tobi Delbruck on Feb 09, 2024; 10:21am
URL: https://forum.jogamp.org/Corrupted-frame-or-transform-Mac-OSX-OK-on-win-linux-tp4043303p4043305.html

Hi Sven,Thanks for instantaneous response. Yes, we have a discretionary budget for some critical software support. Please write me to arrange a contract.

The JOGL coding in jAER was written while we were complete novices at OpenGL and also Java and so it shows. We are completely reliant on Swing for UI interaction and make heavy use of a variety of font rendering methods.  And yes, jAER uses a mole of dependencies but it is pretty easy to setup; I could do it in 1h on a brand new Mac Mini with zero mac experience in last 20 years; the only hassle was installing homebrew to install libusb.

I currently develop jAER via single dropbox on windows/linux/mac in netbeans and that is now I made the videos that I uploaded (with VNC to the mac mini) so it is pretty easy to compare and debug.

I can try to write a standalone project that exposes this bug but that will take me a few days. Otherwise I can ask you for a recommendation: Should I change from using top level GLCanvas to using top level GLWindow? Could that possibly affect this problem? I'm totally clueless about the inner working and don't even know what NEWT stands for or what is the role of jogamp and jogl. We began with GLCanvas and it works wonderfully for us except on Mac OSX.

One more thing: This problem only seems to appear in the 2d rendering pipeline: jAER's 3d rendering of the event sensor events doesn't seem affected. Our 2d rendering pipeline uses 2D textures to render the different camera outputs (event/frames/annotation). This suggests to me that the problem might be related to our texture handling code in https://github.com/SensorsINI/jaer/blob/master/src/net/sf/jaer/graphics/ChipRendererDisplayMethodRGBA.java