Emulator Issues #11727
open
Metroid Prime (gamecube) D3D11 thermal visor is not working
0%
Description
Game Name?
Metroid Prime 1 (gamecube).
Game ID?
GM8E01
MD5 Hash?
fdfc41b8414dd7d24834c800f567c0f8
What's the problem? Describe what went wrong.
When using Thermal Visor with D3D 11 rendering game gives error (see screnshots). If you click ok, it will pop out at the very next frame again. If you choose to ignore it, the game plays fine, but there is no heatmap effect on thermal visor: hot items meant to become yellow and red, but everything is just violet or grayscale. Special objects (doors) are still highlighted. If error is not dismissed in about 10 seconds, the game have tendention to hung up for good.
Using OpenGL or Vulcan rendering fixes the problem (but for me they are unplayable for other issues).
Supposedly, it applies to X-Ray too, because they actually use the same effect. But I haven't got so far in the game yet.
What steps will reproduce the problem?
- Aquire Thermal Visor or load a save where you have it.
- Use it.
- Get an error.
Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.
Yes. Emulator version 5.0-10200. Also tested it on 10151.
Release version 5.0 works flawlessly.
If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer
https://www.dropbox.com/s/rxwog68h1we884m/Fifo%20Log.dff?dl=0
What are your PC specifications? (CPU, GPU, Operating System, more)
Intel Core i5 4210H @ 2.90GHz
NVIDIA GeForce 840M
Windows 7 x64
More specific information is applied.
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
My save.
https://www.dropbox.com/s/u5aq7duzlxgboj9/MemoryCardA.USA.raw?dl=0
Files
Updated by EasternTime over 5 years ago
It doesn't seem to be an Ubershaders issue. Error is occuring on any shaders settings.
Updated by JMC4789 over 5 years ago
- Status changed from New to Questionable
Please try updating to Windows 10, Windows 7 has incomplete D3D11 support. We rely on aspects of D3D11.2 for better emulation in the latest development builds.
Updated by JMC4789 over 5 years ago
Alternatively, can you try compiling Dolphin in visual studio, enabling validation layer in settings, reproducing the bug, and seeing if anything spits out in Visual Studio's output window? It's possible we're doing something wrong that Windows 10 supports/ignores.
Updated by EasternTime over 5 years ago
Yes, found it! Version 5.0-9633-x64 works as intended, but at the next available build, 5.0-9638-x64, you get an error like in the current version.
Updated by JMC4789 over 5 years ago
That's nice to know, it means it's likely not Windows 7 causing this.
Have you tried updating your drivers recently?
Updated by EasternTime over 5 years ago
JMC4789 wrote:
Alternatively, can you try compiling Dolphin in visual studio, enabling validation layer in settings, reproducing the bug, and seeing if anything spits out in Visual Studio's output window? It's possible we're doing something wrong that Windows 10 supports/ignores.
I'm only hello-word level programmer, but I have a copy of Microsoft Visual Studio 2017 from my university program. If you provide me with step-by-step instructions, I'll try it out.
Updated by JMC4789 over 5 years ago
Step by step instructions for compiling can be found here - https://github.com/dolphin-emu/dolphin
Updated by EasternTime over 5 years ago
JMC4789 wrote:
Have you tried updating your drivers recently?
Updated it now just to be sure. Problem still exists.
Please try updating to Windows 10
Sorry, I believe it's out of reach of my financial possibilities.
Updated by EasternTime over 5 years ago
JMC4789 wrote:
Step by step instructions for compiling can be found here - https://github.com/dolphin-emu/dolphin
Looks like my installation is faulty - I can't compile even "Hello world". Oh well.
If I really have to re-download 40 gb installer from uni network and try again - then I'll try.
Updated by Geemer over 5 years ago
- File GM8P01-1.png GM8P01-1.png added
Hi, I'd like to report that I'm affected by this issue as well.
Both on the GM8P01 PAL version (MD5: b1379c44e0ebc521e18215de3e5dbeea) as well as a randomized version based on GM8E01 (Revision 0, MD5: eeacd0ced8e2bae491eca14f141a4b7c).
When switching to either the Thermal or X-Ray visor the error from EasternTime's screenshot shows up. If you hit OK it'll play one frame and show up again. If you switch back to Combat or Scan visor the error will stop appearing once the visor effect goes away.
When moving around objects that are supposed to show a heat signature, they will instead be overlaid with whatever was on that spot of the screen when the visor was activated. In my screenshot I activated the thermal visor and then turned slightly to the right.
My basic system specs are:
Intel Core i5 3570 @ 3.4GHz
8 GB RAM
Nvidia GTX 1070
Windows 7 x64
Nvidia drivers 430.64
The issue does not occur on my anemic notebook running Windows 10 x64. Its specs are:
Intel Core i5-2430M @ 2.4GHz
8 GB RAM
Nvidia GT 540M
Windows 10 x64 (1809)
Nvidia drivers 391.35 (Latest version that still supports this chip.)
Both systems were only tested with Dolphin 5.0-10430.