Forza Horizon 4 doesn't get past the splash screen

[Sid127]

I'm using gamescope as a nested session through steam on i3/X11, with an NVIDIA gpu on drivers 515.76.

Forza Horizon 4 refuses to get past the small splash image, though this doesn't happen on other games that have similar splash screens, like Street Fighter V.

Launch argument: gamescope -w 1920 -h 1080 -f -- %command%

[Sid127]

Looked around a bit longer and it looks like this is causing some sort of zombie process/memory leak. Even after closing the gamescope window and steam confirming the game wasn't running, htop and nvtop both showed the game process slowly increasing in memory and holding my cpu at 270%. This didn't happen while launching the game without gamescope

[lostalejandro]

Looked around a bit longer and it looks like this is causing some sort of zombie process/memory leak. Even after closing the gamescope window and steam confirming the game wasn't running, htop and nvtop both showed the game process slowly increasing in memory and holding my cpu at 270%. This didn't happen while launching the game without gamescope

It also happens to me, i think it has something to do with the fact that the "launched" image (in this case the splash screen) dissapears and causes a bug making the "next" image (in this case the game) to launch in some invisible way. I don't know if this only happens on nvidia but my workound is to pass the -e flag even tho i use it nested too. I use this as my launch parameters: gamescope -h 900 -H 1080 -U --fsr-sharpness 8 -f -e -- gamemoderun mangohud %command% This works for almost all the games with splash screen but for others it doesn't. If you really want to run the game with gamescope i suggest you trying out nested mode on a different tty but it's kinda buggy right now on nvidia.

I'm running kernel 6.0.2 and nvidia 520.56.06 GTX 1660 Super

[Sid127]

Did try passing the -e flag on an up to date system as well, and it still doesn't get past the splash screen, but it doesn't create the unkillable process either.

One minor detail I forgot to mention is that I have an Optimus setup, though the same thing happens even when I'm in Nvidia-only mode

[LazarusCat59]

I just had the same issue a while ago, tried reporting on Proton issue tracker instead of here since I thought it was Proton related, and apparently the environment variable DISABLE_GAMESCOPE_WSI=1 gets me past the splash screen. See messages from the Proton issue.

Hopefully this helps to fix this issue.

[CarbonNotes]

In my experience on Deck, if you go into Settings then dismiss the menu (You don't even have to go >1 level deep, just open the Settings menu) before hitting Continue, the game loads up just fine.

If you just immediately hit "Continue", the screen goes black and the Deck drops back to Steam.