Emulator Issues #10360
closed
Rock Band 3 very slow to boot and load state saves
0%
Description
Game Name?
Rock Band 3
Game ID? (right click the game in the game list, properties, info tab)
SZBE69
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
ce581cfcbf0abc535416a747e458d2fb
What's the problem? Describe what went wrong.
Game takes an unusually long time to boot and resume from pause or state load. The emulation window will simply say "Dolphin" for about 15 seconds with no apparent activity. After a few more seconds, the strap usage screen finally appears, though it can't be skipped as quickly as before. Attempting to load from a state save also takes about 10-15 seconds when it didn't use to take as long.
What steps will reproduce the problem?
Boot the game. Try to make a save state and load it.
Other tested Wii titles did not have this issue.
Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?
5.0-4484
5.0-4409
5.0-4406
The problem starts with 5.0-4409. 4406 still boots reasonably quick, and the hang is obvious with 4409.
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel Core i5 2500k
GTX 1060 6GB
Windows 10 1703
16GB DDR RAM
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
Running in portable mode seems to take care of the problem. There are cheats enabled, but disabling cheats does not solve the problem. Changing graphics backend from Vulkan and OpenGL does not make a difference. Maybe it's some other configuration?
Updated by JMC4789 over 7 years ago
It's definitely some configuration issue if setting portable mode fixes it.
What I'd do if I were you was slowly add various settings from your standard install to portable to figure out what's wrong.
Obviously, even if it is a configuration issue, making it so the game takes 15 seconds to load is something we don't want to happen. Do you have a gigantic SD card on the non-portable install?
Updated by megarockexe over 7 years ago
JMC4789 wrote:
It's definitely some configuration issue if setting portable mode fixes it.
What I'd do if I were you was slowly add various settings from your standard install to portable to figure out what's wrong.
Obviously, even if it is a configuration issue, making it so the game takes 15 seconds to load is something we don't want to happen. Do you have a gigantic SD card on the non-portable install?
No, SD card never worked for me here.
Seems to be the game's .map file in the Maps folder of Dolphin. The file is 2.16 MB though. When I remove it, it boots in a reasonable amount of time.
Updated by JMC4789 over 7 years ago
- Status changed from New to Accepted
- Regression changed from No to Yes
Accepting because that actually makes a lot of sense.
I'll try to narrow down who added that file and see how it's malfunctioning.
Updated by JosJuice over 7 years ago
Dolphin doesn't ship with a file for this game in the Maps directory, so trying to narrow down who added it doesn't seem useful.
Updated by JMC4789 over 7 years ago
We changed how the symbol maps were handled recently though?
Updated by megarockexe over 7 years ago
JosJuice wrote:
Dolphin doesn't ship with a file for this game in the Maps directory, so trying to narrow down who added it doesn't seem useful.
It doesn't ship with one, but I believe it will be 2MB if one is just generated. I need that code coloring. But mine also has some routines named.
Updated by megarockexe over 7 years ago
This issue is still happening even on 5.0-5075. Seems it has to do with a really large map file. It's not game-specific, so if any game has a large map file, booting will hang, even if not in the debugger. And this didn't used to happen with 5.0-4406.
Updated by JosJuice about 7 years ago
Can you re-test this? 5.0-5475 improved the speed of loading map files.
Updated by megarockexe about 7 years ago
JosJuice wrote:
Can you re-test this? 5.0-5475 improved the speed of loading map files.
Yup. It's fixed in that version. Looks like the same bug was stumbled upon.
Updated by JosJuice about 7 years ago
- Status changed from Accepted to Fixed
- Fixed in set to 5.0-5475