Search
Members
HelpUsers browsing this thread: 1 Guest(s)
ff3se 2.12
coder
Posts: 3,970
Threads: 279 Thanks Received: 236 Thanks Given: 58 Joined: Oct 2011 Reputation: 65 Status
|
I think I found the cause of the bug, the monster GFX pointer in the GFX data only allow $3FFF8 bytes:
https://www.ff6hacking.com/wiki/doku.php...phics_data
Basically the last bit of the word is used for 3bpp, so $7FFF * 8 = $3FFF8, which seems to fit with vanilla GFX data + ~35 000 extra bytes. I'm not sure what FF3SE does, maybe the pointer overflow and go back to near 0. Anyway for more space you would need to modify FF3SE, expand of 1 byte that 5 bytes data, convert the existing data to 6 bytes and do a small ASM hack.
https://www.ff6hacking.com/wiki/doku.php...phics_data
Basically the last bit of the word is used for 3bpp, so $7FFF * 8 = $3FFF8, which seems to fit with vanilla GFX data + ~35 000 extra bytes. I'm not sure what FF3SE does, maybe the pointer overflow and go back to near 0. Anyway for more space you would need to modify FF3SE, expand of 1 byte that 5 bytes data, convert the existing data to 6 bytes and do a small ASM hack.
![[-]](https://www.ff6hacking.com/forums/ff9/collapse.png)
« Next Oldest | Next Newest »
 |
 |
|||
|
||||
 |
 |
Users browsing this thread: 1 Guest(s)
2017