Revert "Merge pull request #16628 from hrydgard/remove-fog-fshader-flag" #17439
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reverts commit 10dee90, reversing changes made to 34c11c8.
Changes the fog back to be controlled by a fragment shader ID bit instead of by uniforms.
While this did reduce the shader count, I should have carefully benchmarked on older mobile GPUs - while not at all on newer GPUs, on ones like Mali-400, the hit is quite noticeable.
Same with the lmode flag, so I'm gonna have to revert that too. While risky just before a point release, these changes are fairly easy to see if they break..
Then for 1.16 I'll make a "fragment ubershader" flag, so we can choose between max fragment shader performance or minimizing the shader count for less stutter. Or maybe even compile specialized shaders in the background when using the ubershader..