Proton
Proton copied to clipboard
ValveSoftware
Assetto Corsa EVO (3058630)
Compatibility Report
- Name of the game with compatibility issues: Assetto Corsa EVO
- Steam AppID of the game: 3058630
System Information
- GPU: NVIDIA RTX 3070 Ti
- Video driver version: 565.77
- Kernel version: 6.12.7-200.fc41.x86_64
- Link to full system information report as Gist: https://gist.github.com/kropop/662464c030a490654c4e3b5bf0d9bd8c
- Proton version: Proton Experimental
I confirm:
- [ x ] that I haven't found an existing compatibility report for this game.
- [ x ] that I have checked whether there are updates for my system available.
Symptoms
-Game launches properly with no steering wheels connected. -Once I launch the game with my Fanatec CSL DD and my Thrustmaster T-LCM Pedals connected, the game spawns the window, then crashes. -Launching the game first THEN powering up the device does not crash the game.
-Force feedback is missing. I can bind all analog axes just fine.
-Severe stuttering.
Reproduction
-Connect a steering wheel and pedals to the PC -Start the game
Game's crash log: https://gist.github.com/kropop/a16fefbb42ee366c3b045cfcba52e350 Proton log: https://gist.github.com/kropop/e237aad755e3ff9bffa63081b3acd713
Hello! I did not have that problem with the game, but my wheelbase and pedals are different. OpenFFBoard + FreeJoy pedals + GT Neo all connected and detected by the game, without issues. Force Feedback also working.
But i have another issue: graphical artifacts present, look like polygons glitching on car interior, dashes and mirrors Also tried various graphical settings and RADV_DEBUG=nodcc, without luck. These artifacts does not appear on any other game, so GPU is not a problem.
Video with artifacts: https://www.youtube.com/watch?v=Yb-y3J-lbbo
Another user with Nvidia GPU reports that game is working without any artifacts.
Looks like Mesa/DKVK issue?
GPU: AMD Radeon RX 6900 XT Video driver version: Mesa 24.2.8-1, AMDVLK 2024.Q4.3 Kernel version: 6.12.6-1 Link to full system information report as Gist: https://gist.github.com/JacKeTUs/56c34143883c3e2661f30d1e800e5058 Proton version: Proton Experimental, but also tested Hotfix, 8.0-5, 9.0-4, GE-Proton9-22
UPD: I tested with AMDVLK, 2024.Q4.3, artifacts are present as well. Performance is worse, 30fps vs ~120 fps on Mesa UPD: no changes with new update (0.1.1) UPD: no changes with new update (0.1.2)
Replying to https://github.com/ValveSoftware/Proton/issues/8395#issuecomment-2596293883
I hear the game is working fine on Steam Deck without artifacts, and I believe for other RADV users.
I won't be able to play until I get home, so I will have to test later, but I am using the latest Mesa version (Kisak PPA).
Replying to https://github.com/ValveSoftware/Proton/issues/8395#issuecomment-2596293883
I have tested on ChimeraOS same artifacts here. I have a problem with OpenFFBoard the buttons not work very well. Performance are not the best but i have the minimum hardware required.
Replying to #8395 (comment)
I have tested on ChimeraOS same artifacts here. I have a problem with OpenFFBoard the buttons not work very well. Performance are not the best but i have the minimum hardware required.
In that case, I guess someone could file a bug report to Mesa about this?
Hello
Once I launch the game with my Fanatec CSL DD ... the game spawns the window, then crashes.
This is a known bug which affects a couple of games that come with the FanatecSDK. In short, it seems that the wheel detection of FanatecSDK throws an exception when it finds a compatible wheel but it cannot really talk to it.
This is why I'm working on supporting a hidraw mode for Fanatec wheels, which allows the FanatecSDK to talk to the wheel 'the same way' like in windows, see https://github.com/gotzl/hid-fanatecff/pull/86 and this comment https://github.com/gotzl/hid-fanatecff/pull/86#issuecomment-2365175089. With this branch of the driver, and the posted proton version, I'm able to run ACE and I get FFB/LEDs ...
I confirm same visual artefacts than @JacKeTUs 6950XT with Mesa 24.3.3
And I also confirm that hidraw branch of fanatec driver made by @gotzl makes FFB and LEDs works perfectly
I can also confirm the new fanatec driver makes my wheel work perfectly, with one caveat: it is detected as "Thrustmaster Sim Pedals", so I have two devices using the same name, but one of them are the actual pedals, the other one is my Fanatec wheel. This peculiar issue is also visible in ACC with this Proton version.
I still get a lot of stutter, making the game unplayable completely. I don't see any visual glitches, though.
Once I launch the game with my Fanatec CSL DD ... the game spawns the window, then crashes.
What I think. ACE detects Fanatec gear and auto enables Fanatec SDK (on ACC it's Fanatec LED's (schreenshot bellow). That's why only https://github.com/gotzl/hid-fanatecff/pull/86 works.
Tested with different proton versions, all of them crashes (if Fanatec gear is connected). Without Fanatec, it starts with no issues. And the biggest issue here, there is no ability to turn OFF Fanatec SDK (Fanatec LEDs).
And I can confirm a lot of stutters. This happens always in the same place on track. For example on Brans Hatch first corner, then third one. On back straight near arch. When stutters happens GPU load drops to zero, and then jumps back to full load.
Just clicked play and the game works but there are graphics issues like these:
Tried running Proton Hotfix and ProtonGE-22, lowest settings and even a different pp filter but the issue still shows up.
After messing with graphics settings it's fine for a couple of seconds and then goes back to having issues again.
System Specs:
More discussion also about my issue on Reddit / other peoples' experience: https://www.reddit.com/r/linux_gaming/comments/1i2vgb5/graphics_issue_on_ac_evo_with_fedora_linux_nvidia/
Is any contributer here able to tell us if the graphical bugs on AMD are a RADV problem or possibly a problem with Proton/vkd3d-proton?
Replying to https://github.com/ValveSoftware/Proton/issues/8395#issuecomment-2598384872
You're using an older Nvidia driver, so upgrade to the latest one (in this case, 565) if possible.
I have some graphic artifacts that you can mainly see on the cockpit of the cars. Specially on the mirrors and infotainment area. It also happens on the bonnets from the outside camera.
Operating System: Arch Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.1 Kernel Version: 6.12.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 6600 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7B84 System Version: 2.0
I have no apparent graphics problems, but the performance is very bad with constant stuttering. I'm not sure but I thought I read somewhere that a recent update removed the rare artifacts.
AMD® Ryzen 7 5800x 8-core processor × 16 GeForce RTX 3070 (555) 32GB DDR4 3200
I can see my resource usage go up and I am able to hear the main menu song, but no window appears for me.
11th Gen Intel(R) Core(TM) i7-11800H GPU: Nvidia RTX 3060 laptop (565.77) 16GB DDR4 3200
proton log: https://gist.github.com/superboss2300/2363cf708613a401347317fada635b13
Had to do this or it wouldn't work:
sudo sysctl --write vm.max_map_count=1048576
Replying to #8395 (comment)
You're using an older Nvidia driver, so upgrade to the latest one (in this case, 565) if possible.
I've updated to the latest production driver 550.144.03 and tried a different map as well and it's still happening. Using Proton Experimental.
It initially starts off fine
And after some time it's just horrible - for some reason this time it's a completely different effect.
Replying to https://github.com/ValveSoftware/Proton/issues/8395#issuecomment-2614578201
Well with games, you're better off with the beta drivers like 565
Losing FFB in Assetto Corsa Evo when at limit (Thrustmaster T300RS)
Issue
When playing Assetto Corsa Evo (early access v0.13) when reaching maximum force the FFB just completely drops to zero (-1 in logs).
For example driving around a corner, when at about the grip limit/getting understeer the wheel instantly loses all FFB for a short period of time (ranging from very short to about a second or so). Sometimes there was a "knocking" effect where FFB would drop and activate 2-4x a second while driving around a corner.
To avoid reaching maximum FFB it is possible to reduce the ingame FFB strength to about 60-65. This does not work by reducing the FFB gain in Oversteer.
Other games (Assetto Cora/Automobilista 2/native BeamNG.drive) do not have this issue, nor does it occur on Windows.
Logs
The ffbwrap logs show that the force drops to -1 instead of reaching at 32767 (no occurrence of 32767): FFB_ACE.log-20250126122545_bug.log
000094499695 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:-32614 attack_length:0 attack_level:0 fade_length:0 fade_level:0
000094499701 < 0 id:0
000094502707 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:-31382 attack_length:0 attack_level:0 fade_length:0 fade_level:0
000094502715 < 0 id:0
000094505716 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:-1 attack_length:0 attack_level:0 fade_length:0 fade_level:0
000094505722 < 0 id:0
000094508696 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:-1 attack_length:0 attack_level:0 fade_length:0 fade_level:0
While the log from Assetto Corsa (via Content Manager) does not show this behavior and reaches 32767: FFB_AC.log-20250126144719_normal.log
000035919049 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:31593 attack_length:0 attack_level:0 fade_length:0 fade_level:0
000035919056 < 0 id:0
000035922066 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:32767 attack_length:0 attack_level:0 fade_length:0 fade_level:0
000035922076 < 0 id:0
000035925110 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:32586 attack_length:0 attack_level:0 fade_length:0 fade_level:0
000035925120 < 0 id:0
000035928067 > UPLOAD id:0 dir:16429 length:0 delay:0 type:CONSTANT level:32767 attack_length:0 attack_level:0 fade_length:0 fade_level:0
How to reproduce
FFB gain 100% in Oversteer and ACE (with Thrustmaster T300RS). Driving with Mazda MX5 at second gear redlining and steering either fast in a direction or just taking a corner at about the steering limit.
Tried
Changing Proton versions Installing Thrustmaster driver into prefix ffbwrap --offset-fix --update-fix
@Pengukov, that issue lies both in game and in wine. And Wine team today approved my patches for this. https://gitlab.winehq.org/wine/wine/-/merge_requests/7161 https://gitlab.winehq.org/wine/wine/-/merge_requests/7217
TLDR: game doesn't properly scale Magnitude values, and sends values over documented 10k. Wine doesn't properly scale them and returns -1 instead.
Will update my ProtonGE with latest patch version and issue will be resolved in it.
I have a similar problem with Pista Motorsport. I fixed it lowering FFB to 50%. I hope this patches work also with this game
@JacKeTUs just tested your GE-Proton release from last week, seems to be working fine. Guess I'll use that for the time being. Thanks for your work. @leillo1975 you could also test the release from JacKeTus from here https://github.com/JacKeTUs/proton-ge-custom/releases/tag/GE-Proton9-23-FFB
tested your GE-Proton release
It lacks latest fixes for saturation value for condition effects. It will be just enough for correct values, but as you clearly saw, AC Evo may set some values incorrectly 😄
I will update this build soon, but i would call it temporary solution at best.
@JacKeTUs just tested your GE-Proton release from last week, seems to be working fine. Guess I'll use that for the time being. Thanks for your work. @leillo1975 you could also test the release from JacKeTus from here https://github.com/JacKeTUs/proton-ge-custom/releases/tag/GE-Proton9-23-FFB
I can confirm that this Proton-GE fork works great and now I don't have the FFB problems described on previous messages. Also works great on Pista Motorsport.
It would be great to fix the stuttering problems that make this title unplayable, although I don't know if it's due to Wine/Proton, or the game itself. I've tried the trick of setting the Texture Size Pool to Ultra, but it works sometimes, sometimes not. It also often happens that it gets stuck on the loading screen and you have to kill the process to exit.
I am still having a lot of problems. Since the last patch 0.1.4 I can't fix the stuttering if I set the Texture Size Pool to Ultra (with the past version worked). Now the game stalls always when loading the race, and only responds if I delete the prefix and regenerate it, but when I close the game and reload it, the same thing happens again, as if something is corrupted in the prefix. I don't know if it happens to any of you?
@leillo1975 I had this, but I'm not sure it was with 0.1.3 or 0.1.4
And you don't need to delete all prefix, try to remove video settings file video.videosettings from <..>/SteamLibrary/steamapps/compatdata/3058630/pfx/drive_c/users/steamuser/Documents/ACE
Thanks, I'll check it out as soon as I get home, and then I'll let you know how it went. Were you able to correct the stuttering?
@leillo1975 I had this, but I'm not sure it was with 0.1.3 or 0.1.4
And you don't need to delete all prefix, try to remove video settings file
video.videosettingsfrom<..>/SteamLibrary/steamapps/compatdata/3058630/pfx/drive_c/users/steamuser/Documents/ACE
Your workaround is good! I created a backup of a working config and when I get a hang , I restore it and then the game works again. I also test the last bleeding-edge proton Experimental, and now I have no stuttering (I didn't tried with other Texture Size Pool setting than Ultra). The only problem is that I can't use the @JacKeTUs proton-ge mod to avoid FFB problems
I also test the last bleeding-edge proton Experimental, and now I have no stuttering
I can confirm. Still few really tiny stutters per LAP. But is totally drivable.
Texture Size Pool setting was Height