Project

General

Profile

Emulator Issues #9749

After upgrading to Dolphin 5.0, all games show a black screen only

Added by ajburley over 3 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Multiple games. Games tested include:
Mario Party 4
Mario Party 6
F-Zero GX
The Wind Waker
F1 2002

Game ID? (right click the game in the game list, properties, info tab)

Multiple games. Games tested include:
GMPP01 (Mario Party 4)
GP6P01 (Mario Party 6)
GFZE01 (F-Zero GX)
GZLP01 (The Wind Waker)
GF2E69 (F1 2002)

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

Multiple games. Games tested include:
ed604c3a345138ac84ea809fb023a73f (Mario Party 4)
e4015f1a9f6259528773e5235c8bec63 (Mario Party 6)
b3e4932731c63b98f0617e6764cc364d (F-Zero GX)
9841cc876fb7be6c61ead51deeabf280 (The Wind Waker)
aa748e8e0a8c91bb3635889d95f3243e (F1 2002)

What's the problem? Describe what went wrong.

After booting the game, no graphics are loaded; instead a single colour screen flashes up (for anything between about a quarter of a second and 3-4 seconds) and then a black screen is shown. I can hear the initial audio which the game plays immediately after booting, but see nothing on the screen. This happens in both windowed and full screen modes.

What steps will reproduce the problem?

  1. Double click a game to load it.
  2. Wait for a few seconds.

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?

3.0 - works fine
4.0.2 - works fine
5.0 release - does not work
5.0-419 - does not work

What are your PC specifications? (CPU, GPU, Operating System, more)

Dell XPS L702X
CPU: Intel Core i7-2820QM
GPU: NVidia GeForce GT 555M/PCIe/SSE2, 4.4.0
RAM: 6GB
OS: Windows 7 Ultimate SP1 (64-bit)

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

Example - Mario Party 6 on Dolphin 5.0-419:

57:01:348 ConfigManager.cpp:73 N[BOOT]: Saving settings to C:/Users/Adam/Documents/Dolphin Emulator/Config/Dolphin.ini
57:01:510 Boot\Boot.cpp:249 N[BOOT]: Booting D:\Programs\Games\Platforms\Gamecube\GCMs/MarioParty6.gcm
57:01:523 HLE\HLE_OS.cpp:46 N[OSREPORT]: 81200508->81300000|
Apploader Initialized.
57:01:523 HLE\HLE_OS.cpp:46 N[OSREPORT]: 81200524->81300000| This Apploader built May 21 2004 10:12:56
57:01:894 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - EXI release build: Apr 5 2004 04:14:14 (0x2301) >>
57:01:894 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - SI release build: Apr 5 2004 04:14:16 (0x2301) >>
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]:
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Dolphin OS
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Kernel built : May 21 2004 09:28:09
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Console Type : Development HW3 (10000006)
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Memory 24 MB
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Arena : 0x802f29a0 - 0x817f5fa0
57:01:897 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - OS release build: May 21 2004 09:28:09 (0x2301) >>
57:01:907 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - DVD release build: Apr 5 2004 04:14:51 (0x2301) >>
57:01:909 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - VI release build: Apr 7 2004 04:13:59 (0x2301) >>
57:01:909 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - PAD release build: Apr 5 2004 04:14:49 (0x2301) >>
57:01:913 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - GX release build: Apr 5 2004 04:14:28 (0x2301) >>
57:01:955 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: HuMem> left memory space 165KB(169248)
57:02:001 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - AR release build: Apr 5 2004 04:15:03 (0x2301) >>
57:02:001 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - ARQ release build: Apr 5 2004 04:15:04 (0x2301) >>
57:02:172 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - AI release build: Apr 5 2004 04:15:02 (0x2301) >>
57:02:174 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - DSP release build: Apr 5 2004 04:15:32 (0x2301) >>
57:02:183 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: << Dolphin SDK - CARD release build: Apr 5 2004 04:15:35 (0x2301) >>
57:02:217 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: DLL DBG OUT
57:02:218 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objman>Call New Ovl 1(1)
57:02:230 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: VI_FIELD_BELOW
57:02:250 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Dec 16 2004 EUROPE Mode
57:02:270 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ++++++++++++++++++++ Start New OVL 1 (EVT:0 STAT:0x00000000) ++++++++++++++++++
57:02:270 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objman>Init esp
57:02:270 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objman>Call objectsetup
57:02:270 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: DLLStart 1 0
57:02:270 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Search:dll/bootdll.rel
57:02:271 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objdll>Link DLL:dll/bootdll.rel
57:02:272 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Rest Memory 500000
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ===== DLL Module Info dump ====
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ID:0x00000001
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: LinkPrev:0x00000000
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: LinkNext:0x00000000
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Section num:19
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: Section info tbl ofst:0x805059ec
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: nameOffset:0x00000000
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: nameSize:48
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: version:0x00000003
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ===============================
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ==== DLL Module Header dump ====
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: bss Size:0x00000236
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: rel Offset:0x80543bbc
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: imp Offset:0x80543bac
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: prolog Section:1
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: epilog Section:1
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: unresolved Section:0
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: prolog func:0x80505a84
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: epilog func:0x80505ad8
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: unresolved func:0x00000000
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ================================
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objdll>LinkOK 805059a0 8054a3c0
57:02:421 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objdll> dll/bootdll.rel prolog start
57:02:422 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: ******* Boot ObjectSetup *********
57:02:422 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objman>InitObjMan start
57:02:422 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objman>InitObjMan end
57:02:424 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objdll> dll/bootdll.rel prolog end
57:02:424 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: objman>ObjectSetup end
57:02:430 HW\EXI_DeviceIPL.cpp:343 N[OSREPORT]: DLL DBG OUT

