VideoCommon: fix regression with texture load order #12094
Merged
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
…texture code was always updating the asset map for each texture with each entry, making it so the last value actually would be loaded instead of the first
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.
A user using a dynamic input texture pack notified me to let me know that the DIT texture pack's button textures were not taking precedence over another pack. The reasoning for this is that when I switched over texture packs to use the asset loader, I accidentally updated the asset map with the latest texture asset, instead of choosing the initial value. This caused the ordering of precedence for texture packs to be reversed, which caused the issue.