high bit (0x1000) in bsNumUvSets is lost #20
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.
Loading Skyrim version of NIF initializes bsNumUvSets but not numUvSets from older versions. But re-calculating bsNumUvSets in NiGeometryData::bsNumUvSetsCalc() used numUvSets only for calculating high bit. This works well for loading old style NIF and save them with new version but not when loading and saving new style.
Added bsNumUvSets in NiGeometryData::bsNumUvSetsCalc() instead of initializing numUvSets with unknown data in read().