Textures: Hardcode resolutions and formats + generate wxHexEditor tagfile #16
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
JayFoxRox
commented
May 3, 2018
| b_size = c - b | ||
| print("Section-b: %d bytes" % (b_size)) | ||
| assert((b_size == 32) or (b_size == 512)) | ||
| #FIXME: Fix this codepath |
There was a problem hiding this comment.
Comment should be removed
JayFoxRox
commented
May 3, 2018
|
|
||
| if b == 0: | ||
| if length == 128: | ||
| if length == 32: |
There was a problem hiding this comment.
There should be a comment which states that this is trying to guess texture resolution / format
|
I've moved the texture names to https://github.com/OpenSWE1R/openswe1r/wiki/List-of-Textures |
|
Closing PR. wxHexEditor changes will be migrated another time. |
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.
I've added a lot of experimental code, most of which is broken.
This adds a tag exporter for wxHexEditor so we can see where / how information could be stored.
However, to me, it appears as the texture information (resolution / format / filters) must be stored elsewhere.
So likely in the modelblock or the games binary.Mostly in modelblock. See #17I've also started to hardcoded texture information so the textures can actually be exported. Ideally someone will translate this into adict, including the text-comments about the texture contents.See comment below.
Many of these textures don't export correctly because the purpose of the "b" section is still unknown.It appears that these textures use some palette, but I was unable to locate it / figure out how to use it.
The
bsection is the palette. But my code was buggy asbreferred to the palette section offset, but also the blue color channel. So the code was/is producing garbage results.