09-03-2022, 05:40 AM
Well, I'm stumped on this one. Completely.
I can use "above normal sprite sheets" in battle, I can get one to not crash or go ballistic in the load/save menu (even if its not the correct sprite, still works as an unglitched place holder) not ideal, but manageable. Hell, they show up perfect in the shop screen too.
Pull up a party select screen? Well, it results in an invisible sprite... And random screen glitches on everything else. If the cursor is on that sprite the portrait, data, and everything else is loaded fine, at least when the screen stops glitching long enough to see it clearly anyway.
The save screen works because its loading from an extended OAM list out back (not the proper, vanilla OAM data). It doesn't load the sprite above vanilla, but I CAN have it display say... A ghost sprite (unglitched and correct palette) which as I said, not ideal but no crash or debilitating glitch.
The roster I can't get anything out of. It has to be looking at the vanilla OAM list, loading complete trash from beyond the list, and that's whats causing the mass graphical glitches but how to fix? I've got nothing. If I try to tell it to use the extended list it freezes as soon as it opens, no clue why. Of course that being said, if I try and point the save/load screen back to the original OAM list it freezes too.
I looked into M06's patch, which I've installed on a vanilla ROM and it works. Yet I've tried at least a half a dozen times/ways to use his code to load the party roster and such... And it always results in a complete black screen/crash as soon as any attempt to load any screen it effects is made. If it was a typo on my part pure dumb luck would have let it work by now, so I'm either missing a major part of code or it just refuses to work with all the other stuff I've got going on (which I can't find any sign where something would overlap to cause said crash). Its not recent additions that don't get along either. I tried it several times before most of that was added, same results.
At this point I'm out of ideas of what to look at. I can't even figure out a way to bypass it even. While it might not crash entirely as is, its pretty trash to even attempt to ignore.
In other words, I'm open to suggestions of any kind.
I can use "above normal sprite sheets" in battle, I can get one to not crash or go ballistic in the load/save menu (even if its not the correct sprite, still works as an unglitched place holder) not ideal, but manageable. Hell, they show up perfect in the shop screen too.
Pull up a party select screen? Well, it results in an invisible sprite... And random screen glitches on everything else. If the cursor is on that sprite the portrait, data, and everything else is loaded fine, at least when the screen stops glitching long enough to see it clearly anyway.
The save screen works because its loading from an extended OAM list out back (not the proper, vanilla OAM data). It doesn't load the sprite above vanilla, but I CAN have it display say... A ghost sprite (unglitched and correct palette) which as I said, not ideal but no crash or debilitating glitch.
The roster I can't get anything out of. It has to be looking at the vanilla OAM list, loading complete trash from beyond the list, and that's whats causing the mass graphical glitches but how to fix? I've got nothing. If I try to tell it to use the extended list it freezes as soon as it opens, no clue why. Of course that being said, if I try and point the save/load screen back to the original OAM list it freezes too.
I looked into M06's patch, which I've installed on a vanilla ROM and it works. Yet I've tried at least a half a dozen times/ways to use his code to load the party roster and such... And it always results in a complete black screen/crash as soon as any attempt to load any screen it effects is made. If it was a typo on my part pure dumb luck would have let it work by now, so I'm either missing a major part of code or it just refuses to work with all the other stuff I've got going on (which I can't find any sign where something would overlap to cause said crash). Its not recent additions that don't get along either. I tried it several times before most of that was added, same results.
At this point I'm out of ideas of what to look at. I can't even figure out a way to bypass it even. While it might not crash entirely as is, its pretty trash to even attempt to ignore.
In other words, I'm open to suggestions of any kind.
The only true wisdom is knowing you know nothing.