Any other files are available on request.

History

#1 Updated by phire over 3 years ago

Sometimes settings from 4.0 get stuck and cause issues with 5.0.

Could you try renaming the C:/Users/Adam/Documents/Dolphin Emulator/Config/ folder?
This will force dolphin to recreate it and revert to the default settings.

#2 Updated by ajburley over 3 years ago

phire wrote:

Sometimes settings from 4.0 get stuck and cause issues with 5.0.

Could you try renaming the C:/Users/Adam/Documents/Dolphin Emulator/Config/ folder?
This will force dolphin to recreate it and revert to the default settings.

Okay I have done this - but it did not make any difference. More specifically I followed the below steps:
1. Delete Config folder
2. Open Dolphin 5.0 release
3. Accept usage statistics dialog
4. Config -> Paths -> set ISO path
5. Double click any game
6. Wait for a few seconds
7. Close Dolphin
8. Delete Config folder
9. Open Dolphin 5.0-419
10. Perform steps 3-7 again

#3 Updated by phire over 3 years ago

Thanks for testing that. Can you also:

  • Try the DirectX 11 video backend (We default to OpenGL, I'm not sure what you were using in your first tests)
  • Make sure your graphics drivers are updated.
  • Looks like an Optimus laptop, From the nvidia control panel, try forcing Dolphin to use each of the GPUs.

This should narrow things down.

#4 Updated by ajburley over 3 years ago

Hi,

  • Yes I was using OpenGL for my first test
  • When I try to switch to Direct3D 11, I get an error "Failed to load D3DCompiler_42.dll, update your DX11 runtime, please". However I am already running DirectX 11.1, which is the latest version available for Win7 SP1
  • Software Renderer can display the graphics (very slowly!)
  • I switched between integrated graphics and Nvidia graphics in the Nvidia Control Panel (Global settings, which are not overridden for Dolphin), but neither option worked with OpenGL in Dolphin
  • My graphics drivers are already on the latest version (checked this through Nvidia Control Panel -> Help -> Updates)

#5 Updated by JMC4789 over 3 years ago

Sounds like there's something seriously wrong with your setup. Those D3D errors shouldn't be happening.

#6 Updated by phire over 3 years ago

If you go back to 4.0, does it work on the DirectX 11 and OpenGL backends?

I wonder if dolphin was only working through the DirectX 9 backend and broke when we removed that.

#7 Updated by ajburley over 3 years ago

Yes, on 4.0.2 it works on both Direct3D 11 and OpenGL. I never knew Dolphin even supported Direct3D before... However I just tested (by deleting the config folder and then running Dolphin 4.0.2 and setting the graphics to Direct3D 11) and it works in Dolphin 4.0.2.

DXDIAG does not show any errors and does show that DirectX 11 is installed. I even tried downloading the DirectX 11.1 update directly (Windows6.1-KB2670838-x64.msu) and running it, but I got a message that this update is already installed. And the fact that Direct3D 11 works on Dolphin 4.0.2 leads me to think there is nothing actually wrong with my DirectX 11 installation...

Anyway I guess the issues I am having with DirectX on Dolphin 5 are probably a separate issue that may or may not be related. This issue was trying to see why Dolphin OGL graphics are working on 4.0.2 and not on 5.x...

#8 Updated by phire over 3 years ago

So let's set aside driver issues for now. Can you use the bisection tool to find out exactly what commit the problems started. Start at 4.0.2 and bisect though to 4.0-9511 (which is the last development release before 5.0 and basically identical)

https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds

#9 Updated by ajburley over 3 years ago

Are you sure that the Dolphin Bisect Tool is actually working? Every build it downloads, including 9510 and 9511, is marked as "4.0.2" in the title bar and in the Help->About is listed as commit ...c3d4f from November 2013. I feel that DBT is downloading the stable 4.0.2 every time, despite the build it "thinks" it's downloading.

I also reported the (DBT) issue here: https://github.com/Helios747/DolphinBisectTool/issues/6

I was not able to reproduce the (Dolphin) issue on any of these "builds".

#10 Updated by ajburley over 3 years ago

PS: I did some more debugging on the DBT issue to narrow down the root cause. Posted my findings at https://github.com/Helios747/DolphinBisectTool/issues/6

Once DBT gets fixed, I will use DBT to narrow down the Dolphin issue!!

#11 Updated by ajburley over 3 years ago

Hi,

I managed to get DBT fixed via a PR which I submitted :) and ran it to determine when the issues started occurring.

