VR Performance Tweaks & Tips

Ok , thanks I didn’t know the status on that. Last time I checked he was supposed to borrow some other headsets internally and try to make them work with either SteamVR or OpenXR.

Regarding the rest: yeah I just wanted to respond, that just because someone implemented it for 2 other older games for free it doesn’t mean it’s easy( even with the help of AI ) . I have practically zero experience with game development, and in particular VR implementation , but you can hear sim devs struggle with proper VR support.
Anyway, the upgrade to DX12 definitely makes sense for various reasons and I hope we’ll see some beta builds available in 2027.

 

Maybe they will be able to increase the performance with it as it stands at the moment, its not long since they changed the graphics engine and I always feel that VR is not at the top of the list to fix.

 

I'd prefer to see the majority of dev effort spent on the DX12 code base, which should give real improvements to how it runs in VR for everyone

 

Yes, the point is very clear: someone needs to spend their time to implement this, it doesn't appear out of thin air just because people want it.

 

Anyone else getting microstutters again? I can't figure out what it is...Have tried process lasso, shader delete, cleanup utilities, in game settings tweaks.

 

It’s a problem with DX9 shaders and others ... It’s bad luck for us.
this may help, but there is little chance.
https://forum.kw-studios.com/index.php?threads/stutters.21000/
https://forum.kw-studios.com/index.php?threads/extremely-low-fps.21044/

 

RaceRoom mit VR zum Laufen zu bekommen ist ziemlich einfach
....wenn man weiss wie es geht. Es sind eigentlich nur wenige Schritte erforderlich. Ich habe viel getestet und mit dieser mehr als simplen Methode läuft RR auf meinem Mini-PC (AOOSTAR GEM 12+, 32 GB, Ryzen 8845HS, 5,1 GB) mit ext. RX 9060 XT mit 16 GB, verbunden über Oculink Kabel und eine Meta Quest 3s.

RR läuft stabil mit 90 FPS und super Grafik. Auflösung 4096x2112, und 1,8 fach Supersampling.

Einfach die beiden Dateien Zip-entpacken und in das x64 Verzeichnis von RaceRoom kopieren (vorher die openvr_api.dll umbenennen/sichern). Das war es eigentlich schon. RaceRoom startet ab jetzt über Meta-Link. Daher nachsehen, ob Meta-Link in den Einstellungen unter Allgemein als aktive OpenXR Runtime festgelegt ist. Wenn nicht, einfach die Schaltfläche aktivieren. Von nun an wird SteamVR umgangen, was die Einstellungen leichter macht, weil sie nicht mehr kollidieren. Daher läuft das System wesentlich stabiler.

Die Datei Opencomposite.ini kann mit einem Texteditor bearbeitet werden. Solte beim Start eine Fehlermeldung kommen, in der eine Zeilennummer angegeben ist, dann einfach die entsprechende Zeile löschen. Die Opencomposite.ini kann man auch ganz löschen, wenn es Probleme gibt. Dort stehen nur allgemeine Einstellungen, die vorgenommen werden. Möchte man Supersampling verwenden, dann einfach als erste Zeile: supersampleRatio=2.0 eintragen. Das stellt das Supersampling Auflösung auf 2. Läuft bei mir prima. Weil ich den Wert öfter geändert habe, habe ich ihn nicht in die Opencomposite.ini geschrieben, sondern als Startbefehl in den Eigenschaften von RaceRoom eingetragen. Mein kompletter Befehl latuet:
-vr 2.0 -refvr 0 -cefno-gpu und sollte auf jedem System funktionieren.

Wichtig: Allgemeiner Tipp
Unbedingt die VR Optimierung wählen und Schatten=aus oder niedrig, Partikel=niedrig, Fahrzeuge=10, Spiegel=niedrig
Diese Einstellungen müssen sein, weil sonst eine FPS Sperre die frames halbiert!

Ich habe mit "Process Lasso" die CPU und GPU optimiert. Wegen der alten Systemstruktur wird nur ein Prozessor-Kern für Berechnungen genutzt. Das ist das größte Problem von RaceRoom. Ich habe dort ein Profil für RacRoom angelegt, was ganz einfach ist. Hier Schritt für Schritt:

Prozess Lasso öffnen
Unter dem Diagramm ie Schaltfläche "Regeln bearbeiten"
Im nächsten Fenster: "anlegen"
Dann bei "installierte Spiele" RaceRoom auswählen und fertig

