Reply – Re: How to run Java 3D 1.6 under old Intel processors with integrated graphics?
Your Name
Subject
Message
or Cancel
In Reply To
Re: How to run Java 3D 1.6 under old Intel processors with integrated graphics?
— by gouessej gouessej
Hey

babor wrote
I must say I exactly understand what Manu has in his mind...
I don't use telepathy yet, sorry.

babor wrote
As you may remember we're developing VisNow (http://visnow.icm.edu.pl) which is Java3D based application, and are struggling with all the same problems and many more
To make the story short - VisNow is still distributed with Java3D 1.5.2 (except MacOS) and running on native OpenGL pipeline as we cannot ultimately migrate to 1.6 or 1.7 due to a number of problems. To keep with the topic, on integrated Intel graphics we also have problems with inverted z-buffering in some cases of triangulated surfaces or surface+line objects. On Windows 10 + Intel (e.g. HD4000) it makes VisNow + Java3D 1.6 practically unusable. On MacOS (e.g. Intel Iris Plus 640) it behaves a bit differently and may be acceptable with known bugs.
On the other hand I still cannot force VisNow to run at all with Java3D 1.7-pre1 on all platforms but MacOS .
JogAmp APIs aren't to blame, we're not responsible for Intel's debatable choices and sometimes you have to tell your end users that they should use some hardware with more professional driver support. We spent several months in looking for some workarounds for the problem with some Intel GPUs no longer working under Windows 10 despite the fact that it's not caused by a bug in our APIs, we can't do more. We aren't responsible for driver bugs. Sometimes we succeed in writing some renderer quirks. We aren't responsible for your technical choices, I already wrote that Java Webstart doesn't help to work around some limitations and bugs.

Moreover, switching from Java3D 1.6 to Java3D 1.7 only requires to update the package names in your code, it's not an unachievable change.

Finally, I cannot fix bugs that aren't in our APIs and bugs that nobody reports. "we cannot ultimately migrate to 1.6 or 1.7 due to a number of problems" doesn't help at all and I still highly discourage the use of Java3D 1.5. Several contributors have worked in fixing bugs, sticking to Java3D 1.5 only to go on supporting a very few Intel GPUs or deprecated Java versions is a nonsense.
Julien Gouesse | Personal blog | Website