-
-
Notifications
You must be signed in to change notification settings - Fork 3
Description
I think it might be beyond me to find all the bugs. But we'll see with dev tools in ffnx I might be able to atleast jump to each field and see. There are times when the combined output hides tiles. This might be fine because the game does that. There are even times where the game never uses various tiles. That's why I think we need to look in game to see if there are problems before we panic.
We could also generate swizzle all as one image from multiple inputs and check the resulting outputs with some kinda test to check if the images are different.
Don't forget to push the FFNx button before outputting textures.
Okay we can focus on specific known texture differences.
- Input
.mim - Output
deswizzle,swizzle, orswizzle as one image - Input
.mim,deswizzle,swizzle, orswizzle as one image - Output
.toml full filename textures - Input
.toml full filename textures - Output
deswizzle,swizzle, orswizzle as one image - Use Beyond Compare to check for differences in output where Output type == Output type. Or write my own test.
I'd like to output in swizzle as one image so we can test in FFNx easy.
Though deswizzle is more human understandable. So maybe output both of those.
@AxlRose-RX Was saying there are like 126 images that are different post combine and separation. So we need to check those fields in game to see if it breaks anything. Else we need to maybe adjust the deswizzle.toml or adjust the separation algorithm.
