VerifiedShow Details
Unknown
Con el proton por defecto funciona casi todo menos el online, que no une a la sala, el resto perfecto. Cambie a Proton GE y 0 problemas.
Flawless with default Proton.
It supports Ultrawide but not with the correct 21:9 aspect ratio, so it looks stretched horizontaly.
Works great out of the box! Wireless Xbox One controller doesn't work on menus, but works great in the actual game while driving.
As mentioned in my previous entry, I had to install some things to get my wireless Xbox One controller to work as I hate playing fighting/driving games without a controller, here's a list of links I used and it worked flawlessly for me, minus the fact it didn't work in menus which I don't think is a Linux issue as on Windows 10 I don't think it worked either:
This is the link for the software needed to get the Xbox dongle to work correctly: https://github.com/medusalix/xone
I had to install this to get the Xbox controller working: https://github.com/atar-axis/xpadneo
I had to install this to extract the firmware: https://packages.ubuntu.com/jammy/amd64/cabextract/download
Steps to get Xbox One wireless controller working through USB dongle and NOT bluetooth, Note: all commands are between the quotes " below:
Unplug your Xbox devices.
Clone the repository using the following command in your terminal: "git clone https://github.com/medusalix/xone"
Install xone: "cd xone sudo ./install.sh"
Download the firmware for the wireless dongle: "sudo xone-get-firmware.sh"
Plug in your Xbox devices and follow the pairing instructions per Microsoft's documentation: https://support.xbox.com/en-US/help/hardware-network/controller/connect-xbox-wireless-controller-to-pc
Powertools decky plugin: 4 Threads, default frequency limits on a cpu(I likely forgot to adjust those); GPU: 400-400 MHz(I play with SSAA x8, x4 might be sufficient). I would say play around with the TDP setting(maybe the gpu will run at ?200mhz without the minimum clock set to 400?), play around with cpu frequency limits. I'm also not really sure if doing 400MHz on memory(in actuality: 400MHz -> 3200MT/s, 1600MHz vs 667MHz -> 5500MT/s 2250MHz). Undervolted steam deck(-10/-50/-50).
Sometimes audio blasts at an elevated volume.
When restarting the race continously/waking the device from sleep the engine sound might go missing. Going back to the game menu and back to the race might help.
The official control scheme doesn't work, because the game doesn't detect the controller. I also don't mind using the sticks for acceleration/deacceleration like the default control scheme sets them, but if they don't use triggers, they should have been seperated at the very least.
Random audio blasting/eardrum piercing as said before. Usually happens once per game-session, it could be my steam deck's undervolt settings -10/-50/-50 mv.
Works great on the latest version of Wine-GE.
Had to map the controllers manually, in the games menu.
I had to use my ~/.wine prefix (any stock wine prefix would have probably worked) inplace of protons default one to get around an instant crash to desktop issue.
Some change in button setting was necessary to split Accelerate and Nitro/Launch
I could not make it work with an external controllers (bluetooth XBox or wired Logitech) even though all other games play well with it. Therefore playing on a big TV screen was not possible.
Reassigned a button for nitro/launch - for some reason it was the same as general throttle
Once there was an issue with crackling/song speedup after waking up from sleep mode
Sound plays flaky. Had to fiddle with the game config. You can open that config passing -setup after %command% in the launch options.
I changed in game config the following to fix stuff:
- Sound Output: Windows Multimedia Waveout
- Sound Driver: PulseAudio
- Mixing Rate: 44khz
Need to map buttons in menu and Steam Input (Start/A = Enter, X = Del, B = Escape)
Some collision impact noises initially play at an extremely loud, probably unsafe volume
WINEDLLOVERRIDES="dinput8.dll=n,b" %command%
You can apply widescreen fix and add fix online multiplayer with openspy.
Widescreen fix: https://github.com/ThirteenAG/WidescreenFixesPack/releases/tag/flatout2
openspy fix: https://github.com/DCxDemo/Flatout2.SteamOpenSpyFix/tree/1.0
Note that the openspy fix requires the widescreen fix to be installed. The launch options are needed to make wine load the widescreen fix dll correctly
Works well. No crashes during my watch including multiplayer.
To play online replace FlatOut2.exe with the one which connects to OpenSpy instead of GameSpy (not a Proton issue, applies to any OS)
Works out of the box.
Proton 7.0-5
Everything has to be manually bound once
The game only supports gamepads duing the races. Menus require the keyboard. So you have to map the arrow keys to the d-pad and escape and enter keys to the grip buttons. Then you need to go to the control options and map the sticks and trigger for racing.
After all that, the game works fine, except there is no vibration feedback even if you have that option enabled.
As long as you use a custom controller profile, it works. Doesn't work with the default controller profile.
In game changed throttle and brake to right and left trigger respectively
PROTON_LOG=1 PROTON_USE_WINED3D=1 %command%
Proton log: https://pastebin.com/7UPF2iRS
Proton: 1603141982 proton-5.0-10b
Options: {'forcelgadd', 'wined3d'}
Silent crash, no error
Proton log: https://pastebin.com/4xcvq8Sb
Options: {'forcelgadd', 'wined3d'}
Proton: 1603141982 proton-5.0-10b
Silent crash and no error
Silent crash instantly
PROTON_USE_WINED3D=1 %command%
Silent crash instantly
1650552288 proton-7.0-2
Silent crash after 1 second
I have no idea what it can be. Game files and tool files have been verified without errors.
1645632810 proton-7.0-1b
Using the back grip buttons for the "escape" key and "enter key". Also changed the left trackpad for arrow keys so I can navigate menus before a race.
Changed resolution to 540p, enabled FSR to upscale back to 720p. At 60FPS with a 3w~ TDP limit via gamescope, it stays locked at 60FPS 99% of the time and you can play for up to 5.5 hours. Total system power draw is 8w~ on average.
Sometimes audio fails to play for your car's engine sounds. Not sure if this is a game bug or proton bug. Also once when resuming after a day of sleep mode, the audio was all crackly. Restarting fixed it. Otherwise all audio plays fime.
You have to manually map controls in-game, takes maybe 5 minutes. You only have to do this once.
The actual game runs like native. Only slight problem is the 1st time launch.
Upon 1st pressing play it opens the settings window just like on windows. After selecting your settings and pressing play the game crashes. Launching the game again doesn't open the settings window and launches the game instead with the selected settings.
Flawless!
You will need to manually map buttons for the Xbox 360 controller.
This game runs perfect with Proton and has excellent performance.
Works like charm
You need to remap controllers. Menus don't detect controller imputs but its a general problem and races work as normal.
Runs flawlessly out of the box
Just hit play and enjoy! Also, it works fine with the widescreen patch.
Runs pretty smoothly.
Sometimes the tire skid sound doesn't stop, or you hear another driver eject from the window from the other side of the map, in two races my car had no engine sound.
Cars go boom
Just kidding, runs out of the box
