search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.9k stars 1.04k forks source link

Forza Horizon 4 (1293830) #4667

Open NTMan opened 3 years ago

NTMan commented 3 years ago

Compatibility Report

System Information

I confirm:

steam-1293830.log

Symptoms

The game crashes at start.

Reproduction

Always.

UPDATE with Proton experimental-6.3-20210723b

The following problems still remain unresolved:

  1. At startup and when changing graphics settings, the game shows a black screen. To show the picture from the game, you need to press <Alt + Tab> twice to switch to a any other window and return back to the game. The bug is repeated with both RADV and AMDVLK. Demonstration: https://youtu.be/GSOvB-LeUkA

  2. ~~During first race in Fortune Island event the game crashes every time. Demonstration: https://youtu.be/k73nyalMLPs Proton log: https://drive.google.com/file/d/1bRO5nTtGyM6TEhxyFOjTbIoxcT8DLHMq/view?usp=sharing (105.1 MB)~~ UPD: Fortune Island event is playable with Proton experimental-6.3-20211004

  3. Unable to add a friend to the session. The game says that there are no friends online. Game Bar is also not called by <Super + G>. Screenshot from 2021-07-24 16-33-31

  4. When trying to find a club, the game shows the error "There is no Windows program configured to open this type of file." Screenshot from 2021-07-24 16-42-12 After clicking on the "Ok" button, the screen goes out, and to return the picture you need apply workaround solution from issue 1, after which we see another error "There was an error communicating the Forza Horizon 4 server. Please try again later." Screenshot from 2021-07-24 16-42-23

  5. PROTON_LOG = 1 is too verbosive, which makes it impossible to use it. If it's just stupid to go in and exit the game without playing for a second, then 500Mb of logs will be written to the disk. And for an hour of the game, 100Gb of logs are accumulated. The logs are flooded with messages trace: seh: dump_unwind_info with assembler opcodes. And FPS with PROTON_LOG = 1 sags at least three times. steam-1293830.zip

  6. Vibration of triggers does not work on Microsoft gamepads imitating traction, thus killing the wow effect that I got playing for the first time in Forza Horizon 4 on Xbox One X.

gabibbo97 commented 3 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/4667#issuecomment-826169878

Hello, please find my hardware survey results in this gist

rudi4463 commented 3 years ago

Stuck on Splash Screen too. Gist steam-1293830.log

71.625:00f4:00f8:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

Might be the problem.

kisak-valve commented 3 years ago

Thanks @gabibbo97, that eliminates some guesses I had last night. Can you easily test if the game and Proton behaves the same with a GNOME/X session as a GNOME/wayland session?

gabibbo97 commented 3 years ago

Thanks @gabibbo97, that eliminates some guesses I had last night. Can you easily test if the game and Proton behaves the same with a GNOME/X session as a GNOME/wayland session?

The previous log was with Wayland, this time with Xorg the game crashes

steam-1293830.zip

rudi4463 commented 3 years ago

Thanks @gabibbo97, that eliminates some guesses I had last night. Can you easily test if the game and Proton behaves the same with a GNOME/X session as a GNOME/wayland session?

In my case X Session fixed it and i was able to play the first couple of races without any crashes or other problems. DualSense controller works just fine too.

kisak-valve commented 3 years ago

Great, that log looks healthier and I think it tells us that the VKD3D / Timeline semaphore missing issue is connected to running in a GNOME/wayland session.

So for pondering the game on your system, we're back to VKD3D having a hard time with GCN2, but now with less fireworks in the log.

shyam-s00 commented 3 years ago

Working very well on Nvidia here, though I had to upgrade from 460.x to 465.24.02 (and use dxgi.customVendorId = 10de ) to prevent a crash in the second stage of the first race.

Did anyone manage to get a wheel controller to work? My G29 is not detected, not even as a generic input device.

According to game's inputmappingprofiles.zip it should be looking for VID/PID 0x046dc24f which matches with how my controller presents itself.

The game manual warns that Logitech gaming software is necessary for correct controller detection, but it also explains that is purely to ensure the controller uses the right VID/PID, so that shouldn't be an issue under Proton.

Any ideas what else might the game expect from the controller to recognize it?

Here's +hid,+hidp,+hid_report,+rawinput,+xinput,+dinput,+plugplay,+joystick,+winmm: trace.txt

In particular, the trace suggests the device is available to wine:

