Yuzu intermittent startup failure

[drw4013]

Trying to figure this one out.  Yuzu will start sometimes and other times it refuses to open. I changed startup timer to 10 from 5 secs, and the issue was unchanged. Between  the startup successes and failures below, I have made no setting changes in either Yuzu or Launchbox.

I attached logs, but can't see anything for the failures that tells me why it's happening.  Here is what I experienced:

TOTK

Desktop mode
5/18 11:54: LB Success, manually closed Yuzu
5/18 12:05: LB Success, manually closed Yuzu
RESTART
BigBox
5/18 12:11: BB Launch failure after ~5 seconds, kicked back to BigBox
5/18 12:12: BB Launch failure after ~4 seconds, kicked back to BigBox
Switch to Desktop mode
5/18 12:13: LB Launch failure after ~4 seconds, kicked back to LaunchBox
RESTART
BigBox
5/18 12:11: BB Launch failure after ~5 seconds, kicked back to BigBox

Anyone know what might be happening?

 

 

Logs.zip

Edited May 19, 2023 by drw4013

[drw4013]

Is anyone launching Yuzu from LaunchBox without issue?

[skizzosjt]

On 5/23/2023 at 3:18 PM, drw4013 said:

Is anyone launching Yuzu from LaunchBox without issue?

Yea, there isn't any special work arounds required either. if it's still giving you a hard time you would want to prove if it's emulator related or frontend related. do that by opening a CMD window and launching the game that way, using the same launch commands as LB/BB would. if it fails there then likely your launch commands aren't correct. -f switch is for launching in fullscreen and -g switch is defining the file (game) to run. so that sequence is important, the -g switch must come last due to the file path gets appended onto the end. edit: using emulator version "yuzu 1439" - I just had to set this emulator up again in the last week so it should be a pretty recent build

 

 

I do use Startup and Shutdown Screens, still works OK with them enabled. Not sure if this is what you meant by "startup timer", maybe you meant the slider "Startup Load Delay"?

 

And I use this in my running script to make sure it exits OK

$Esc::
WinClose, ahk_exe {{{StartupEXE}}}

 

Edited May 24, 2023 by skizzosjt
emulator version added

[drw4013]

On 5/24/2023 at 2:57 PM, skizzosjt said:

Yea, there isn't any special work arounds required either. if it's still giving you a hard time you would want to prove if it's emulator related or frontend related. do that by opening a CMD window and launching the game that way, using the same launch commands as LB/BB would. if it fails there then likely your launch commands aren't correct. -f switch is for launching in fullscreen and -g switch is defining the file (game) to run. so that sequence is important, the -g switch must come last due to the file path gets appended onto the end. edit: using emulator version "yuzu 1439" - I just had to set this emulator up again in the last week so it should be a pretty recent build

 

 

I do use Startup and Shutdown Screens, still works OK with them enabled. Not sure if this is what you meant by "startup timer", maybe you meant the slider "Startup Load Delay"?

 

And I use this in my running script to make sure it exits OK

$Esc::
WinClose, ahk_exe {{{StartupEXE}}}

 

Yes, I was referring to startup delay.  I've messed with it and it doesn't seem to impact anything.  Here are my settings:

I am narrowing it down - I haven't been able to start a game from the cmd prompt. Yuzu gives me "the ROM format is not supported. Starting from the Yuzu GUI is fine.

Could you post your cmd line that works for you?

[drw4013]

I was able to get it to launch via cmd prompt by removing all spaces (from both the filename AND the full directory).  Strange that Yuzu has issues with that, but whatever.

So this works:

C:\Emulators\Yuzu\yuzu-windows-msvc>yuzu.exe -f -g "C:\Games\Nintendo_Switch\Zelda_TotK\zelda.xci"

But the issue remains in Launchbox and BigBox after updating the Launch settings with the new directory and file names. A few seconds after launching, it goes right back to LB/BB.  Yuzu is not open.  I can't see anything in the logs that indicate why:

