You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per the title, glDrawBuffers is used incorrectly and has to be specified (per the literal language of the spec) every time the fbo is changed.
This is why deferred rendering doesn't function on Intel hardware (like an HD4000). ATI/nVidia treat the fbo a bit like a vao, which is not correct - drivers massaging out common errors.
The text was updated successfully, but these errors were encountered:
I checked an intel 3600 and an HD4000 in GL2. The HD4000 I also checked in GL4 (had to cheat it to create a 4.0 (GLFW) instead of a 4.3 one).
I made the necessary changes for the HD4000 to run GL4 deferred-pipeline correctly. I need to do the same changes to GL2 and check the 3600 again on it (that's a GL3 device IIRC).
Though, if newer Intels have taken the same interpretation of the specs (the language is nonsensically vague in them) as the other vendors it might make sense to only make those changes in GL2 (where the issue is more realistic) or ignore it altogether.
Per the title, glDrawBuffers is used incorrectly and has to be specified (per the literal language of the spec) every time the fbo is changed.
This is why deferred rendering doesn't function on Intel hardware (like an HD4000). ATI/nVidia treat the fbo a bit like a vao, which is not correct - drivers massaging out common errors.
The text was updated successfully, but these errors were encountered: