In extension GL_ARB_fragment_program, the components value of fragment.fogcoord are (f, 0, 0, 1), but Mesa assign the components value as (f, f, f, f). For example: Call glProgramStringARB with program string: "!!ARBfp1.0\nATTRIB state_param = fragment.fogcoord;\nMOV result.color, state_param;\n\nEND"; and set the fog coord as 0.6, then draw a quads, the pixel color should be (0.6, 0, 0, 1) instead of (0.6, 0.6, 0.6, 0.6);
Created attachment 9763 [details] test case
Fixed in git.
Today I wanted to verify this bug, but it still exists. Reopen it.
Which driver are you using? It works with software rendering here.
Xlib driver is OK. I use 915 and 965 driver. So change the component to DRI/I915.
fixed in mesa 7eef52e975e852207ee840c74cd822c8f8c90a01 (i915), 83068115e2104b1880431ada96fa37e632149a86 (i965)
I got pixel color (0, 0, 0, 1) when I ran the test case with i915/i965 driver and softrendering(set LIBGL_ALWAYS_INDIRECT=1). Please recheck, thanks.
(In reply to comment #7) > I got pixel color (0, 0, 0, 1) when I ran the test case with i915/i965 driver > and softrendering(set LIBGL_ALWAYS_INDIRECT=1). > Please recheck, thanks. > test case issue. please add the following line in your case. #define GL_GLEXT_PROTOTYPES or glFogCoordf is implicitly declared.
Yes, case issue. Thanks for your hint.
Mass version move, cvs -> git
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.