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

Image extract error #248

Open
dbdbdee opened this issue Jul 30, 2024 · 2 comments
Open

Image extract error #248

dbdbdee opened this issue Jul 30, 2024 · 2 comments

Comments

@dbdbdee
Copy link

dbdbdee commented Jul 30, 2024

Hello, thank you for the excellent library. I've encountered an issue while extracting images. I was trying to export attack1 from 8141000.img in Mob.wz. However, I noticed that images from a different path are being extracted instead of the attack1 images.

It seems that when extracting "attack1", images from the "stand" path in the same directory are being overwritten. For example, if "attack1" has images labeled 1, 2, 3, 4, 5, 6, 7, 8, 9..., the images corresponding to 0, 1, 2, 3, 4, and 5 are actually the "stand" images.

Extracting one frame at a time manually works fine. However, the error occurs when attempting to extract "8141000.img" or "attack1" in its entirety.

@dbdbdee
Copy link
Author

dbdbdee commented Jul 30, 2024

1

Original Image

attack1 0
Resulting Image

@lastbattle
Copy link
Owner

lastbattle commented Nov 9, 2024

image
It looks fine in my test by selecting both "stand" and "attack" property for extraction, I could not replicate that.
The latest version attaches the property name within the image file name.

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