- Joined
- Aug 28, 2020
- Messages
- 83
- Reaction score
- 54
Installation
- rFactor 2 is only available through Steam
- You need a 64-bit version of Windows 7 or above (32-bit is barely supported)
- You need around 20 GB of space (please allow extra space for mods)
- DX9 - the most widely supported for mods, works very well
- DX11 - beta branch, limited mod support, but enables better graphics and VR - at the moment I advise against this version as it is unstable
Launcher
If you downloaded your mod through Steam Workshop, it is very likely that it will be installed automatically. For all other mods, you will have to manually check if they have been installed - if not, mark them and click install, on the bottom left.
Not all mods have to be installed, some are automatically downloaded when you join a server.
If a mod causes a problem, try to uninstall/delete it first. If that doesn't solve the problem, delete the corresponding files in "...\SteamApps\common\rFactor 2\Packages" & "...\SteamApps\common\rFactor 2\Installed".
You can tweak most, but not all, of the settings during a session (whilst in the garage). You can find all available settings in 'Singleplayer' > 'Options'.
Most leagues in rFactor 2 require your real name. To set that, do this:
Go to the start page of the launcher (house symbol) and on top right, you should see your steam name, click on it. Then you can set your real name and in the end press "Save Edits". As nickname I use "Blue Monkey".
Graphics
Select an ISI/Studio 397 Track (eg. Sao Paulo), set the grid to maximum, multiclass, night and maximum rain. Start the race and check your ingame FPS (eg. Steam Overlay). During driving it should be a minimum of 60 FPS.
There are no simple "this or that improves frame rates", you will need to experiment and see how each setting works for you.
We strongly recommend to set "Special Effects" & "Soft Particles" to off, as they can cause huge framedrops when someone locks up. And don't turn "Shadows" to max, as it can cause artifacting. For full livery details, go to "player.json" -> open with notepad, find "Opponent Texture Override" and set it to 3.
Here are though some other recommendations:
Lowering detail of cars in the garage:
In the player.json file, search for "Garage Detail". Default is 0.5, I set it to 0.01.
Lowering detail of cars on track, while keeping the liveries clear:
In the player.json file, search for "Opponent Detail" and make sure it looks like the following:
"Opponent Detail":1,
"Opponent Texture Override":3
This lowers the detail of the actual car model, while keeping the livery at high quality.
Maximum number of headlights:
Search for "Max headlights" in the player.json file
Change to whatever you want, I personally have it at 50, which is plenty. Default is 256.
Rear view mirror render distance:
Search for "Rearview_Back_Clip" in the player.json file. The number is the render distance in meters.
Issues with stuttering/screen freezes:
Incase you have issues with stuttering or freezing, search for "Use Thread" in controller.json and set it to true. It had no impact on performance in my case.
In the player.json file, search for "Garage Detail". Default is 0.5, I set it to 0.01.
Lowering detail of cars on track, while keeping the liveries clear:
In the player.json file, search for "Opponent Detail" and make sure it looks like the following:
"Opponent Detail":1,
"Opponent Texture Override":3
This lowers the detail of the actual car model, while keeping the livery at high quality.
Maximum number of headlights:
Search for "Max headlights" in the player.json file
Change to whatever you want, I personally have it at 50, which is plenty. Default is 256.
Rear view mirror render distance:
Search for "Rearview_Back_Clip" in the player.json file. The number is the render distance in meters.
Issues with stuttering/screen freezes:
Incase you have issues with stuttering or freezing, search for "Use Thread" in controller.json and set it to true. It had no impact on performance in my case.
Wheel Settings
First, load the correct profile in rFactor 2 - for a G27, the default force feedback settings are perfect. For your own particular wheel, check the RF2 forums for recommended settings or tweak them yourself. Here are our recommended keybindings:
- Check if the bars of throttle & brake & clutch are synced with your input
- Check in cockpit cam during driving if your wheel is synced properly
- If you use only paddle shifting, map a key to reverse
- Speed Limiter
- Brake Bias (F) & Brake Bias (R)
- Increment / Decrement Mixture
- Ignition & Starter
- Headlights
- Request Pits
- ABS & Stability Control & Traction Control
- Vote Yes / Vote No / Ping (for practice sessions)
- Camera Change
- Toggle Mirror (in case it bugs out)
- Toggle HUD / Stats, bind once to disable them
- Vehicle Labels
- LCD Mode & LCD Up/Down/Increase/Decrease (DPad recommended)
- Passenger select (Driver Swap)
Network settings guidelines
We strongly recommend you to change the network settings according to following guidelines, in order to ensure maximum stability, also in the view of driver swaps and servers with high traffic:
- Racing on WLAN or mobile phone connection is prohibited in most leagues due to possible lagspikes andor packet loss
- For determination of your internet speed, use a speedtest tool, as ie. www.speedtest.net - all results and following values are in Bits, not Bytes! 1 Byte = 8 Bits.
- You can ignore the setting "CONNECTION TYPE"
- You should NOT go below 512 Kbps on the "UPSTREAM" or 1 Mbps on the "DOWNSTREAM" - if you don't reach that speed, please do not race in multiplayer. Some racing communities are actually demanding a speedtest from you to see if you have a good enough connection.
- If you exceed 20 Mbps on either down- or upstream, we recommend to set the value simply to 20 Mbps, as more is just not needed in rFactor 2.
- Driver X reaches 800 Kbps down- and 200 Kbps upload speed in the speedtest - he is below the recommended minimum and should not race in multiplayer. He can still try though but most likely he will lose connection or the driver swap simply fails.
- Driver Y reaches 15 Mbps down- and 1.5 Mbps upload speed in the speedtest - he thereby sets the "DOWNSTREAM" to 15.0 Mbps and the "UPSTREAM" to 1.50 Mbps in rFactor 2.
- Driver Z reaches 300 Mbps down- and 30 Mbps upload speed in the speedtest - he thereby sets the "DOWNSTREAM" to 20.0 Mbps and the "UPSTREAM" to 20.0 Mbps in rFactor 2.
Additional files
For the SRC, it is recommended to use the "Ducker" plugin for Teamspeak, so you can always hear incoming whisper.
If you have any further questions, please do not hesitate to ask us. We're here to help
Your rFactor2 Staff Team