Posted by hharrison on Apr 27, 2015; 4:44pm
URL: https://forum.jogamp.org/Java3d-1-6-0-pre12-released-requires-jogl-2-3-1-tp4034327p4034385.html

Manu wrote

hharrison wrote

Java3D 1.5.2 almost certainly used the Direct3D backend in this case, not the opengl backend.

Sorry Harvey, but I don't think it's the case. First, I actually never saw the Direct3D switch work automatically, and anyway it's not even available under Windows 64 bit with which I work most of the time.


Anyway, since everybody here seems to refuse to consider this issue as a bug that could happen with other drivers, I'll stop reporting my problem here every year. Either I'll try to investigate the problem myself in Java3D, or wait for a fix in Parallels, and I'll tell you once it's fixed. Meanwhile, I'll continue to use Java3D 1.6 only under Mac OS X.

Sorry, it's been a few years and I didn't realize you were speaking of 64-bit windows.

In that case, you were/are getting the native OpenGL backend w/ Java3D 1.5.2, it was only 32-bit that defaulted to Direct3D.

I really wish we could catch this error, but that's kind of the problem with driver bugs, it just segfaults in the native bits, and there's nothing you can do to catch it on the Java side, it's vm failure time :-(

WRT OpenGL versions, I'd actually like to someday rely on having OpenGL 2.1 as the miniumum version, but I'm not going to go breaking the OpenGL 1.2/1.3/1.4 pathways without having enough time to fix things up for people, so it's very unlikely to change ever.

One exercise that would be instructive would be to read through the old OpenGL native backend for Java3D and compare the initializtion sequence vs the jogl backend, maybe there's something there that was missed when porting.


Harvey