Project

General

Profile

Emulator Issues #12059

Netplay black screen on start with Mario Strikers Charged

Added by Joeybeta 5 months ago. Updated 18 days ago.

Status:
Accepted
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?

[Mario Strikers Charged]

Game ID? (right click the game in the game list, Properties, Info tab)

[R4QE01]

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

[8b0cd728c698950b09e4e0731f2b5969]

What's the problem? Describe what went wrong.

[Netplay session starts and stays with a Black Screen, with or without another person, no further progression. Happens with both the wbfs and ISO. Game will run perfectly fine locally.]

What steps will reproduce the problem?

[I've tried various property settings for the game itself with no luck. Disabling dual core does not work. Trying netplay alone does not work either.]

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

[5.0-11863]

Is the issue present in the latest stable version?

[Yes and 5.0 (It would not have supported Wiimote controls if it booted through netplay anyways)]

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

[First found out in a version last updated about a couple weeks ago]

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

[Not a graphical issue to my knowledge]

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

[CPU: Ryzen 5 3600, GPU: MSI GTX 1660, OS: Windows 10, RAM:16GB DDR4]

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

[Nothing ever gets logged when attempting to load. Other Wii titles I've attempted that starts on netplay just fine to my knowledge are Fortune Street and Sonic Riders Zero Gravity. Screen shot is basically how it's stuck like when attempting to run a netplay session with this game. My personal known workaround is running the Wii system menu through netplay and selecting Mario Strikers Charged as the default ISO to load from the menu with, which was more steps than i thought it would be]

dolphin netplay black screen.PNG (34.3 KB) dolphin netplay black screen.PNG Joeybeta, 04/19/2020 02:31 AM
dolphin close confirm.PNG (4.33 KB) dolphin close confirm.PNG Will appear trying to end the emulation a 2nd time when the first time didn't work. Joeybeta, 04/19/2020 02:44 AM
dolphin controller windows.PNG (52.7 KB) dolphin controller windows.PNG Joeybeta, 04/19/2020 04:11 AM
dolphin controller windows.PNG (52.7 KB) dolphin controller windows.PNG Joeybeta, 04/19/2020 04:32 AM
dolphin msc got this far with 4.0-6286.PNG (142 KB) dolphin msc got this far with 4.0-6286.PNG Joeybeta, 04/19/2020 04:59 AM
Log.PNG (162 KB) Log.PNG Joeybeta, 04/20/2020 01:15 AM
7746
7747
7748
7749
7750
7752

History

#1 Updated by Billiard26 5 months ago

  • Status changed from New to Questionable

It sounds like your Wii remotes are not assigned.
Show a screenshot of your "Controllers" dialog and your "Assign Controllers" NetPlay dialog.

#2 Updated by JMC4789 5 months ago

Can confirm it's not starting in Single Core. Can you bisect? Even if you use GC controllers just to see if it boots in older builds, it'll be enough to see what's going on.

#3 Updated by Joeybeta 5 months ago

7748

Billiard26 wrote:

It sounds like your Wii remotes are not assigned.
Show a screenshot of your "Controllers" dialog and your "Assign Controllers" NetPlay dialog.

Here's what I got for what shown in both my assign window and controller settings window. These work fine booting w/ fortune street

#4 Updated by JMC4789 5 months ago

Yeah, it's not related to Wii Remotes. It's getting stuck super early into initialization.

#5 Updated by Joeybeta 5 months ago

7749

Billiard26 wrote:

It sounds like your Wii remotes are not assigned.
Show a screenshot of your "Controllers" dialog and your "Assign Controllers" NetPlay dialog.

Here's what I got for what shown in both my assign window and controller settings window. These work fine booting w/ fortune street

JMC4789 wrote:

Can confirm it's not starting in Single Core. Can you bisect? Even if you use GC controllers just to see if it boots in older builds, it'll be enough to see what's going on.

I'm starting to look through builds months apart to see if I find anything that boots it on netplay. 3 so far, no luck.

#6 Updated by Joeybeta 5 months ago

7750

after guessing several times. I did find one build(4.0-6286) that lead to this screen showing up and staying that way for not only netplay but locally as well. With or without dual core. Dolphin hangs when attempting to close.

Slight update before posting this but this is also happening with the following: 4.0-6341, 4.0-6410, 4.0-6550. With the strange oddity that 4.0-6550 only has this happen on local boots but on netplay it just shows a black screen instead, not even getting to the "loading" frozen screen, as shown in the screenshot, and does not hang when attempting to close the emulation through netplay.

Will look into more builds in my free time soon.

#7 Updated by Joeybeta 5 months ago

7752

I might have been really dumb not remembering how to display the logs to actually show up before but here it is from attempting to run the game on the current build on netplay.

#8 Updated by JMC4789 18 days ago

  • Status changed from Questionable to Accepted

This is some kind of XFB initialization bug. I'll be damned, I was wrong.

Also available in: Atom PDF