GPU: Handle bad fog params as large signed vals #11380
Merged
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.
From tests, it seems they're just treated as valid exponents.
Using 65535 since that's the range of depth, can't think of a game using a larger value for a fog parameter, probably never even this large.
Did some more fog tests, I think I had a mistake before when I thought softgpu fog was reversed - but since I was there, I validated how inf/nan behave. It seems like they act just like vfpu min/max - the exponent is just not treated as special.
This could use validation against MediEvil and any other affected games, though. But this matches tests.
-[Unknown]