VerifiedShow Details
Unknown
Por algum motivo não consigo calibrar os pedais e a rotação do volante
Em minha maquina tive problemas com o ProtonGE onde a fisica ficava estranha, impossibilitando correr no online (isso também acontecia no Project Cars)
Some crackling audio from time to time. Pretty rare.
Despite being listed as a native Linux game, you need to run it using Proton. Using the latest Experimental/Hotfix build worked perfectly for me, no issues. My Logitech G29 works perfectly too, including the shifter add-on and force feedback.
the game is really heavy on CPU, you can slightly improve battery life by setting TDM limit to 11 W
dotnet 4.7.2 for CrewChief
I followed this guide: https://gist.github.com/srlemke/73850b6dad8f98046a6852ac4df021f4 Im sure there is some way to get it working on newer proton versions, but I couldnt do it. Once I got Oversteer, setting up my T248 was easy (I couldnt compile it myself unfourtunatly, so I just grabbed it from Open Build Service). Not sure how Native AMS2 works though
Runs like native (Yes, I know there is a native Linux version)
Haven't tested the native Linux version because I'm not sure if it's still being updated like the Windows version and AMS 2 is a multiplayer experience for me firstly, but there are zero problems with running the Windows version under Proton Experimental. Buttery smooth and no graphical glitches or bugs introduced by Proton.
gamemorun %command%
Résolution : 5120X1440
lowered FPS
impossible to read, this is a simulator, after all
Force Feedback on my logitech G920 works without any major issues. There is no need to install custom drivers.
My Logitech G920 does the engine simulation rattling thing at times while in menus. I'm unsure if this also occurs on windows, as i've only played on linux. It is not really much of an issue
With minimal effort (though not zero) all my input devices work and the game peforms very well.
As with most games I play using swaywm (wayland tiling window manager based on i3) I need to run steam it self in gamescope to get the window to appear on the correct display. Other than that things are fine.
My Heusinkveld Ultimate+ pedals are not detected but this is not unusual for proton games. I use xboxdrv to map them to two virtual xbox controllers. Gas and Brake on one, and Clutch on the other. This works well and no other fiddling is required.
See https://github.com/ValveSoftware/Proton/issues/5126# for details on problems with input devices which have no buttons.
I had previously made a "borked" review and this is an update to that. It turned out that I had accidentally saved a non-working input profile which was causing the game to crash on start when any input devices worked. This game does not use steam cloud so a reinstall fixed it, it just took me a while to figure that out.
After ~20 minutes of driving, the game would cause my entire system to crash to a black screen and lock up completely, requiring a power cycle to rescue it. No useful information in any log, temperatures and power draw were well within safe ranges every time. I tried narrowing down the cause myself by unplugging devices one at a time, using different Proton versions, changing graphics settings, and more. Nothing helped.
I picked this up during the summer sale since I have been really looking forward to this game for a long time. Hopefully by the time it goes on such a big sale again, whatever's causing my problem here will have been resolved. Wish I at least knew what the problem even was.
The pedals mapping were wrong (easily fixed in the controls settings). Force Feedback need drivers to be installed depending on wheel.
The pedals had wrong assignments (easy fix on controller settings), and the force feedback (Logitech G29) only worked after I installed berarma/new-lg4ff drivers (I'm using berarma/oversteer as well).
Game will start but only when controllers (t300rs, TH8A, Arduino Handbrake, Heusinkveld pedals) are disconnected.
Any combination of controllers connected via USB when attempting to start the game results in either a crash with the crash report window, or a flash of the startup screen followed by a silent exit.
When I disconnect all my controllers the game starts and runs perfectly, except for having to play with the keyboard...
Al hacer Alt+Tab el volante deja de funcionar.
No funciona con SteamVR.
Funciona perfectamente con un G29 usando pyLinuxWheel.
It does not work with VR. I tried also switch to older version: 6.3-8
VR: The game starts but it is frozen at start, it does not continued to the screen menu
Alt-tab during start up will cause the game to crash. Alt-tab in general (could) cause FFB not to work
This game ran way better than I expected, with one exception. Rumble seems to cause the game to slow down (braking, driving offroad). If you turn controller vibration completely off in control settings, the issue goes away.
This is unfortunately also a problem on desktop, and in Project Cars 2 (same engine).
Movement slows down when breaking or other random events making it unplayable (framerate stays locked interestingly enough)
Game seems to works flawlessly, but after recent update, Logitech G29 pedals are not working anymore.
gamemoderun mangohud %command%
Logitech G29 pedal were not recognized properly
After recent update Logitech G29 pedals are not being recognized properly. I tried to delete old configurations and even reinstall the game but the pedals still don't work. Had someone found a solution?
Except for that, everything is working perfectly.
7.0rc3-GE-1 GloriousEggroll
Proton 6.3.8 would not detect the cluth pedal on my Logitech G920. All the other inputs worked fine. Wit Proton7.0GE everything works as expected
Game runs fine with occasional stutters and game logic slow downs, might run smoother with another Proton Versions
Game runs fine most of to time, but there is definitely some noticeable stutter every now and than even on low settings without AI.
The game logic seems to struggle from time to time leading to the game slowing down to slow-motion while still running at full FPS. Seems to happen a lot when driving on gravel, crashing or when a lot of AI cars are around you at the start of a race.
Everything works and runs great. Except Alt-Tab breaks FFB unless restarting the game
Alt-Tab works but breaks FFB unless restarting the game
Less likely to crash when playing at native resolution
Couple of times, graphical issue looks like the "Hall of Mirror" after I set resolution 1920 x 800 + Borderless, but not known for Recurrencibity.
Very rarely, stop drawing few seconds in driving. but not known for Recurrencibity
May crash in driving immediately after changing screen resolution.
pedals can't be configured on G29 setup
pedals can't be configured
I have a G29, wheel is recognized, but pedals can't be assigned. Clutch is recognized as throttle, brake and clutch not recognized.
pedals did not work properly
The game works flawlessly
I was able to play using my Logitech G29 Wheel, and it works perfectly. But I couldn't find any way to make the wheel's shift indicator leds work on Linux.
Worked out the box and runs great
Switching workspace caused a black screen on return. Does not happen when windowed. Very minor annoyance
Using a G29, pedals and H shifter with "new-lg4ff" driver. Everything works great and ffb is the best i have experienced in any racing game. Runs at 60fps with high settings on my ageing hardware
alt + tab is an issue as I am not able to return to the game after alt +tab. I just get a black screen
Perfect experience.
Using Logitech G29 wheel with https://github.com/berarma/new-lg4ff driver.
