---- Reported by yug 2006-12-15 16:48:32 ----
Ok, this is completely insane. Please believe me anyway.
I have a simple program which draws two triangles using jogl.
Triangle A uses gl.glColor3d(0.9, 1.0, 0);
Triangle B uses a glsl shader.
Triangle B's fragment shader looks like this:
When I run the program normally, both triangles are yellow.
If I run it with javaws, triangle B (the glsl triangle) is green!
In fact, every color value < 1.0 (in the fragment shader !!) is treated as 0.0
when I run the application with javaws.
I could track the problem back to
GtkLookAndFeel.initialize() which is called by javaws.
When I add new GtkLookAndFeel().initialize() as the first line of my
application, triangle B is also green when I run it directly with java (without
javaws). Reverting to MetalLookAndFeel does not help.
How the hell can GtkLookAndFeel break a glsl shader???
jdk 1.6.0-b105 linux i386
---- Additional Comments From yug 2006-12-15 17:37:18 ----
UNIXToolkit.checkGTK() seems to be sufficient to mess the colors up
---- Additional Comments From kbr 2006-12-23 07:19:07 ----
That's pretty weird. I haven't had time to test this yet but I strongly suspect
this is a bug in ATI's Linux graphics drivers. I don't think it can be anything
else since I doubt either the JDK or Gtk use OpenGL at all in the default case,
and even if they were, JOGL uses its own independent GLContext which should not
be able to interfere with any other one and vice versa.
I strongly recommend you put up a Java Web Startable test case and file a bug
with ATI. I may be able to get you into the ATI Linux beta program to file these
bugs more directly; please contact me via email if you'd like to try to join it.
---- Additional Comments From kbr 2008-03-30 16:41:10 ----
This bug has been sitting around for a while with no action. Since I can't
believe JOGL is responsible for this in any way I'm closing it as invalid.
--- Bug imported by firstname.lastname@example.org 2010-03-24 07:49 EDT ---
This bug was previously known as _bug_ 258 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=258