Framework: R.E.A.L. VR catalog guide · Pair this article with the general PCVR performance guide.
Modern R.E.A.L. VR can put some of the most demanding PC games ever made into a headset.
That also means performance tuning matters.
In 2026, the framework includes technologies such as AER v2, DL(S)SS, and for compatible games DL(S)SS-RR, a stereoscopic fix for DLSS Ray Reconstruction.
This guide explains how to tune the framework without treating every game as if it had the same bottleneck.
First: understand the render workload
A normal game renders one camera view.
VR needs distinct views for the eyes plus strict latency requirements.
That means a game that runs at 100 FPS on a monitor is not automatically a 100 FPS VR game.
What is AER v2?
AER stands for Alternate Eye Rendering.
Instead of rendering both eyes as fully independent views every display interval, the framework alternates work between eyes and applies VR-specific reconstruction/compensation.
The goal is to make demanding flatscreen games practical without requiring native-VR rendering performance.
Why FPS numbers can be confusing
The framework's rendering model means you should not compare its reported game FPS directly with a native VR title without understanding how frames are distributed between eyes.
Judge the experience by:
- Head-motion smoothness.
- ghosting.
- frame consistency.
- latency.
- stereo stability.
DL(S)SS
R.E.A.L. VR includes stereo-aware work around DLSS in supported games.
Upscaling can be extremely valuable because headset resolutions are high.
However, very aggressive upscaling can create:
- Shimmer.
- unstable thin geometry.
- foliage artifacts.
- softness.
Use the least aggressive mode that meets your performance target.
DL(S)SS-RR and Ray Reconstruction
In April 2026, Luke Ross added a VR-specific fix for NVIDIA DLSS Ray Reconstruction.
Current examples include:
- Spider-Man 2.
- Star Wars Outlaws.
- Indiana Jones and the Great Circle.
- DOOM: The Dark Ages.
The framework automatically changes how the DL(S)SS fix operates when Ray Reconstruction is enabled in a compatible game.
Ray tracing warning
Ray-traced VR is brutally expensive.
The framework creator explicitly warns that even an RTX 5090 can struggle with path-traced VR.
For most users, treat full RT as optional.
Start with rasterized or reduced-RT settings.
Optimization order
Use this order:
1. Choose a realistic refresh target
Do not force 120 Hz simply because your headset supports it.
For heavy AAA mods, 72, 80, or 90 Hz can be more realistic.
2. Reduce render resolution
This usually produces the biggest GPU saving.
3. Reduce ray tracing
RT can consume enormous GPU time.
4. Reduce shadows and volumetrics
These are frequent heavy settings.
5. Use DLSS/FSR intelligently
Upscaling can recover performance while maintaining reasonable clarity.
6. Check CPU frame time
If resolution changes barely affect performance, you may be CPU-limited.
Quest wireless users: leave encoding headroom
The GPU may also be encoding the headset video stream.
A game sitting at 99-100% GPU usage can leave too little room for consistent wireless encoding.
Reduce game load slightly.
Driver problems
The R.E.A.L. VR creator has warned about NVIDIA driver regressions affecting advanced ray-traced VR.
Symptoms can include:
- Checkerboard patterns.
- flashing.
- grain/noise.
- one-eye artifacts.
The creator's recommended recovery sequence is:
- Clear shader caches.
- Reboot.
- Test another NVIDIA driver version if needed.
Benchmark the worst scene
Do not tune in an empty menu.
For each game, test the real stress case:
- Spider-Man: fast city swinging.
- Avatar: flying through dense foliage.
- TLOU: combat and effects.
- Indiana Jones: complex ray-traced interiors.
- Watch Dogs: driving through dense city streets.
Keep the game version stable
A game patch can break VR even when your PC configuration is perfect.
Record these details while troubleshooting:
- Game version.
- framework build.
- driver notes.
- last verified date.
Do not stack injectors during troubleshooting
Temporarily remove:
- ReShade.
- unrelated frame-generation hooks.
- overlay injectors.
- third-party graphics DLLs.
Establish one clean VR baseline first.
Public vs early-access framework
The current 2026 R.E.A.L. VR model provides:
- A free public version.
- An early-access version containing the newest game support/features.
Newly added games are intended to move to public support after about three to six months.
Always verify which track your game currently needs.
FAQ
What should I lower first in R.E.A.L. VR?
Render resolution and heavy ray-tracing options.
Should I always target 90 or 120 FPS?
No. Choose a stable target appropriate to the framework's rendering mode and your hardware.
Is DLSS useful in VR?
Yes, but overly aggressive upscaling can create stereo-visible artifacts.
Does Ray Reconstruction work in R.E.A.L. VR?
The 2026 framework includes a stereoscopic DLSS Ray Reconstruction fix for compatible games.
Why does my Quest stream look bad even when the game FPS is fine?
Your GPU or network may be struggling with video encoding/bitrate rather than game rendering.