search

mgba-emu / mgba

mGBA Game Boy Advance Emulator
https://mgba.io/
Mozilla Public License 2.0
5.73k stars 794 forks source link

Pokemon Emerald stopped launching (white screen bug) #3339

Open Tagger102 opened 1 week ago

Tagger102 commented 1 week ago

I've previously played Emerald with no issues but haven't launched it in a few months. I started it up to get back to my old save and now it just hangs on a white screen (specifically stuck on an indefinite white screen after the bios splash screen). The FPS counter at the top of the window still fluctuates, so the emulator itself seemingly hasn't frozen. All other games (Pokemon games and rom hacks included) start just fine.

I tried removing my save, redumping my cart, messing with the save type in Tools-> Game Overrides, and nothing has worked. I'm just at a loss as to why it would randomly stop working when there were no issues in the past and no changes to the emulator or my system since.

Tested on mGBA v0.10.3 OS: Win10 CPU: Intel i9-13900k GPU: RTX 3090 24gb

UPDATE I'm able to launch the game by setting the save type to 1mb manually, but mGBA keeps defaulting to autodetecting (even with the option unchecked) and setting it to 512kb for Emerald. How can I permanently change it to launch with 1mb for Emerald?

Squall-Leonhart commented 6 days ago

autodetect is setting 1mbit on 0.10.3 for me.

probably another weird case to attribute to faulty 13/14 gen processors.

endrift commented 6 days ago

Seriously Squall? Blaming the CPU?

Please upload the zip generated by File > Report bug. I suspect something might be wrong with the dump.

Tagger102 commented 6 days ago

Seriously Squall? Blaming the CPU?

Please upload the zip generated by File > Report bug. I suspect something might be wrong with the dump.

I can do that! It is launching correctly now though, I messed around with the order of saving the game overrides and now it actually launches as 1mb save type. I can't replicate the issue at this time, would a bug report file still show anything?

Squall-Leonhart commented 6 days ago

Seriously Squall? Blaming the CPU?

considering nothing done on the overrides persists across sessions and they are now claiming it to be working on the same dump, I'm sticking with blaming the CPU too :[

The failures cause cache and random memory corruption after all (and mgba already automatically corrects wrongly sized sav files in my testing).

The L3 on RPL is 36MB's in size, large enough to store an entire GBA game for a few cycles, and its this location that ends up deteriorated from the excessive SVID requests.

endrift commented 6 days ago

@Tagger102 Please do. It'll give me some info about the ROM in question at least.

Tagger102 commented 5 days ago

@Tagger102 Please do. It'll give me some info about the ROM in question at least.

Bug Report.zip

Hopefully this helps. Game launches properly today as well... Not sure why it wasn't defaulting to 1mb before.

endrift commented 5 days ago

Oh, you need to generate the report while the game is loaded.

Tagger102 commented 4 days ago

Oh, you need to generate the report while the game is loaded.

Apologies, new to this, Here it is! Bug Report.zip

Squall-Leonhart commented 4 days ago

1f1c08fb is one of the known trusted dumps,

would have been great to see the hash while it was white screening.