0234:trace:dinput:find_sdldevs Found a joystick on 0x7efbf8080900: Logitech G29 Driving Force Racing Wheel
0234:trace:dinput:find_sdldevs  ... with force feedback
0234:trace:dinput:find_sdldevs Found a joystick on 0x7efbf801c080: Xbox 360 Controller
0234:warn:dinput:find_sdldevs Ignoring force feedback support for "Xbox 360 Controller"
0234:trace:dinput:fill_joystick_dideviceinstanceA 580 0x1dfff420
0234:trace:dinput:fill_joystick_dideviceinstanceW 1100 0x1dfff700

With all these settings, mine still crash at first race at 3rd stage (Spring)

ga2mer commented 3 years ago

With all these settings, mine still crash at first race at 3rd stage (Spring)

Same, hangs on "spring is in the air" text

System

shyam-s00 commented 3 years ago

With all these settings, mine still crash at first race at 3rd stage (Spring)

Same, hangs on "spring is in the air" text

System

After hours of trying, I had to add PROTON_HIDE_NVIDIA_GPU to my launch option and it works ....

gabibbo97 commented 3 years ago

Update: the game did somehow start in Gnome40/Xorg, allowing me to access the main menu, the game then crashes while loading the map, the only option that I added was VKD3D_DEBUG=info to the launch options steam-1293830.zip

kisak-valve commented 3 years ago

I think that 352:err:vkd3d_create_image: Sparse images not supported with format 139, type 1, samples 1, usage 0x7, tiling 0. is the line of interest from your log, which is immediately followed by an access violation (c000005) and the game goes downhill from there. Reference: https://gitlab.freedesktop.org/mesa/mesa/-/commit/d2524ed4a072430ca4acba50f00041d03d7039b1

ah- commented 3 years ago

With all these settings, mine still crash at first race at 3rd stage (Spring)

Same, hangs on "spring is in the air" text System

After hours of trying, I had to add PROTON_HIDE_NVIDIA_GPU to my launch option and it works ....

No luck for me, I'm still getting [ 5492.215482] NVRM: Xid (PCI:0000:08:00): 31, pid=7567, Ch 00000038, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_3 faulted @ 0x2_78415000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

ga2mer commented 3 years ago

No luck for me, I'm still getting [ 5492.215482] NVRM: Xid (PCI:0000:08:00): 31, pid=7567, Ch 00000038, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_3 faulted @ 0x2_78415000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ

Yeah, hangs on transitions between videos and game with dxvk.conf spoofing, proton env, without, changed game settings, nothing helps

NicoSoler commented 3 years ago

Great, that log looks healthier and I think it tells us that the VKD3D / Timeline semaphore missing issue is connected to running in a GNOME/wayland session.

So for pondering the game on your system, we're back to VKD3D having a hard time with GCN2, but now with less fireworks in the log.

Sorry for not responding earlier. I actually just tried it in an Xorg session and it runs just fine.

ga2mer commented 3 years ago

I finally passed first race, I just set settings to "very low" and set 72 fps lock instead of 144, no gpu hiding

I think something different affects hangs

CCF100 commented 3 years ago

Some odd behavior I've noticed, I'm trying to run Forza on an NVIDIA Optimus (hyprid GPU) laptop, and as long as the setting in my BIOS is set to use both GPUs, the game will refuse to get anywhere past the start splash, (and before you ask, I do set the proper env vars to tell it to use the NVIDIA GPU)

patgrajkowski commented 3 years ago

I manage to run this game on my RX580 with newest mesa-git, game is somehow smooth but looks very glitchy. Gpu is fine i've tested it. 2021-04-26_23-27

kisak-valve commented 3 years ago

Hello @patgrajkowski, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the visual corruption, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

gofman commented 3 years ago

It looks the same here too with the current mesa git. It works without such glitches though on RX580 on Mesa listed as known good in release notes 899dd8e60a5228c4506400d621ef6b5abfe5e32c.

patgrajkowski commented 3 years ago

Here is log and here system information i dont know why system information is saying I have mesa 21.0.3 I've checked this in terminal and terminal says that I have OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.2.0-devel (git-496f99e8d1)

ah- commented 3 years ago

I finally passed first race, I just set settings to "very low" and set 72 fps lock instead of 144, no gpu hiding

I think something different affects hangs

This worked for me as well, on NVIDIA. I turned down the settings to very low, reduced resolution and got through the first couple races with no issues. Even afterwards it seems to run really well for me now.

Edit: And a few minutes later it crashed again, this time with: 