Einstellungen:
Wieder zurück zu "Regeln bearbeiten"
Rechtsklick auf das oberer Feld "Prozessorübereinstimmung", das öffnet ein Fenster, in dem man Kontrollieren muss ob folgende Optionen mit einem Haken versehen sind. Wenn nicht, einfach Haken setzen und alles andere abwählen.

Kontrolliere folgende Einträge:
- CPU/-Zugehörigkeit [2,4,6,8]
- CPU-Sets [2,4,6,8] Ordnet Prozesskerne dem Spiel zu. Nur gerade nehmen, ungerade sind langsamer!
- Prioritäten-Klasse [Hoch]
- I/O Priorität [Hoch]
- GPU-Priorität [Hoch]
- Effizienzmodus [Ein]
- Leistungsmodus [Ja]

Das optimiert CPU und GPU und lässt sie auf Höchstleistung laufen. Problem: Wenn nur ein Kern genutzt wird, dann langweilt sich der Rest der CPU und GPU und fährt die Leistung herunter. Im Zweifelsfall wacht sie zu langsam auf, was dann zu Rucklern führt. Die Windows APP "Prozess Lasso" ist übrigens kostenlos und ein muss für RaceRoom, um Beschränkungen in der Leistung zu beheben.

Das war jetzt mehr Text, als ich eigentlich schreiben wollte. Ich hoffe, dem ein oder anderen einen nützlichen Tipp gegeben zu haben. Viel Erfolg und dann noch mehr Spaß mit eurer neuen Grafik

 

Supersampling auf 2x hoch knallen? Das frisst doch massiv Leistung.
Stattdessen Schatten aus empfehlen? Da kann man doch gleich RR als Mobile Game spielen, Immersionskiller #1.
Und das mit den ungeraden Kernen kann nur eine fehlerhafte Beobachtung sein.

 

Hat mich auch gewundert, wo auf einmal die Leistung herkam, aber es klappt bei mir...

 

Translated by ChatGPT.

Getting RaceRoom Up and Running (The Easy Way)
Getting RaceRoom running properly is actually quite simple
…if you know how to do it

Only a few steps are required. I tested a lot, and with this very simple method, RaceRoom runs perfectly on my mini PC:

System:

• AOOSTAR GEM 12+
• 32 GB RAM
• Ryzen 8845HS
• 5.1 GHz
• External RX 9060 XT (16 GB) via Oculink

Performance:

• Stable 90 FPS
• Excellent graphics
• Resolution: 4096 × 2112
• 1.8× supersampling

Installation Steps

1. Unzip the two files.
2. Copy them into the RaceRoom x64 directory.
3. Before doing so, rename or back up the existing openvr_api.dll.

That’s basically it. From now on, RaceRoom will start via Meta Link.
OpenXR / Meta Link Setup

• Check that Meta Link is set as the active OpenXR runtime:
  • Meta settings → General → OpenXR Runtime
  • If not active, simply enable it.

This bypasses SteamVR, which:

• Prevents conflicting settings
• Makes configuration easier
• Results in a much more stable system

OpenComposite Configuration

• The file OpenComposite.ini can be edited with a text editor.
• If you get an error message on startup that references a line number:
  • Simply delete that specific line.
• If problems persist, you can delete OpenComposite.ini entirely.
  • It only contains general optional settings.

Supersampling
If you want to use supersampling, add this as the first line:
supersampleRatio=2.0
This sets supersampling to 2× and works perfectly for me.
Because I changed the value frequently, I did not put it in the .ini file.
Instead, I added it as a launch command in RaceRoom’s properties.

My full launch command:

-vr 2.0 -refvr 0 -cefno-gpu

This should work on any system.

IMPORTANT: Graphics Settings (Very Important!)
You must use these settings, otherwise an FPS limiter will cut your frame rate in half:

• VR Optimization: Enabled
  
• Shadows: Off or Low
  
• Particles: Low
  
• Number of cars: 10
  
• Mirrors: Low

These settings are critical for stable performance.

CPU & GPU Optimization with Process Lasso
RaceRoom uses an old system architecture and only utilizes one CPU core for calculations.
This is RaceRoom’s biggest performance issue.

I optimized CPU and GPU usage using Process Lasso.
Create a RaceRoom Profile (Step-by-Step)

1. Open Process Lasso
   
2. Click “Edit Rules” below the graph
   
3. In the next window, click “Create”
   
4. Under Installed Games, select RaceRoom
   
5. Done

Required Process Lasso Settings
Go back to “Edit Rules”

• Riggt-click the top field “Processor Affinity”
  
• A new window opens
  
• Make sure the following options are checked
  
