Monster graphical glitch (adventure 4.5.9)

I have monsters in my game that are suddenly loading in random graphics on certain action steps, when they haven't had any issues previously throughout months of development. For example, it is even happening to a monster that has no animation.

Perhaps if I can isolate the code that loads in graphics for a new action step I could understand the issue better, but I'm really at a loss for the moment.

I have attached a zip of a 10-second movie that shows a skull that bounces around diagonally (like the ones in zelda 2), but it displays the issue described above.

This is an issue for a game that is near completion aside from adding graphics and sound, so any help would be greatly appreciated.
 

Attachments

  • Mesen - game 2023-01-06 22-02-16.zip
    1.9 MB · Views: 1

dale_coop

Moderator
Staff member
Make sure all your animations used for an animation type have the same frame count.
For example, for your "Idle" animation type, if your "idle left" animation is 2 frames, make sure the other ones "idle right", ... "idle down" are 2 frame animations too.
For your "walk" animation type; if your "walk left" is 4 frames, make sure the other "walk ..." animations are 4 frames too.
ETC...

Also, of course, make sure to assign correctly the "idle left", "idle right", "idle top", "idle down" to your "Idle" animation type (for all the corresponding directions) in the Object details dialog.
 
Thanks for the reply Dale.
I just noticed something, the bug only occurs in Mesen.exe
But if I load the game in RetroArch using the Mesen core it is also fine.
Could I possibly have enabled a setting in Mesen that is causing such a bug?
 

dale_coop

Moderator
Staff member
hmmm... not sure.
You could also delete your "Saves" subfolder in Mesen folder and see if it works better (I often have graphical glitches to Mesen auto/loading memory saves)
 
I think you might have successfully isolated the issue Dale, thank you very much!
I also received advice from TakuikaNinja on the Discord programming help thread suggesting that I should disable "automatically load IPS/BPS patches" in Mesen preferences, so that might be a way of preventing this issue from occurring in the first place - just thought I'd add that info here in case anyone else encounters the issue and stumbles across this. TakuikaNinja also noted that "mapper 30 saving is handled as IPS patches, much like FDS games", so that's probably worth noting as well.
 
Top Bottom