[ 2496.842036] NVRM: GPU Board Serial Number: 0323818176837
[ 2496.842039] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception on GPC 0: 3D WIDTH ZT Violation. Coordinates: (0x566, 0x2f4)
[ 2496.842053] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception: ESR 0x500420=0x80000004 0x500434=0x2f40566 0x500438=0x5050000 0x50043c=0x0
[ 2496.842071] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception on GPC 1: 3D WIDTH ZT Violation. Coordinates: (0x568, 0x2f4)
[ 2496.842082] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception: ESR 0x508420=0x80000004 0x508434=0x2f40568 0x508438=0x5050000 0x50843c=0x0
[ 2496.842099] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception on GPC 2: 3D WIDTH ZT Violation. Coordinates: (0x5ee, 0x2d8)
[ 2496.842110] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception: ESR 0x510420=0x80000004 0x510434=0x2d805ee 0x510438=0x5050000 0x51043c=0x0
[ 2496.842127] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception on GPC 3: 3D WIDTH ZT Violation. Coordinates: (0x5f8, 0x2dc)
[ 2496.842138] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception: ESR 0x518420=0x80000004 0x518434=0x2dc05f8 0x518438=0x5050000 0x51843c=0x0
[ 2496.842155] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception on GPC 4: 3D WIDTH ZT Violation. Coordinates: (0x600, 0x2dc)
[ 2496.842166] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception: ESR 0x520420=0x80000004 0x520434=0x2dc0600 0x520438=0x5050000 0x52043c=0x0
[ 2496.842182] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception on GPC 5: 3D WIDTH ZT Violation. Coordinates: (0x5f6, 0x2d8)
[ 2496.842194] NVRM: Xid (PCI:0000:08:00): 13, pid=433, Graphics Exception: ESR 0x528420=0x80000004 0x528434=0x2d805f6 0x528438=0x5050000 0x52843c=0x0
[ 2496.842558] NVRM: Xid (PCI:0000:08:00): 13, pid=9110, Graphics Exception: ChID 0038, Class 0000c597, Offset 00000000, Data 00000000```
rafalcieslak commented 3 years ago

In terms of controller support, simply disabling Steam Input gets my G29 to work - it is available in game, recognized as a wheel, and named "Logitech G29". However, button images use generic (1), (2), (3) ... symbols, and default bindings are all wrong, so I assume it is detected as a generic controller. All buttons and axes bindings are customizable, and with that done the controller works well. Force feedback (using new-lg4fff) seems to be working perfectly too.

Concerning crashes on NVIDIA: in my experience "very low" graphics settings does indeed tremendously decrease the chance of a crash when entering an event or transitioning into race by other means. It does not completely eliminate such crashes, but brings their frequency down to playable levels. This has no effect on rarer crashes in free roam mode that manifest differently, though.

I will attempt to pinpoint if there is a specific graphics setting that affects event loading crashes, but considering their random nature it will likely take me a while to reach reproducible results I'm confident to share.

CCF100 commented 3 years ago

https://youtu.be/7IGQ1r9vZj8 This video may be helpful

kisak-valve commented 3 years ago

Between https://gitlab.freedesktop.org/mesa/mesa/-/commit/9bcaeddf77298a32f567723359e714b61eef6479 and https://gitlab.freedesktop.org/mesa/mesa/-/commit/8b31092bcd38db242eba9e2267fb17b841c93735 the visual corruption with bleeding edge mesa/RADV should be resolved. Please retest with mesa git that includes these commits.

X-m7 commented 3 years ago

Some odd behavior I've noticed, I'm trying to run Forza on an NVIDIA Optimus (hyprid GPU) laptop, and as long as the setting in my BIOS is set to use both GPUs, the game will refuse to get anywhere past the start splash, (and before you ask, I do set the proper env vars to tell it to use the NVIDIA GPU)

Damn, my laptop is one of those ones that's missing that option. What launch options did you use to get it running without Optimus though? I'm using nvidia-xrun to run the whole X server and DE on the dGPU, and I've already set VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/nvidia_icd.json, so I don't see why Optimus would still interfere in my case, and yet I'm stuck on the splash screen too (the game also pegs one CPU core almost fully, so like ~10% total usage on a 4 core 8 thread CPU).

Edit: My Steam system information is here, and the log is here (I let it run for about 15 minutes in case it was just slow, doesn't seem like it).

thankjura commented 3 years ago

I will attempt to pinpoint if there is a specific graphics setting that affects event loading crashes, but considering their random nature it will likely take me a while to reach reproducible results I'm confident to share.

Try enable "Allow flipping" in nvidia-settings and turn on vertical sync in game

rafalcieslak commented 3 years ago

Try enable "Allow flipping" in nvidia-settings and turn on vertical sync in game

No luck, in fact, all my tests so far were done with "allow flipping" enabled.

X-m7 commented 3 years ago

So I decided to try running it on my integrated graphics (Intel HD Graphics 530) instead of my discrete graphics (NVIDIA GTX 960M), and it actually got past the splash screen, and I could hear the sounds of the intro videos as well as the title screen music. Granted, the screen was either fully white or fully black the whole time, but now I'm wondering what the issue is with running it on my NVIDIA GPU. (My previous comment about trying that is the third above this one).

My system information in Intel mode is here, and the log is here.

gabibbo97 commented 3 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/4667#issuecomment-826345146

You were right, on my new PC (5950X + 6900XT) the game now runs properly with occasional crashes

macktab commented 3 years ago

Game exits after pressing "Return" on main menu. https://gist.github.com/macktab/31d239bfb7ded7f841b38b2a587af18d steam-1293830.zip


wine: Unhandled page fault on write access to 00007F08507F84D0 at address 00007F09B45933C2 (thread 0284), starting debugger...
Unhandled exception: page fault on write access to 0x7f08507f84d0 in 64-bit code (0x00007f09b45933c2).
mathew2214 commented 3 years ago

i played through the entirety of summer without issue. but now that i got to the autumn part of the game, it crashes a few seconds after showing my my home's menu. proton log: https://gist.github.com/mathew2214/2cabe57978c7dd82125f0a874b0c91bb

system information: https://gist.github.com/mathew2214/bfc6632f0905b1de27d0091480134f0e

AMD Navi10 MESA 21.1.0 proton 6.10-GE-1

NyaomiDEV commented 3 years ago

Did anyone notice that there is no way to invite friends to private adventures? and there is also no way of joining their sessions...

mathew2214 commented 3 years ago

Did anyone notice that there is no way to invite friends to private adventures? and there is also no way of joining their sessions...

yes i did notice that. the invite friends button just does nothing. but my friends on windows are able to join me. also, anybody else constantly crash on Fortune Island?

asaokej commented 3 years ago

I have tried many times to travel to Fortune Island but it crashes in the loading screen almost every time with this messages in logs: NVRM: Xid (PCI:0000:01:00): 31, pid=12954, Ch 00000055, intr 00000000. MMU Fault: ENGINE GRAPHICS GPCCLIENT_T1_6 faulted @ 0x1_f1fba000. Fault is of type FAULT_PDE ACCESS_TYPE_VIRT_READ. The two times it loaded through the loading screen it crashed early in the introduction race for fortune island with the same error message. Lego dlc I could travel to once but after I left I have not been able to travel back with the same issue as fortune island. I have not tried with the new mesa git yet.

mathew2214 commented 3 years ago

Replying to https://github.com/ValveSoftware/Proton/issues/4667#issuecomment-877833154

i find that switching to Valve's proton experimental and then recreating the game's prefix temporarily fixes fortune island. but after less than an hour, it starts crashing again. here's a log of Fortune Island crashing on load: https://gist.github.com/mathew2214/0430fdc5126aba33c9e4a4917aa5319d

shyam-s00 commented 3 years ago

I tried the game with Nvidia 470 beta driver and I haven't experienced any crash for hours. However, there are frequent frame drops during game play.

PxChainWarden commented 3 years ago

Hi, When I press play button on steam game devours 1 CPU core to %100. Game doesn't open a window. Steam says its running. Both proton-experimental and proton-6.3-5. Can anybody help me to get this game working?

[ali@archl ~]$ pacman -Q | grep vk
dxvk-bin 1.9-1
vkd3d 1.2-1
vkd3d-proton-bin 2.4-1

System Specs: image Log File: steam-1293830.log

kisak-valve commented 3 years ago

Hello @PxChainWarden, these look like the lines of interest in your log:

err:module:process_init failed to load L"C:\\windows\\system32\\explorer.exe", error 4000000e
err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nodrv_CreateWindow The explorer process failed to start.

I suspect that you're seing an NTFS-related issue, similar to some of the feedback on #4269. Out of mild curiosity, what filesystem are you using with /HDD/SteamLibrary Linux/?

The system-installed dxvk and vkd3d packages are not used by Proton.

PxChainWarden commented 3 years ago

Hello @PxChainWarden, these look like the lines of interest in your log:

err:module:process_init failed to load L"C:\\windows\\system32\\explorer.exe", error 4000000e
err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
err:winediag:nodrv_CreateWindow The explorer process failed to start.

I suspect that you're seing an NTFS-related issue, similar to some of the feedback on #4269. Out of mild curiosity, what filesystem are you using with /HDD/SteamLibrary Linux/?

The system-installed dxvk and vkd3d packages are not used by Proton.

It's using NTFS. I forgot proton-experimental is installed on /HDD/SteamLibrary Linux/. Changed library for proton, game opens now. While "Optimizing for your PC" game freezes steals so much CPU time cant even move cursor. Proton log file too large but i think line of interest is this:

850.112:0454:0778:fixme:bcrypt:BCryptCreateHash ignoring object buffer
859.153:0454:0778:fixme:bcrypt:BCryptCreateHash ignoring object buffer
859.287:0454:0778:fixme:bcrypt:BCryptCreateHash ignoring object buffer
871.208:0454:0778:fixme:bcrypt:BCryptCreateHash ignoring object buffer
934.414:0454:0778:fixme:bcrypt:BCryptCreateHash ignoring object buffer
1113.971:0454:0464:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0464, blocked by 0778, retrying (60 sec)
1134.576:0454:04c4:fixme:bcrypt:BCryptCreateHash ignoring object buffer
1139.521:0454:03e8:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 03e8, blocked by 0778, retrying (60 sec)
1141.442:0454:0474:err:ntdll:RtlpWaitForCriticalSection section 00000000002B4560 "../src-wine/dlls/ntdll/threadpool.c: threadpool.cs" wait timed out in thread 0474, blocked by 06e0, retrying (60 sec)
1141.442:0454:06d4:err:ntdll:RtlpWaitForCriticalSection section 00000000002B4560 "../src-wine/dlls/ntdll/threadpool.c: threadpool.cs" wait timed out in thread 06d4, blocked by 06e0, retrying (60 sec)
1141.442:0454:06d8:err:ntdll:RtlpWaitForCriticalSection section 00000000002B4560 "../src-wine/dlls/ntdll/threadpool.c: threadpool.cs" wait timed out in thread 06d8, blocked by 06e0, retrying (60 sec)
1151.775:0454:06e0:err:ntdll:RtlpWaitForCriticalSection section 00000000002B4560
 "../src-wine/dlls/ntdll/threadpool.c: threadpool.cs" wait timed out in thread 06e0, blocked by 0474, retrying (60 sec)
1158.213:0454:06dc:err:ntdll:RtlpWaitForCriticalSection section 00000000002B4560 "../src-wine/dlls/ntdll/threadpool.c: threadpool.cs" wait timed out in thread 06dc, blocked by 0474, retrying (60 sec)
1165.233:0454:03ec:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 03ec, blocked by 0778, retrying (60 sec)
1180.869:0454:03f4:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 03f4, blocked by 0778, retrying (60 sec)
1180.869:0454:0464:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 0464, blocked by 0778, retrying (60 sec)
1189.281:0454:06dc:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 06dc, blocked by 0778, retrying (60 sec)
1206.031:0454:03e8:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 03e8, blocked by 0778, retrying (60 sec)
1209.176:0454:06d4:err:ntdll:RtlpWaitForCriticalSection section 000000007BC6A580 "../src-wine/dlls/ntdll/loader.c: loader_section" wait timed out in thread 06d4, blocked by 0778, retrying (60 sec)
NodokaHanamura commented 3 years ago

Reporting that Forza Horizon 4 does work with Latest version of Glorious Eggroll (6.12-GE-1) but I've got three issues:

Specs:

AMD Ryzen 5 3600 NVIDIA GTX 1060 3GB 16GB DDR4 Ubuntu 20.04 derivative

NTMan commented 3 years ago

The following problems still remain unresolved:

  1. At startup and when changing graphics settings, the game shows a black screen. To show the picture from the game, you need to press <Alt + Tab> twice to switch to a any other window and return back to the game. The bug is repeated with both RADV and AMDVLK. Demonstration: https://youtu.be/GSOvB-LeUkA

  2. ~~During first race in Fortune Island event the game crashes every time. Demonstration: https://youtu.be/k73nyalMLPs Proton log: https://drive.google.com/file/d/1bRO5nTtGyM6TEhxyFOjTbIoxcT8DLHMq/view?usp=sharing (105.1 MB)~~ UPD: Fortune Island event is playable with Proton experimental-6.3-20211004

  3. Unable to add a friend to the session. The game says that there are no friends online. Game Bar is also not called by <Super + G>. Screenshot from 2021-07-24 16-33-31

  4. When trying to find a club, the game shows the error "There is no Windows program configured to open this type of file." Screenshot from 2021-07-24 16-42-12 After clicking on the "Ok" button, the screen goes out, and to return the picture you need apply workaround solution from issue 1, after which we see another error "There was an error communicating the Forza Horizon 4 server. Please try again later." Screenshot from 2021-07-24 16-42-23

  5. PROTON_LOG = 1 is too verbosive, which makes it impossible to use it. If it's just stupid to go in and exit the game without playing for a second, then 500Mb of logs will be written to the disk. And for an hour of the game, 100Gb of logs are accumulated. The logs are flooded with messages trace: seh: dump_unwind_info with assembler opcodes. And FPS with PROTON_LOG = 1 sags at least three times. steam-1293830.zip

  6. Vibration of triggers does not work on Microsoft gamepads imitating traction, thus killing the wow effect that I got playing for the first time in Forza Horizon 4 on Xbox One X.

NyaomiDEV commented 3 years ago

Game Bar is also not called by <Super + G>.

@NTMan Proton does not have any kind of implementations for the Xbox Game Bar, which is a Windows component. It is only natural that it cannot be called on Linux.

mozo78 commented 3 years ago

It crashes with NVIDIA. Sometimes I can pass Autumn but it always freeze at the start of Winter.

JacoG-RH commented 3 years ago

Running Nvidia driver 470.57.02 the game crashes for me now during the "optimizing for your PC" part every time. Same on my partner's PC. We are both on Manjaro. Tried with Proton Experimental and the newest GE build.

mozo78 commented 3 years ago

I'm with 470.57.02 too but I can pass rhis screen. Unfortunately it crashes on the first or second season.

JacoG-RH commented 3 years ago

Downgraded to the 465 nvidia driver and playing with the current Proton Experimental it seems to work. Even managed to play through summer and winter and bits of spring. Sometimes still freezes up though. I have a log, but it's 2.3GB so below are the last 5000 lines. My partner's been trying to get it to even get past the introductory mini-races with the same setup as me with 0 success. steam-1293830-n5000.zip

AsciiWolf commented 3 years ago

Was anyone able to get Forza Horizon 4 running on Flatpak Steam with community Flatpak build of Proton? On my system, it always crashes right after start because of a wine64-preloader coredump. Are the Forza Horizon 4 patches compatible with Proton running inside a Flatpak sandbox?

segvee commented 3 years ago

I tried running the game on my desktop, an older i5 with a GTX 970. The maximum that I got out of the game was playing the intro, after which it crashed and didn't start. I don't have access to that system at the moment.

I have a laptop with a discrete NVidia GPU now and using Optimus the game never goes beyond the splash screen. To start the game I use the following command line options: PROTON_LOG=1 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only %command% When not specifying anything the game defaults to the internal Intel GPU and the game seems to start i.e. it goes beyond the splash screen but the game window just stays black and has to be killed from another machine via ssh since the machine is running but the X server is not responding.

Here is the Steam log, Proton log and system information. slr-app1293830-t20210828T180524.log steam-1293830.log system_information.txt

X-m7 commented 3 years ago

I have a laptop with a discrete NVidia GPU now and using Optimus the game never goes beyond the splash screen. To start the game I use the following command line options: PROTON_LOG=1 __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia __VK_LAYER_NV_optimus=NVIDIA_only %command% When not specifying anything the game defaults to the internal Intel GPU and the game seems to start i.e. it goes beyond the splash screen but the game window just stays black and has to be killed from another machine via ssh since the machine is running but the X server is not responding.

Seems like a common theme with Optimus, I still have that issue too, gets further with Intel than with NVIDIA, although in my case I was running Wayland with Intel (switched to X11 for NVIDIA via nvidia-xrun), and with that it didn't freeze, I could hear the intro sounds and music, still black screen though.

More on my experience in my earlier comment.

coreybruce commented 2 years ago

I notice that not only is it really unstable but on my Nvidia card using the latest driver (GTX 1060 6GB using 470.63.01) it will memory leak and use all my ram until all 16gb and lock my whole computer up making it unplayable.