Star Citizen - DA Air SLAM & Lighthouse — Share Your Settings

Hey all,

With Star Citizen’s VR support maturing (slowly!) through the 4.x Alpha builds, I wanted to start a proper thread for Dream Air users — both SLAM and Lighthouse versions — to share what’s actually working right now.

There’s a lot of scattered info but nothing consolidated for the Dream Air specifically.

My setup:
Intel i5-13600K (13th gen)
RTX 5080 (PCIe Gen 5)
64GB RAM
Dream Air SLAM

Even with this setup I’m seeing microstutters that persist even when dropping render resolution down to 0.6 in Pimax Play/Evo.

So clearly raw GPU grunt isn’t the whole story.

Please share if you can:
:desktop_computer: PC Specs
CPU (gen matters — 12th, 13th, 14th gen Intel or Ryzen?)
GPU
RAM (amount and speed)
NVMe gen (Gen 4 vs Gen 5 — SC is notoriously storage-heavy)
:goggles: Headset
Dream Air SLAM or Lighthouse?
:wrench: Tracking / Runtime

Are you running Pimax’s native OpenXR runtime?
Or routing through SteamVR via sboys’

CustomHeadsetOpenVR driver?
Which is giving you better stability and performance in SC?

:gear: Settings
Render resolution / supersampling in Pimax Play or the new Pimax Evo app
Fixed Foveated Rendering (FFR) or Dynamic Foveated Rendering (DFR) — is eye tracking holding in SC?
SteamVR Motion Smoothing on or off?
In-game SC video settings (resolution, quality preset, crowd density etc.)
Any frame generation in use?

Known problem areas I’d like others to weigh in on:
Microstutters in live builds — SC’s live Alpha builds have notoriously inconsistent frame pacing.

Are stutters worse in busy areas (stations, Pyro jump points)? Are they present even in quiet space?
USB bandwidth — SLAM users especially, are you running direct to a rear USB 3.2 Gen 2 port?

Running through a hub seems to cause tracking instability and codec failures.

Eye tracker reliability — Tobii dropout seems to correlate with codec self-test failures.

Is DFR staying locked during SC gameplay or dropping out mid-session?

Resolution sweet spot — what’s the highest render scale you can run without hitting the microstutter wall?

CPU bottleneck — SC is heavily CPU-bound. Is anyone seeing a meaningful difference between 12th/13th gen and newer Ryzen 7000/9000 series or Arrow Lake? I’m wondering whether a CPU upgrade would shift the bottleneck more than further GPU headroom at this point.

Feature request / wishlist (interested in others’ thoughts):

One thing that would massively help the setup process: if Pimax Play / Evo had a game + PC spec profile system — you select the game, input your CPU/GPU tier, and it pre-populates a recommended baseline config.

Right now there’s too much trial and error and the “correct” settings for an RTX 4090 + 14th gen setup are completely different from a 5080 + 13th gen one.

Would anyone else find that useful?

Keen to hear from anyone who has a genuinely stable, enjoyable SC VR experience on the Dream Air — SLAM or Lighthouse.

What does your working config actually look like?

2 Likes

CPU (gen matters — 12th, 13th, 14th gen Intel or Ryzen?)

CPU 13TH 13900KF

GPU

RTX 4090

RAM (amount and speed)

128 GB 5600

NVMe gen (Gen 4 vs Gen 5 — SC is notoriously storage-heavy)

4 Gen

On many current motherboards (especially those using AMD’s AM5 platform or Intel’s LGA1700), the primary PCIe graphics card slot shares its data lanes with the first M.2 slot for PCIe 5.0 NVMe SSDs. While the impact is not significant, it is something to keep in mind.

Dream Air SLAM or Lighthouse?

SlAM

Are you running Pimax’s native OpenXR

OpenXR

Render resolution / supersampling in Pimax Play or the new Pimax Evo app

Fixed Foveated Rendering (FFR) or Dynamic Foveated Rendering (DFR) — is eye tracking holding in SC?

Eye tracking works for me with quadviews

In-game SC video settings (resolution, quality preset, crowd density etc.)

Present is high - cloud medium

Any frame generation in use

DLSS

Are stutters worse in busy areas (stations, Pyro jump points)? Are they present even in quiet space?

USB bandwidth — SLAM users especially, are you running direct to a rear USB 3.2 Gen 2 port?

Yes with adapter

Resolution sweet spot — what’s the highest render scale you can run without hitting the microstutter wall?

Not tested

It works for me. There’s the occasional stutter in cities, but by and large, it runs very well at around 30 fps. Considering it hasn’t been optimized for VR yet, I’m satisfied—and impressed. I wouldn’t want to play it without VR anymore.