Add tests for immediate prims and fog calculation #223
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See hrydgard/ppsspp#16005, hrydgard/ppsspp#16042, and hrydgard/ppsspp#15978 for some additional comments.
Using imm verts, we can specify the 8-bit fog factor directly, rather than by slope, end, and Z. So this uses that to illustrate the rounding of fog factors * color values.
Antialias is not well tested for immediates, and the "clipping mask" (at least per some JPCSP code) bits don't have a clear function. Maybe it's even for range culling somehow...
Texture UV gen hasn't really been tested either, which might somehow use the q of UVs.
-[Unknown]