• Uncheck everything else

Verify These Settings:

• CPU Affinity: [2, 4, 6, 8]
  
• CPU Sets: [2, 4, 6, 8]
  (Assigns CPU cores to the game – use even cores only, odd cores are slower)
  
• Priority Class: High
  
• I/O Priority: High
  
• GPU Priority: High
  
• Efficiency Mode: Enabled
  
• Performance Mode: Yes

This forces CPU and GPU to run at maximum performance.

Why This Matters
If only one core is used, the rest of the CPU and GPU idle and downclock.
Sometimes they wake up too slowly, causing stutters.

Process Lasso (Windows app) is free and, in my opinion, essential for RaceRoom to remove performance limitations.

Final Words
That turned into more text than I originally planned
Hopefully this helps one or two people with a useful tip.

Good luck—and enjoy even more fun with your new graphics setup!

 

Thank you for above, but its rearranging chairs on the Titanic..

RaceRoom arguably is already the lowest bar for quality graphics in SImracing currently, and having to turn it down so much further with all those settings to LOW makes it look like LFS.. (which now has a night time cycle...)

The correct and only answer here is Devs need to pull finger and drag the game forward 20 years.. time to release DX11/12 already.

 

UPDATE: Level VR up - using FXAA now.
I Tried the new FXAA and it´s change all! The new graphics in VR is insane now.

There's not much to complain about regarding the graphics in RaceRoom with VR.

Actually, this was my last attempt to get RR running properly with VR. I'd already tested every combination, and the image was always jagged and/or blurry. Then I read about FXAA and tried it again. WOW. The result was incredible! MSAA can be set to 2x without much loss of quality, and the supersampling can be set as high as possible, resulting in a beautifully crisp image at 75 FPS. Everyone has to test and find their own compromises; this is just a general guideline for how it could work. Of course, you have to make compromises depending on your system. For me, it runs on a mini-PC with an external GeForce RX 9060 XT/16GB, connected via Oculink.

The 9060 proved to be a real VR beast. AMS2 runs at 90 FPS with high to ultra settings. Great image, only slightly blurry in the distance. RR is even better now!
I have a super clear picture, sharper than AMS2! The settings are: OTT: Distortion Curve=High - Resolution=4040 - Sharpening=enable

in RR: MSAA2x - FXAA=ON! The FXAA seems to have been reworked and delivers a razor-sharp image... as far as possible. Shadows are all disabled, and for some, reducing the number of cars to 10 helps. Additionally, I start RR with the following launch option:

-vr 2.2 -refvr 0 -cefno-gpu

In terms of quality, I'm absolutely on par with AMS2! Try it out!

 

#Nauseumster

Those days are gone! With FXAA and MSAA 2x, I get razor-sharp graphics at medium to high settings with 75 FPS on my Quest 3s. I've only disabled shadows or set them to the lowest level. Right now, I even prefer playing RR because the image is so sharp and crisp.

If RaceRoom gets a modern multi-core engine and more weather options, it could be a huge success. They're taking it one step at a time, it seems...

 

What does -refvr 0 do? Do you get a stutter free multiplayer experience?

 

the issue is not the graphics as much as it is all the stuttering, i run a BEAST machine that plays everythig else i have at least 90FPS maxxed out, even ACE in VR maxxed out.. but R3E is a stutterfest even on low settings.

 

I would say the same thing

 

not saying this is a solution but can you try reinstalling the dx9 pack from microsoft

https://www.microsoft.com/en-gb/download/details.aspx?id=8109

after that i may be way off but can you make sure r3e isnt using any E cores

Andi

 

ill give it a try. but. i recently wiped and reinstalled windows to move my machine to a larger primary drive, adn both instance of windows and R3E are the same so far. That said my install was on a secodnary drive in steam so it was not wiped at its folder level, might do that too.

 

Thank you, Andi, I just tested it, it doesn’t change anything. For the CPU, I didn’t really understand, but the CPU is running at about 16% on average, the GPU at 76% but with some stutters. I managed to reduce the stutters with the FXAA and MSAA 2x options, and I turn off the feedback screen (the PC screen). But it’s still not normal.

 

confirm no change for me either, for reference in both regular and dxvk with triple screen and eveything maxxed my GPU is sitting at ~20% usage, in VR it jumps to only 45% usage (maxxed out graphics) or 35% (low graphics) so its not the GPU bottle necking, CPU is ~15-25% in all scenarios, but for some reason in VR even though not stressing my maching it stutters and microstutters irrespective of graphics settings.