Posted by gouessej on Jun 25, 2013; 3:59pm
URL: https://forum.jogamp.org/Java3D-crash-intel-4000-tp4029426p4029461.html

macster110 wrote

Hi All

I have played around with the gears example I found on the jogl wiki page. It works on a windows 7 machine with ATI graphics card but crashes the jvm on my intel hd4000 computer (MS Surface Pro). The error log is in dropbox here .

Thanks. You should put that into a new bug report.

macster110 wrote

Thanks for the advice on drivers but since we're distributing a program used by a lot of people I'm reticent to ask everyone using windows 8 with an intel chipset to switch from the manufacturers drivers. If the problem was confined to a ms surface pro that would be fine but it seems to be a problem with at least a few windows 8 computers with an intel hd4000 graphics card.

Using the manufacturer drivers is the best thing to do anyway and using the latest drivers is a good practice. Encouraging your users to use obsolete or Microsoft drivers is a bad practice both in terms of security and reliability. Please consider updating your driver (at least on one machine) and confirming whether it fixes this bug.

macster110 wrote

So is there any way to fix this bug within jogl/java3d or is this an issue I need to address with Microsoft an Intel?

In my humble opinion, the root cause of this bug should be fixed in the driver itself. It is not possible to fix it in JOGL 2.0 but maybe (there is no guarantee) Sven can find a way to work around it, some similar "render quirks" have already been implemented in the past. Notice that it will be difficult without the real hardware in his hands.

However, this isn't a good solution on the long term. I don't accuse you but asking us to fix driver bugs is an easy way out to avoid asking the end users to use proper drivers. It means that Microsoft and some manufacturers will go on providing poorer drivers as time goes by and will get accustomed to see some of their bugs fixed in third party libraries and it will mean that the maintainers of these libraries will be held accountable for them. In other words, this tendency could lead to discredit OpenGL and its ecosystem, which is exactly what Microsoft wants (in order to favor Direct3D). Moreover, maybe some bugs won't have any workaround, that's why you should report this bug against your driver in priority.

Sorry to be harsh but I spent several weeks in trying to find a workaround for a bug of the Intel chipset 3000 HD under Windows for Ardor3D without having any computer under this OS and this graphics chip.