Unknown
Back button > ESC Back button > Enter Trackpad behaves as mouse
All text is very small
Switch to bordered
Ensure sufficient storage space. In-game updates can crash the game.
Will run but may need multiple attempts to ensure updates have installed. Also needed to switch to bordered window otherwise could not launch from "race" button.
Finally before launch go to game properties > updates > Betas and select old version.
same issue with controller i have on windows - restarting the game fixes it every time though ?
runs better than on my windows partition - default graphics settings in both instances
Does not get past the launcher. Can't recognise the game files and thinks the game is not installed.
Game works, but with no FFB it's not really playable
FFB doesn't work
Tested with Moza R5 and moza-ff driver; I do have FFB in other games, including those that are running via Proton
Fonctionne parfaitement, tres agreable a jouer avec gyroscope !
Initial setup of packages can be slow but after that, the rest is fine. Except for menus...
Used CryoUtilities. Unclear if performance is worse without it
Assign a Back Grip Button to ESC and another for your keyboard assigned pit limiter. You can set two of the buttons to be gear up and down as well.
The settings can be difficult to read if your vision isn't brilliant but generally it is all alright.
Detailed and large maps can take a very long time to load but the average circuit track runs fine after it loads.
Workshop content and rFactor 2 made DLC addons are easy to install and run as long as you have the storage for it. Game can run with multiple AI drivers on a detailed track at 40+ FPS on mediumish graphic settings at native resolution. Although loading up the tracks can take a while, once the initial package extraction is done when you first install the game, boot up is quite quick. Menus are a big issue. If you use the touch screen, you often need to tap on a button twice for it to work. The exception is where you are tapping on an arrow key (such as in the car setup menu) where tapping on it once then tapping anywhere else on the screen activates the button. This behaviour is still weird and I would recommend using a mouse to navigate the menus. Considering the amount of keyboard shortcuts rFactor 2 uses, I would also recommend a keyboard although it isn't necessary. I personally don't use one but again, it can help.
I am using a Thrustmaster T300RS wheel with the hid-tmff2 driver. After Proton 5.13, Steam runtime - Soldier changed the way it dealing with input devices. So I have to downgrade to Proton 5.13.6.
It works out of box if you are not using a T300RS wheel and your controller driver has been installed correctly.
I had to edit Controller.JSON to fix inverted axis. I had to do the same on Windows, though.
I had to use new-lg4ff driver for my Logitech G29 wheel. Mouse is sometimes laggy in menus.
It may probably work without tinkering, but not with G29 wheel.
The UI will be alittle vague with 1280X800 resolution
memory will drain out with super big racetrack like nurburgring nordschleife. have to use less detailed texture for ram usage.
will loss any mouse input of keyboard respond on starting game update UI. must finish all the car / track / DLC update before game launch. In game update will freeze the UI.
on board UI and fonts will be too small at 1280X800 resolution
When using the default Proton, my Xbox One controller is detected but the game would not respond to any input. This is not a problem when using Proton GE.
I use Thrusmaster T300 RS. Newer kernels detect it correctly but rFactor was unable to do so. After installing this: https://github.com/Kimplul/hid-tmff2 it was properly detected and even FFB worked just like on Windows!
Vulkan for AMD
I have used MESA driver vulkan-radeon. I have tried amdvlk first but it gave me heavy performance problems (5-10 FPS). After switching to MESA driver there is very little performance overhead compared to Windows. See https://wiki.archlinux.org/title/Vulkan
I'm using Gamemode, disabled compositor when running games, and custom kernel.
I'm using Proton-7.0rc6-GE-1.
The game runs at 90+ at highest settings 5120x1440 without MSAA. I'm currently running the game with FSR at 3840x1080 with MSAA 8x at Ultra which runs at 100+ fps.
Runs poorly even on low settings, not near playable
Around 30 fps on lowest settings is not near playable for my hardware
performance is - for whatever reason - way too slow, unplayable with such low fps.
10-25 FPS with RTX3090
game is no playable
the game is unplayable, no textures and objects disappearing and appearing on the screen, all colorless with rare exceptions, I tried with experimental proton and 6...
the game is unplayable, no textures and objects disappearing and appearing on the screen, all colorless with rare exceptions, I tried with experimental proton and 6...
Кроме Post Effects вообще ничего для стабильной работы менять не потребовалось. Proton 6.3-5.
Потребовалось понизить Post Effects с ультра до высоких. ВСЁ.
Иногда игра рандомизирует багами интерфейса, например, в настройке управления моргают диалоговые окна "Подтвердите кнопку" (прочитать и назначить невозможно) или в гонке не реагирует ESC, чтоб попасть в меню - решается повторным запуском. Просто. Сначала я подумал, что игра не даёт поменять управление и не умеет автоматом переназначать уже используемую клавишу (типа "ищи сам, где она, и переназначай" - первый раз я дико бомбанул), но оказалось умеет - просто выше названный баг "холодного старта" мешал.
Мой дешманский руль подхватила легко, мёртвую зону можно настроить - красота.
Shows splash screen, then black fullscreen, then crashes
Used to be fine a few months ago on the same machine.
Shows splash screen, than black fullscreen, then crashes
Tried Proton versions all the way back to 3.7 plus all beta versions of the game. No go. Used to be fine a couple months ago.
Just install and away to the races you go, I didn't notice graphical glitched or performance issues
sometimes when enterign the game it crashes, just click play again and your in
for your wheel depending on if its logitech grab oversteer, if its fanatec go grab the driver from github also tested my steam controller and it worked as well
Game hangs at a white screen. After several restarts I reached one time the screen to enter my driver name, but afterwards it crashed again.
The DEV start option works, but is in the end a test drive.
No difference to run on windows10 same installation, same steam library
lot of stuttering
Average 80+ fps single player at Nürburgring 24h on high settings during night.
Crashed first time loading some tracks (worked after restarting game)
Force feedback works with G29 and the new-lg4ff driver
Running with max ingame settings and 3440x1440 i get 150+ FPS (even on Sebring) everything in Nvidia OpenGl settings un-ticked atm.
I need coolbits to lower my GPU mem by -100 or games in general can act up and freeze with my card, just a tip to try if you have strange issues. Thought any overlay would be asking for problems but the FPS counter seems to work right now in rFactor2.
because some tracks are running with lower than 10fps its not a good experience, other tracks might work, but way slower than windows also.
Only new modern tracks fall down to 10fps, older tracks run at 50% of WIN10 Performance, which is way too low for a simulator to use it.
i am in the dev team of rF2 and might transmit further information to help out.
Unknown(> 10 hours with Proton)Single- and multiplayer works perfectly. Performance is at 60% of what Windows provides. Force feedback and racing wheel support is highly vendor specific on Linux.
Unknown(> 10 hours with Proton)
Single player works straight away in 4.2.2, in 64-bit. Previous version didn't work for me, even when forcing 32-bit. I played a bit with a PDP Xbox One controller. Vibration didn't work, but I don't think that's Proton's fault. Multiplayer not tested.
