Use texture information from modelblock #17
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
This was referenced May 4, 2018
JayFoxRox
force-pushed
the
tex-model-xml
branch
2 times, most recently
from
b70a222
to
5cb4de7
Compare
JayFoxRox
force-pushed
the
tex-model-xml
branch
2 times, most recently
from
e877ab5
to
2792ee6
Compare
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.
This is an alternative to #16These branches are created from the same base-version, so this file does not have all the features of the other one.I'll probably close #16 and move the wxHexEditor stuff into it's own PR.The comments about what each texture is, will be moved to a wiki or some RE article.This version of the script depends on the modelblock XML from https://github.com/Olganix/Sw_Racer
Read the information in the script.
After merge, an issue should be created about using making the texture sizes POT.
Another issue should be created about reviewing the 0x10 and 0x01 flags; those double the texture resolution. I'm not sure yet wether more content is loaded from the file or if there is just padding added in the texture. This could be important when trying to use UV coordinates or wrapping these textures.
Textures are flipped so they are no longer upside down. Closes #19
A future port of this to C++ or a port of Olganix/Sw_Racer to Python, would be a good idea, as it's hard to keep all projects (OpenSWE1R, swe1r-tools, Olganix/Sw_Racer) in synchronization, especially with those ASCII identifiers in Sw_Racer.
Also see Olganix/Sw_Racer#16 as it touches this.