2023-05-26 10:51:45 AM Begin M3U Check.
2023-05-26 10:51:45 AM RomPath after M3U build: C:\Games\Nintendo_Switch\Zelda_TotK\zelda.xci
2023-05-26 10:51:46 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - LastPlayedDate = 5/26/2023 10:51:46 AM
2023-05-26 10:51:46 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:46 AM Game.PlayCount changed from 75 to 76: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch)
2023-05-26 10:51:46 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - PlayCount = 1
2023-05-26 10:51:46 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:46 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - LastPlayedDate = 5/26/2023 10:51:46 AM
2023-05-26 10:51:46 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:46 AM DataManager.SaveInternal started.
2023-05-26 10:51:46 AM Saving InputBindings.xml...
2023-05-26 10:51:46 AM Saving GameControllers.xml...
2023-05-26 10:51:46 AM Saving ListCache.xml...
2023-05-26 10:51:46 AM Saving Settings.xml...
2023-05-26 10:51:46 AM Saving BigBoxSettings.xml...
2023-05-26 10:51:46 AM Saving UnsyncedChanges.xml...
2023-05-26 10:51:47 AM Saving C:\Users\Owner\LaunchBox\Data\Platforms\Nintendo Switch.xml...
2023-05-26 10:51:47 AM Saving C:\Users\Owner\LaunchBox\Data\Platforms\Steam.xml...
2023-05-26 10:51:47 AM DataManager.SaveInternal completed successfully.
2023-05-26 10:51:56 AM Aborting MameHighScores.Parse: Uploading MAME high scores is disabled in settings.
2023-05-26 10:51:56 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - PlayTime = 10
2023-05-26 10:51:56 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:56 AM Music.Resume Start
2023-05-26 10:51:59 AM Attract Mode stopped
2023-05-26 10:51:59 AM Music.Pause Start
2023-05-26 10:52:01 AM Music.Resume Start
2023-05-26 10:52:02 AM Attract Mode stopped
2023-05-26 10:52:02 AM Music.Pause Start

My Yuzu settings:

 

Edited May 26, 2023 by drw4013

[DeadVoivod]

This is not helpful but I never had any problems launching games in Yuzu via LaunchBox. 

My command parameters are only -f -g

[Suhrvivor]

The only games i have problems with are the ones on custom xci format that have multiple DLCs and updates all in one file (I get an infinite loading screen). other than that it works fine. NSP files and launching XCis from Yuzu itself works fine though.

[rexryan]

31 minutes ago, Suhrvivor said:

The only games i have problems with are the ones on custom xci format that have multiple DLCs and updates all in one file (I get an infinite loading screen). other than that it works fine. NSP files and launching XCis from Yuzu itself works fine though.

Shouldn't have problems there. Are you doing your own? or a downloaded game with DLC and Updates?

 

[skizzosjt]

On 5/26/2023 at 1:54 PM, drw4013 said:

I was able to get it to launch via cmd prompt by removing all spaces (from both the filename AND the full directory).  Strange that Yuzu has issues with that, but whatever.

So this works:

C:\Emulators\Yuzu\yuzu-windows-msvc>yuzu.exe -f -g "C:\Games\Nintendo_Switch\Zelda_TotK\zelda.xci"

But the issue remains in Launchbox and BigBox after updating the Launch settings with the new directory and file names. A few seconds after launching, it goes right back to LB/BB.  Yuzu is not open.  I can't see anything in the logs that indicate why:

2023-05-26 10:51:45 AM Begin M3U Check.
2023-05-26 10:51:45 AM RomPath after M3U build: C:\Games\Nintendo_Switch\Zelda_TotK\zelda.xci
2023-05-26 10:51:46 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - LastPlayedDate = 5/26/2023 10:51:46 AM
2023-05-26 10:51:46 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:46 AM Game.PlayCount changed from 75 to 76: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch)
2023-05-26 10:51:46 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - PlayCount = 1
2023-05-26 10:51:46 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:46 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - LastPlayedDate = 5/26/2023 10:51:46 AM
2023-05-26 10:51:46 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:46 AM DataManager.SaveInternal started.
2023-05-26 10:51:46 AM Saving InputBindings.xml...
2023-05-26 10:51:46 AM Saving GameControllers.xml...
2023-05-26 10:51:46 AM Saving ListCache.xml...
2023-05-26 10:51:46 AM Saving Settings.xml...
2023-05-26 10:51:46 AM Saving BigBoxSettings.xml...
2023-05-26 10:51:46 AM Saving UnsyncedChanges.xml...
2023-05-26 10:51:47 AM Saving C:\Users\Owner\LaunchBox\Data\Platforms\Nintendo Switch.xml...
2023-05-26 10:51:47 AM Saving C:\Users\Owner\LaunchBox\Data\Platforms\Steam.xml...
2023-05-26 10:51:47 AM DataManager.SaveInternal completed successfully.
2023-05-26 10:51:56 AM Aborting MameHighScores.Parse: Uploading MAME high scores is disabled in settings.
2023-05-26 10:51:56 AM MarkGamePlatformChanged called: The Legend of Zelda: Tears of the Kingdom (Nintendo Switch) - PlayTime = 10
2023-05-26 10:51:56 AM WARNING: MarkGamePlatformChanged complete, change has been recorded
2023-05-26 10:51:56 AM Music.Resume Start
2023-05-26 10:51:59 AM Attract Mode stopped
2023-05-26 10:51:59 AM Music.Pause Start
2023-05-26 10:52:01 AM Music.Resume Start
2023-05-26 10:52:02 AM Attract Mode stopped
2023-05-26 10:52:02 AM Music.Pause Start

