Timeline for GLSL 330 Core Bug? - Uniform variable will not set to value if it is named a certain way
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2015 at 3:29 | comment | added | Trevor Powell | Driver bugs still aren't common -- just much less absurdly rare than C compiler bugs. Suspected driver bugs still almost always turn out to have been technically-illegal OpenGL code which one vendor let you get away with and another didn't. Just not in this case. :) | |
| Jun 29, 2015 at 3:22 | comment | added | Trevor Powell | (You get the these issues using ATI's official drivers on Windows or Linux, under OpenGL. You don't seem to get them on OS X; presumably they're using entirely different codebase for their ATI drivers? Additionally, you don't get these issues on Linux if you're using the open-source community drivers instead of the official ATI ones.) | |
| Jun 29, 2015 at 3:20 | comment | added | Flafla2 | Interesting - I never knew driver bugs like this were so common. I suppose AMD's OpenGL support is a bit shoddy, and DirectX drivers are probably a bit closer to spec. | |
| Jun 29, 2015 at 3:17 | comment | added | Trevor Powell | (With that said, I've seen a lot of newly-ported-to-OpenGL games fail on certain ATI cards due to the "not retaining previously set uniform values" issue. The general wisdom is that you should remember what uniform values you last set, and not re-set them if they don't change. But on ATI cards with the official drivers, you can sometimes end up rendering using rubbish uniform values if you do that.) | |
| Jun 29, 2015 at 3:14 | comment | added | Trevor Powell | @Flafla2 C compiler bugs are very rare; you're unlikely to ever bump into one unless you're working on an unusual platform. When you suspect a C compiler bug, most people won't believe you; on balance, you're more likely to be making a silly mistake than to have found a real issue. Driver bugs around details in the OpenGL specification are much, much more common and less unbelievable. Particularly in this sort of area like "what happens with a uniform variable which the host program doesn't actually set a value for" which virtually never happen in the real world. | |
| Jun 29, 2015 at 1:35 | comment | added | Flafla2 | Dear god, this is a nightmare - it's like C programmers who find a bug in the compiler. | |
| Jun 28, 2015 at 1:04 | comment | added | Nicholas DuPlessis | Ok good, I thought I was losing my mind for a minute! Setting them from inside my program did the trick. Thanks! | |
| Jun 28, 2015 at 1:01 | comment | added | Trevor Powell | While we're here, it's worth also mentioning that the current ATI drivers for certain GPUs also don't always correctly retain uniform values when switching between current shader programs. So not only do you need to set all your shader' uniforms explicitly, you need do it it every time you switch from one shader to another. | |
| Jun 28, 2015 at 0:59 | vote | accept | Nicholas DuPlessis | ||
| Jun 28, 2015 at 0:57 | history | answered | Trevor Powell | CC BY-SA 3.0 |