Emulator Issues #8011
HW bounding box issues (video driver crash, slowdowns)
Super Mario Galaxy
Paper Mario: The Thousand Year Door
What's the problem? Describe what went wrong in few words.
Super Mario Galaxy: Starting from Dolphin revision 4219, selecting a save file while using OpenGL will crash my video driver.
Paper Mario 2: Starting from revision 4219 for OpenGL, and revision 4555 for Direct3D, effects that use bounding box may cause the game to run slower than it does in revision 4217. This is easily noticeable with the water refraction effect in Chapter 1. Additionally, with OpenGL, attempting to stop emulation by using the close button on the game window while the slowdown is happening will freeze Dolphin.
What did you expect to happen instead?
Super Mario Galaxy: I expected that my video driver would not crash.
Paper Mario 2: I expected the game to run as fast or faster than revision 4217, seeing as the changes in question are supposed to be optimizations.
What steps will reproduce the problem?
Super Mario Galaxy:
1. Use Dolphin 4219 or above.
2. Set it to use OpenGL.
3. Start up the game.
4. At the file selection screen, pick any file (new one is fine).
5. Select "Play This File"
6. Whole screen goes black for a second, Display driver has stopped responding and recovered blah blah blah
1. Use Dolphin 4219 or above with OpenGL, or Dolphin 4555 or above with Direct3D
2. Import savegame linked in this report.
3. Start the game and load the save.
4. Go to the pipe on the right and enter it.
5. Game runs slower than it should.
Dolphin 3.5 and 3.5-367 are old versions of Dolphin that have
known issues and bugs, so don't report issues about them and test the
latest Dolphin version first.
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?
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Intel Core i7 3770 @ 3.4 GHz
8 GB Ram
AMD Radeon HD 5770
Windows 7 (x64)
Is there any other relevant information? (e.g. logs, screenshots,
Catalyst driver version: 14.12
Paper Mario savegame + Dolphin config: https://dl.dropboxusercontent.com/u/20789739/HW_bounding_box_report.zip
#3 Updated by JMC4789 about 5 years ago
- Status changed from New to Accepted
- Priority set to Urgent
- Regression set to Yes
- Relates to performance set to Yes
Basically: Certain graphics cards (namely, older ones) are having extreme issues with slowdown as of the Hardware Bounding Box merges, even compared to the software implementations being always on.
Quick solution would be to turn on Bounding Box Emulation on a per game, but we obviously don't want to do that if we don't have to.
Second solution: Make a setting somewhere for users to turn it off themselves, even if we never set it in any INI since it's heavily dependent on hardware
Third Solution: Make detection better without breaking things.
#13 Updated by shreduhsoreus about 5 years ago
I get it in all builds, but in -3659 through -4217 it's a constant 30-50% emulation speed. Prior to -3659 and in every build -4219 and later it's occasional random short slowdowns similar to microstutter, but not your typical microstutter and I don't get microstutter in any games. I stated all of this in issue 8001 and asked if it's just not fixable for me due to my video card but never got an answer.
#18 Updated by metafalica almost 5 years ago
Maybe it's better just to revert this commit?
First dropping dx9 that were fast enough to emulate any game, then x86, now making "old" graphics card users unable to play well with OpenGL above 4217.
I have Radeon HD 5750, my friend has "Radeon HD 5800 series" and emu runs crazy slow above 4217, but 100% speed with our "old graphics card" on 4217.
Those who have "new graphics card" will not even notice any difference between CPU or GPU bounding boxes, when emu run at 100% speed for "old graphics card" users without GPU bounding box stuff.
#20 Updated by skidau almost 5 years ago
rodolfo, for some people, the SW bbox is faster than the HW bbox. For others, the HW bbox is not available. And then for some, the SW bbox is slower than the HW bbox. Having an option confuses things when the emulator should be able to decide which setting is best for the user.