My Yuzu settings:

 

 

Looks like we have the same exact parameters as far as launch commands go so I don't see any red flags there. If you look at the first photo I attached, that is the command line stuff and yours is identical as far as I can tell.

Since you did end up being able to launch it straight from a CMD window, by theory, LB is doing the same exact thing so now I'm scratching my head why it wouldn't give you the same positive result using the same commands in LB

We at least know the ROM file is a good dump if you got it launch directly via a CMD window. And XCI is the cartridge dump format and is certainly supported.

 

I'm scratching my head man, it really doesn't look like you got anything obvious wrong

[Lukeyboy67]

I've just delevoped the exact same problem, every game launched before then yesterday they all suddenlt stopped working. I run a game, it shows Yuzu GUI for a second then reverts back to LB. If I run them through the emulator they work fine. I've not changed any settings in the emu or in LB. Did you manange to solve the issue?

 

[neil9000]

1 hour ago, Lukeyboy67 said:

I've just delevoped the exact same problem, every game launched before then yesterday they all suddenlt stopped working. I run a game, it shows Yuzu GUI for a second then reverts back to LB. If I run them through the emulator they work fine. I've not changed any settings in the emu or in LB. Did you manange to solve the issue?

 

Sounds like a bug in the latest yuzu update then.

 

[DeadVoivod]

11 hours ago, neil9000 said:

Sounds like a bug in the latest yuzu update then.

 

It's always the others 😄

Fortunately Yuzu gets updated quite regularly, that might solve the problem. 

[neil9000]

4 hours ago, DeadVoivod said:

It's always the others 😄

Fortunately Yuzu gets updated quite regularly, that might solve the problem. 

Well there has been no Launchbox update between when Yuzu worked for you and when it didn't, so yeah its not Launchbox as nothing has changed there, Yuzu on the other hand as you say updates pretty much every day. In fact the Yuzu update specifically says that "Yuzu is a experimental emulator and that things will break" while it updates.

[j1ohan]

Hi,

Same issue here. Went back a few builds and it's working again. Probably something that will be fixed in the future.

[RatGuts_85]

Has this issue been fixed yet?

[djohng]

I also have the exact same issue; but only after I updated to the latest version of Yuzu, so it's likely Yuzu, since I have changed nothing on LB/BB side.

[Lukeyboy67]

My problem persists so I've started using Ryujinx fo everything which is not ideal as Yuzu runs some better. This problem started about a week ago, everything worked perfect before and I've changed no settings so very frustrating. I'll try a earlier build and see what happens....

 

[skizzosjt]

To help the community, could users please share the exact Yuzu version(s) that is broken in this regard, launching games via LaunchBox / Big Box as in launching games via command line? This way users know which one(s) to avoid or which ones to rollback to

Last one I've tried and stuck with is same from my earlier post. Its a build from a month ago. I've never experienced this issue. so I would recommend to try yuzu 1439 if you are on another version and it's giving you a hard time.

 

I'll link to that version below. download the zip file I have circled (assuming you're on Windows and want a zip file that is!)

https://github.com/yuzu-emu/yuzu-mainline/releases/tag/mainline-0-1439

[Guest]

I'm currently using v3267 (what it says at the top anyway), and it's working fine on my end. I believe I'm a bit behind on updates on this one, few months maybe. Usual fix for Yuzu is to use Vulkan. Can find its setting in Configure>Graphics>API, you can also set "per game" settings. Right clicking on a game in the menu and clicking "Properties" will bring up the per game settings. Can maybe try the other API's to see if launches the game.

UPDATE: I just updated to the latest version out of curiosity, it now says 3703 at the top and it still seems to work fine on my end. Not sure if they fixed it by now or not.

Edited June 22, 2023 by KingSlayer420

[skizzosjt]

@KingSlayer420 lol wtf I've never seen that nomenclature for Yuzu versions?! thanks for sharing but I have no idea how that fits into this. The latest version would be "yuzu 1476" per their gituhub and is seen on their website within the URL as another method to correlate these numbers. and they use the same version # for Linux, Windows, and....whatever that 3rd icon represents lol sorry for my ignorance there I have no idea what that is for (edit - it's github lol 🤦‍♂️ - how many times I've been on that site I've never once paid attention to github's logo)

 

Linux

 

Windows

 

github

 

Any Yuzu version I've ever used is named like what I am detailing. When I open the emulator the window is named in the same format "Yuzu XXXX" with XXXX being the version #. This all pertains to the mainline versions

 

OK so just checked out YUZU UPDATER and this is apparently early access versions. So I'd like to believe this explains why the nomenclature is so different.  If someone knows different please correct me. But this is good news as it would suggest it would be fixed in the next mainline release that uses the early access code-base.

Edited June 22, 2023 by skizzosjt
github icon