Emulator Issues #7003
closed
Metroid Prime 2 Echoes - Severe refraction slowdown in torvus bog region
0%
Description
Game Name?
Metroid Prime 2 Echoes
Game ID?
G2MP01
What's the problem? Describe what went wrong in few words.
This has been posted on the wiki regarding severe refraction slowdown when water lands on the visor or coming out/entering water in first person mode. FPS bombs to around 11 FPS or worse in the Torvus Bog region.
What did you expect to happen instead?
Slick constant FPS. There's another ticket on here to address the same in MP1 Tallan Overworld region and Ridley boss fight.
What steps will reproduce the problem?
[Don't assume we have ever played the game and know any level names. Be as
specific as possible.]
- Enable OGL Backend
- Travel to the Torvus Bog Region (can provide a save file if you need it)
- Look up and around whilst it's raining, enter/exit the water in FPS mode, try battles in the area, it's unplayable.
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?
4.0.750 x64
Does using an older version of Dolphin solve your issue? If yes, which
versions of Dolphin used to work?
This is a known issue, addressed on the wiki.
What are your PC specifications? (including, but not limited to: Operating
System, CPU and GPU)
Win7 Pro SP1 x64
Intel i7 3820 LGA2011 @ 4.3GHZ
16GB DDR3 RAM
2x Nvidia GTX 680's in SLI
Are you using the 32 or the 64 bit version of Dolphin?
X64
Is there any other relevant information? (e.g. logs, screenshots,
configuration files)
[Upload big files to a hosting service and post links here!]
Captured bellow :-
http://www.youtube.com/watch?v=-mCKZ_SZOiI
[Do not attach files to this issue. Upload them to another site and
link here. Use imgur.com for images and pastie.org for logs.]
Updated by NeoBrainX over 10 years ago
- Status changed from New to Invalid
We don't accept performance issues unless they address particular issues in our code base.
Updated by NeoBrainX over 10 years ago
To be more clear here, we either need to know a specific issue pointed out with our code, i.e. an observation about slow code paths with an explanation as to why they are slow in a particular situation and a realistic fix being available.
That said, we also accept performance issue reports if there is a drastic (and unexpected) performance regression coming from a specific patch. Without knowing if the issue is such a regression and without the information of the patch which caused the regression, we cannot do anything with the report however.
Updated by havord86 over 10 years ago
This is the same bug as ticket 6687 yet that's been accepted and supposedly fixed. This bug only affects the OGL backend,
Updated by JMC4789 over 10 years ago
- Status changed from Invalid to Duplicate
duplicate. We know what happens with it, the fix was reverted.
Find one of the builds where it was fixed, then play on those builds.
Updated by havord86 over 10 years ago
Ok, just so you're aware and can reimplement in the future. Cheers guys.
Updated by JMC4789 over 10 years ago
The reason it was reverted is that it caused problems in other games. You can definitely just use an older build for just this game and get a very big speedup in areas of Metroid Prime 1/2
Updated by havord86 over 10 years ago
Ok cheers guys, I'll stick to build 315 for MP until a safer fix comes out in the future. Thanks for the assist.