It seems that the Direct3D issue and OpenGL issue are unrelated as they appeared in different versions. Not sure if I should create a separate issue item on your tracker for the Direct3D issue, as this item was initially just about the OpenGL issue.

The Direct3D issue appeared between builds 4.0-298 and 4.0-299

The OpenGL issue appeared between builds 4.0-722 and 4.0-732

Thanks!

#12 Updated by ajburley over 3 years ago

Hi, can I get an update on this issue? In particular:

  • "Not sure if I should create a separate issue item on your tracker for the Direct3D issue, as this item was initially just about the OpenGL issue?"
  • Have either of the issues received a known fix?
  • Any update on the investigation into the OpenGL issue itself?

I'm confused because - from my investigation - the only changes between the noted releases seem to relate to the Android version, but I am running the Windows version.

#13 Updated by ajburley about 3 years ago

Hi, is there any update? I have not heard anything for more than 6 months and I just tried the latest build of Dolphin (5.0-2981) and it has exactly the same issue.

Also, I still haven't heard back on whether I should raise a separate item about the Direct3D issue?

#14 Updated by JMC4789 over 2 years ago

The issue tracker gets flooded a lot so it's hard to keep track of everything, especially in issues where we have no idea what's going on and have no idea how to even fix it....

The bisects don't point to anything all that interesting, and no one I know can reproduce this behavior, thus... it's sat untouched in limbo.

#15 Updated by ajburley over 2 years ago

Hi JMC4789,

Thanks for responding. I'm sorry to hear that you are struggling to keep track of things. Is there any other place I should ping you to prompt you to respond to this issue if I am waiting for your response?

Specifically I have been waiting to hear if I should raise a separate ticket for the D3D issue or keep it here?

For OGL, I have found some interesting things about the build numbering around the builds which caused my issue. Something got messed up in the build numbering; the full details are here (see top post written by me):

https://github.com/Helios747/DolphinBisectTool/issues/10

This explains why there was nothing interesting in the bisects, because they were pointing to duplicate version numbers that actually refer to different actual commits. The bottom line is I believe my issue was actually caused by the following commit:

https://github.com/dolphin-emu/dolphin/commit/fabdd8ab39c4f88863ade9cbdbd1a56e2160dde1

This commit "removes the version check for buffer_storage on windows". A comment says "hopefully we'll never have to workaround nvidia bugs". I'm almost certain that what I am facing is precisely one of those "nvidia bugs".

Is it possible to make this version check optional by configuration?

Thanks!

Also available in: Atom PDF