Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the issue about multiple image import #4

Closed
fejich opened this issue Sep 6, 2017 · 3 comments
Closed

the issue about multiple image import #4

fejich opened this issue Sep 6, 2017 · 3 comments

Comments

@fejich
Copy link

fejich commented Sep 6, 2017

I am currently working on "Mario Vs. Donkey Kong: Tipping Stars" in the Chinese Localization

This game has a lot of gtx files containing multiple images,export the file is normal.
There are some gtx files even beyond the TexConv2.exe can only import 64 pictures of the restrictions, there are 153 pictures in the inside.

But,when I edit the dds file, use the -multi option to import the file
Everything looks normal, but I cover it back after the game. Picture position only blank

Can you help me to see what is going on?

**I uploaded files to Google Drive:**https://drive.google.com/open?id=0B6rm6RJxJJ4ORTUxbDkxVXFtN3M

Have time to hope that you can analyze what is the problem somewhere. Thank you

@aboood40091
Copy link
Owner

Hmm, sadly, I think I can't help you with this one. Sorry.

@fejich
Copy link
Author

fejich commented Sep 7, 2017

This morning I observed that the TexConv2.exe generated contains multiple images gtx file

I used HxD.exe observation to find the law, TexConv2.exe just a number of dds → gtx data one by one paste in the same file inside.

So I divided the 153 dds files into three groups

  • 0-63
  • 64-127
  • 128-152

Generate three gtx files, and then manually copy the need to use data, this approach is successful!

Problem fixed :)

PS: GTX-Extractor generated gtx file with TexConv2 generated file is a little bit different, it may be the reason that the game can not be properly identified

@fejich fejich closed this as completed Sep 7, 2017
@aboood40091
Copy link
Owner

Huh.

Nah, it can't be the problem. I think the problem is something else.

aboood40091 added a commit that referenced this issue Jun 15, 2018
* Use "bytearray" instead "unsigned char *" in AddrLib to prevent data
corruption
* Fix aligning data (fixes issue #4)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants