-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Forza Horizon 5 (1551360) #5285
Comments
Can confirm, also didn't work for me with any Proton Version tried. |
Can confirm, also crashes on AMD with PID missmatch |
Can also confirm not working with any proton version with an AMD system. Splash screen appears for a few seconds, then closes. Attached my proton log (6.3 experimental) which also has a PID missmatch. KERNEL: 5.14.14-300.fc35.x86_64 |
Can confirm here as well. Same issue as @rudi4463, with a PID missmatch, though I'm on NVidia. |
The PID mismatch is unrelated, we see that with all games run from Steam. |
I also couldn't get it to work, even tried with all the FH4 tricks |
It also doesn't work on my machine, but I get an unhandled page fault exception Unhandled exception: page fault on read access to 0x00000010 in 64-bit code (0x00000001405b0808). |
Some problem for me! Would love to see a fix soon :) kernel: 5.11.0-38-generic |
I could get the Forza Horizon 5 splash screen but nothing more |
Most likely it won't work, but can someone try create
Game should open the window with gpu driver error, click "ignore and continue" |
Could it be not launching because the game requires "DirectX 12 Ultimate" ? Some people using Windows 10 LTSC and LTSB have reported the same crashing issue, those don't have "DirectX 12 Ultimate". |
it did help open the game, but as you said crashed in opening cinematic |
Same, crashed as soon as it prompted that I needed to sign in (but did not see sign in window) |
Game opens but crashes during the sign-in phase (with a white window) |
Doing that I don't even get the splash screen anymore and the game just runs forever showing nothing. |
With 6.20-GE-1 this gets me into the main screen that says press enter. Then it gets stuck in a please wait loop, but does not crash. Had to force exit after waiting 15 minutes for it to load in. |
That allowed me to get further than before, however with Proton Experimental the game would crash on the main menu with no input needed, but with Proton 6.3-7 I was able to sit on the main menu and pressing enter did attempt to bring up the white "sign in" window, but it was stuck loading and then crashed. Suspecting there may be an issue with vcrun19, similar to Horizon 4, but haven't been able to test yet. Logs (CrashReport.xml and steam-1551360.log for each respective Proton version): |
I think only Proton Experimental is does things right, GE and 6.3 is crashing a webview with Devs changed webview from Chrome to Edge and this may cause issues, the browser itself should work, but it seems to interact poorly with the game or it's DRM fault |
Running GE's proton, fixes above not needed to get in-game. The game's audio is stuttery, but otherwise I'm able to get in-game with the drm bypass. |
Where you get bleeding edge from? In Steam I can see only Proton Experimental. |
Thank you :) |
The game freezes for me when trying to get out of the garage, what distro & drivers are you running? |
Borked on nvidia maybe? Or just borked for me.
|
i am on RDNA2 forgot to say that. but it is on mangohud. |
Can confirm, it is working on Pop!_OS 21.10 Beta using Proton Experimental bleedding-edge. AMD RX 6900XT. |
Limiting the FPS got me about 30 seconds further but then I had the same crash again. At this point I have tried pretty much everything that others have said worked for them except for using gamescope which for some reason fails with |
I assume you have nvidia, did you try an older/patched gamescope version? |
Yes, already tried all the alternative version in the AUR and compiling it from source, same error every time. Would be interesting to know if anyone who experienced the same kind of crashes fixed it with gamescope, so I know if it is even worth trying to get it to run |
On my laptop with an Intel i7-1260P, with latest proton experimental, it crashes shortly after starting the game: |
Crashes when exiting home, except for the first run after reinstall or after playing for sometime on steam deck beforehand. Seems to be throwing almost the exact same error over and over again. Here's a link to the log file, but it is 4.4 GB when extracted https://drive.google.com/file/d/1a5A810bmdHO4UZhr_BR4Xiu9K3Bv7ZUX/view?usp=sharing I had very few crashes when I was playing the past 2 days before this started happening, and I've tried gamescope but even with the nvidia build from the aur gamescope still doesn't work properly. I'm running a RTX 3070, Nvidia 545.29.06-8, and kernel 6.6.9. |
Nvidia released new beta driver 550, anyone tested it already? |
I'm trying to test with the new 550 driver, but for some reason, the game just intantly crashes the moment it starts loading after clicking on "Continue" or when I start benchmark mode. Idk if it's my SSD or something different. I tried most fixes available, even deleting the game's save folder and it keeps crasing. Doesn't seem to be exclusively tied to NVIDIA though... |
I did a quick test with these start params: Ingame Preset ultra Game just worked, even fast travel worked. |
Compatibility Report
System Information
I confirm:
SymptomsGame go through Intro race with no issues, Log in into xbox account no issues, we reach character creation, upon confirmation of character screen goes black, and spinner will go just a quarter, after x minutes game will close. ReproductionIt happened after installation so I logged out and logged in with another account so intro race was fine again till character creation screen. |
Why people are having conflict results? My problem is Forza 5 says it cannot detect the GPU driver.
However, the original issue comment and some people are using |
System: Whats Wrong: Other Info: Tried both system installed mesa & mesa-git. System Information / Runtime information: Game Logs: |
Forgot to add this is where i get stuck. |
Looking around, this infinite loading bug can happen on Windows as well, some people have success with alt-tabbing to get the game to retry connecting to the servers as reportedly this is what the game gets stuck on. Might be worth installing a network monitoring tool of some sort as well to see what the game's doing; if you have a VPN active, I'd suggest disabling that first. As for your proton logs, nothing looks unusual at first glance, other than the usual vkd3d-proton warning spam (the game does mildly stupid things on the D3D12 side) |
I think you might be right, It appears my ISP & my VPN's ips could be blacklisted from the servers. I'm going to contact the Forza team soon to see what's going on on their end. Thanks🙂 |
Hello Proton versions tested: Mesa versions tested: Log: I recently upgraded to a AMD Ryzen 5 7600x so here's the system information & runtime again |
Tried the 550.67 drivers, no luck, crashing while loading. Tried a few different versions of |
Completely different result. Ubuntu 23.04 with 550.67 driver and latest Proton Experimental. I don't have to specify any start options. The game launches and complains about an unknown GPU driver version but you can click ignore. I played for over 5 hours yesterday without any problem. My GPU is 4060 and I can enable features like DLSS without any problem. |
Decided to be more thorough with testing, and did manage to complete five races without a crash using 550.67, three of which were at 60fps (rather than my usual 30 as limited by mangohud). Results of testing so far included for completeness
|
Just ran updates on my EndeavourOS box (i5-10400f, rx 6600xt) and the game is now crashing on launch (shows splash screen, main window opens and immediately closes) where it was working just last night. Tested on Proton 9.0 (14212803), Experimental 14254421, and GE 9-4. Same behaviors in both kernels 6.8.9-arch1-1 and lts 6.6.30-1. Sometimes GE gets in past the press A to start screen and into the proper loading, but then freezes up and pops up six error boxes instead. Every so often there'll be an in-game message saying the game has been updated and needs to restart. Mesa was upgraded 1:24.0.5-1 -> 1:24.0.6-2. Don't know what other upgraded packages might be relevant, there were over 300 of them. Attaching two log files here, both are the same behavior of immediately crashing and seem to end on the same error, just one is from experimental at over 300MB and the GE one is around 45MB. |
Hello @Gotolei, can you check if https://gitlab.freedesktop.org/drm/amd/-/issues/3343 is relevant to your system? A quick test would be to reboot into an older kernel and see how the game behaves (6.6.30 doesn't count as older). |
Those are the only two I have installed, but I'll see if I can get an older one and report back on that. @kisak-valve Tested in 6.8.8-arch1-1 and it appears to be working. Tried both Proton 9.0-1 and GE 9-4 and both got in-game without incident. |
Can't get Forza Horizon 5 To Work - Fedora 40 KDE Spin (on X11), Nvidia RTX 2060 The game launches but can't really get past the intro video which is flickering until it crashes eventually. Tried various launch options and Proton versions with no luck (from protondb comments). Kernel: 6.8.9-300.fc40.x86_64 |
Try minimising the window with the flickering intros. After a few seconds they usually go back full screen without the flickering. Then when the intros are finished the game may minimise again, just alt+tab back in. That's how I got it to work on amd (it seems to be an Wayland issue) but it should work on NVIDIA too. |
try this, it works with me |
Trying to minimize it or sometimes using alt+tab makes the game disappear or go black and non functional.
Sadly this still had flickering and black screen / crash in the intro video. |
Are you using an ultrawide monitor by chance? After troubleshooting this startup flickering then blackscreen issue for well over 3 hours, i had some freinds test it for me. They have the exact same hardware as me, the only difference being their montiors. They use 16:9 monitors and i use a 21:9 monitor. If i switch my monitors aspect ratio from 21:9 to 16:9, the game launches fine and im able to play it without any issue. I can provide more system info if needed, but i have an amd cpu/gpu. Edit: i see in a comment further up that you are in fact using an ultrawide monitor. If possible, try setting you monitor to a 16:9 aspect ratio and see if it loads. I know its not a good long term solution, but maybe it will help narrow down the root cause of the issue. |
Just saying, but Forza Horizon 5 doesn't launch with Proton Experimental now on my Steam Deck. The game will exit a few seconds into launch. |
Hello @robotman40, please add |
FH5 is ok with proton 9.0-2 on Steam Flatpak Mesa 24.1.1 RX6600. Avoid breaks with a specific distro update, if it breaks on Flatpak it's easy to return without messing up your system. |
The game launches fine on Steamdeck, I was playing it one day and then the next day it prompted me to login to my XBox account, when I did it just closed the login prompt and asked me to do it again. It's a common problem for windows users (google login loop FH5) but the solution is unique to windows. I've tried everything from different proton versions, desktop mode, deleting my protonfiles and reinstalling the game itself, nothing works since you HAVE to sign into the game to play. The issue is with the xbox login, everything else works fine. |
Compatibility Report
System Information
I confirm:
Symptoms
The game crashes immediately after showing loading popup.
Using PROTON_HIDE_NVIDIA_GPU=0 and PROTON_ENABLE_NVAPI=1 env variables doesn't change the outcome.
Also found a reference to Forza's XML crash logfile in Proton's logfile ("C:\users\steamuser\AppData\Local\ForzaHorizon5\CrashReport.xml"), which I also attached to this issue; however it doesn't seem to have much useful info.
Reproduction
Simply launch the game.
steam-1551360.log
CrashReport.txt
The text was updated successfully, but these errors were encountered: