You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A bug in "Rubble Saver (J).gb" causes memory corruption and also - sometimes - causes the core to stop rendering new frames. It stays black even after loading a state or hard resetting. The only way to fix it is to reboot the core.
The bug that I'm doing is basicly: using up too many object slots. The boss in Stage 6 produces new enemies and the game fails to set a limit. Memory gets used up until it runs beyond what is normal object slot memory. This is visible at around address $C500 (System Bus).
The text was updated successfully, but these errors were encountered:
Is there any way you can test this on gambatte upstream? It seems almost impossible that this isn't an upstream core bug. There's probably no way you can test it there though.
A bug in "Rubble Saver (J).gb" causes memory corruption and also - sometimes - causes the core to stop rendering new frames. It stays black even after loading a state or hard resetting. The only way to fix it is to reboot the core.
http://dehacked.2y.net/microstorage.php/info/1071068601/Rubble%20Saver%20%28Japan%292.bk2
This movie which starts from a state will cause the issue.
The bug that I'm doing is basicly: using up too many object slots. The boss in Stage 6 produces new enemies and the game fails to set a limit. Memory gets used up until it runs beyond what is normal object slot memory. This is visible at around address $C500 (System Bus).
The text was updated successfully, but these errors were encountered: