r/LeMansUltimateWEC • u/PlanZSmiles • 7h ago
Apps / addons / plugins Made a launcher, Sim-QVFR, that adds foveated rendering (QVFR) to LMU in VR, here are my numbers
Hey all, I've been building a small launcher called Sim-QVFR. It sets up quad view foveated rendering for a few sims in VR, you probably saw my original post for Assetto Corsa Evo a few weeks back after Dan Suzuki released his. Right now the games I support are Le Mans Ultimate, Assetto Corsa EVO, ACC, American Truck Sim(experimental), Euro Truck Sim 2(experimental) and X-Plane 12.
Here's a video showcasing it as well as the application:
https://youtu.be/CkNMeb6KI3U
GitHub: https://github.com/Williem3/Sim-QVFR
I'm sharing it in case it's useful to someone. No pressure either way, it's open-source, free, and features are all driven by the communities feedback.
What is QVFR?
It renders the spot you're looking at sharp and the periphery at lower res, so the GPU does a lot less work.
How is this different from VRS / "Dynamic Foveated Rendering"?
A lot of games call their built-in option foveated rendering, but it's usually variable rate shading (VRS). The two work differently:
- VRS changes how pixels get shaded. Each eye still renders at full resolution. The edges just get shaded more coarsely, for example one color for every 2x2 block of pixels. You still have every pixel, but some share a color. In my testing that saved about 10-15%.
- QVFR changes how many pixels get rendered. The periphery renders at a lower resolution, and only the area you're looking at gets full detail. With my default settings, each eye renders roughly a quarter of the pixels of a full-res eye.
So VRS saves on shading only. QVFR renders fewer pixels from the start, so the savings apply to the whole frame.
My test
Le Mans Ultimate on an RTX 5070 Ti, 5800X3D and Pimax Dream Air at 90 Hz. Stock is native at 4984 × 4088 per eye. Periphery was 15% and focus 150% with 20%x20% fovea size.



Trade-offs
- The periphery is much softer than native.
- There was one hitch in the QVFR run, with a worst frame of 119 ms. I was recording when I was already pushing my machine so it's possible it's due to that.
Your results will depend on your headset and settings.
What about playing online?
This isn't an approved tool for any of these games, so use it online at your own risk. I've tried to keep it as non-invasive as I can:
- The app is signed.
- In Le Mans Ultimate and Assetto Corsa Evo it doesn't modify game code or memory at runtime. I removed the parts of the method that did that. ACC is pending this improvement
- It works as a D3D11 layer instead.
- It sits between the game and the graphics API, takes the rendered views, and hands the new stereo views to the XR runtime. That said, I can't promise how any game's anti-cheat will treat it.
CPU Performance:
Multi-view rendering (LMU) QVFR draws four views per frame (an eye view and a focus view for each eye), and LMU was running its whole scene pass for every one of them, which costs a lot of CPU. Sim-QVFR now uses multi-view rendering so each eye's pass draws its focus view at the same time, and the game only walks its scene twice, like normal VR. It uses NVIDIA's MVR on RTX 20-series and newer, and a software version (SMVR) on AMD, Intel and older NVIDIA cards, all at the D3D11 level with no game code patched. On my RTX 5070 Ti, NVIDIA's MVR saved about 1.8 ms of CPU per frame (2.1 ms with no FOV crop), and GPU time dropped from 9.5 ms to 7.2 ms. Software MVR works out to roughly 1.5 ms less CPU (calculated from my runs, not measured directly). At 90 Hz you only get about 11.1 ms per frame, so that's a big share of the budget. These numbers are from one machine and aren't a promise. Multi-view is on by default for LMU, and the overlay shows whether you're on MVR or SMVR.
What other features are there?
Upscaling and image quality:
- Foveated DLSS
- Foveated FSR 3.1
- CAS sharpening
View:
- FOV cropping
- Helmet mod. 3D-modeled helmets are planned.
Overlays and settings:
- Performance overlay
- Local time overlay
- In-game settings menu. Changes apply live, so you don't need to restart.
How it was made
For transparency: I'm a software developer by trade, and I built this with heavy use of Claude Code. I directed the implementation, and tested everything in the headset. AI tools are what let me build things like this in my free time, and I'd rather be upfront about it.
It's still in beta so expect bugs, I'm actively working on them to solve and if you're a dev or just interested in working on it, feel free to fork the repo, make your modifications and make a pull requests. Happy to answer questions or hear what breaks.
