u/AstroGraphRacer

Hi everyone,
I have a question for Fanatec users. Pc / Iracing / AMS2 / Assetto corsa and Assetto corsa evo .
I can clearly feel road bumps and surface imperfections through my steering wheel, but I don’t really feel the kerbs (rumble strips).
Is this normal, or am I missing a setting?
I’d like to know:
Can you actually feel kerbs with your Fanatec setup?
Which Fanatec wheel base and steering wheel are you using?
Which game are you playing?
If you can feel the kerbs, what settings made the biggest difference?
I’m trying to understand whether this is normal behaviour with Fanatec hardware or if there is a setting that improves kerb feedback.

First, credit where it’s due: opening up the display pipeline and co-developing the native SteamVR driver with Sboys3 is great, and the idea of EVO as a testing ground that feeds features back into Pimax Play sounds good on paper.
But the messaging creates a real tension I’d like cleared up. Pimax says two things at once:
• EVO exists to make Pimax Play better — “when an EVO feature matures, it graduates into mainline Pimax Play for all users.”
• EVO “may introduce paid features in the future” (free for 6 months if you register during Early Access).
My questions to Pimax:
1. Will the features currently in mainline Pimax Play stay free, permanently?
2. When a feature “graduates” from EVO into Pimax Play, will it arrive free for everyone — or could it stay paywalled in EVO instead of migrating? In other words, is every EVO feature guaranteed to eventually reach Pimax Play for free, or only some?
3. On the native SteamVR driver (Sboys3) specifically — which of these is the plan? Please pick one:
(a) It graduates into mainline Pimax Play, free for all users.
(b) It stays an EVO feature and may end up behind a paid tier.
(c) No decision made yet.
4. Is there any plan, now or later, to deprecate or limit standalone tools (like Sboys3’s CustomHeadsetOpenVR) through a Pimax Play update?
I’m not assuming bad faith — early-access-paid-then-free is a normal model. But “may go paid” is vague, and on $2000+ hardware people deserve a clear commitment about what stays free. A straight answer, especially on questions 2 and 3, would go a long way.
Thanks.

Setup: Pimax Dream Air (Lighthouse), Pimax Play 2.0.1, seated.
When I launch Pimax Play and enter the home environment, I end up facing the window in my room. The console/panel that should be right in front of me is behind me instead.
How do I get the home environment to face me correctly, so the console is in front of me? Thanks.

First, credit where it’s due: opening up the display pipeline and co-developing the native SteamVR driver with Sboys3 is great, and the idea of EVO as a testing ground that feeds features back into Pimax Play sounds good on paper.
But the messaging creates a real tension I’d like cleared up. Pimax says two things at once:
• EVO exists to make Pimax Play better — “when an EVO feature matures, it graduates into mainline Pimax Play for all users.”
• EVO “may introduce paid features in the future” (free for 6 months if you register during Early Access).
My questions to Pimax:
1. Will the features currently in mainline Pimax Play stay free, permanently?
2. When a feature “graduates” from EVO into Pimax Play, will it arrive free for everyone — or could it stay paywalled in EVO instead of migrating? In other words, is every EVO feature guaranteed to eventually reach Pimax Play for free, or only some?
3. On the native SteamVR driver (Sboys3) specifically — which of these is the plan? Please pick one:
(a) It graduates into mainline Pimax Play, free for all users.
(b) It stays an EVO feature and may end up behind a paid tier.
(c) No decision made yet.
4. Is there any plan, now or later, to deprecate or limit standalone tools (like Sboys3’s CustomHeadsetOpenVR) through a Pimax Play update?
I’m not assuming bad faith — early-access-paid-then-free is a normal model. But “may go paid” is vague, and on $2000+ hardware people deserve a clear commitment about what stays free. A straight answer, especially on questions 2 and 3, would go a long way.
Thanks.

Je n’ai jamais jouer à PMR à cause de la VR je l’ai depuis le début . Mais tant qu’elle ne sera pas là impossible pour moi je de m’y mettre ! On y il prévu une date ?

When I launch Custom Headset by SBoys3!

I have the launch logo with “Launch Dream Air headset” written on it. When I press it, it does take control of Pimax Play and opens SteamVR, and it gets replaced by “Cancel Launch”.

The problem is that I feel like I’m not in sync with the Sboys3 software at all anymore

My runtime is correctly set to SteamVR.

But after a few moments, the Custom Headset driver shows me “Launch Dream Air headset” again.

Hey everyone,

I’ve got a Pimax Dream Air and I’m a bit confused about how the eye tracking actually works.

I enabled it in Pimax Play and calibrated it there. But now I only use sboys3’s Custom Headset software, not Pimax Play directly.

So my questions are:

•	How can I tell whether the eye tracking is actually running?  
•	Are there settings I need to turn on somewhere?  
•	Do I need to configure anything in-game for it to work?

Honestly, what I’d love is something simple — ideally I’d just tell the headset to do it and not have to touch anything else. Is that possible, or does it always require manual setup?

Thanks in advance for any help.

Hey community! I wanted to publicly thank Sboys3, who developed exclusive software for the Dream Air and helped me configure it properly. It’s truly a game-changer.

The Context: Crystal Light vs Dream Air

Before, I had a Pimax Crystal Light with 2880 x 2880 pixels per eye at 90 Hz on a QLED plus Mini-LED display. Even with a very powerful PC (RTX 5090 32 GB, Ryzen 9 9800X3D, 32 GB RAM), I was still graphically limited — impossible to push settings to the max in demanding games.

Today, with the Dream Air, I have 3840 x 3552 pixels per eye at 90 Hz on a Micro-OLED display. It’s better technology, but that’s not what changes everything.

The Real Game-Changer: Sboys3’s Software

Sboys3 created rendering-optimized software exclusively for the Dream Air. This tool is what truly unlocks the headset’s power.

Before: Crystal Light, no access to this software equals graphical limitations even on powerful hardware.

Now: Dream Air plus Sboys3’s software equals insane performance with the same PC and components.

The Concrete Numbers

With the same processor and graphics card:

— iRacing: 90 FPS stable, GPU at only 60 percent, ALL graphics settings maxed out. Impossible with the Crystal Light.

— Flight Simulator 2024: ultra settings, 45 FPS stable, GPU at 88 percent. The game still has headroom.

The Thank You

Thank you Sboys3 for this software and for helping me configure it correctly. You’ve truly revolutionized what we can do with the Dream Air.

Hi all,

Pimax Dream Air here, running the Custom Headset software made by SBoys3.

There’s a small physical button under the left eye that’s supposed to raise/lower the headset volume. The button is there, but I can’t actually get the volume to go up or down with it.

Trying to figure out where the problem is:

•	Does this volume button work for you under SBoys3’s Custom Headset, or only under Pimax Play?  
•	Is it a known limitation of Custom Headset (volume button not supported / not mapped)?  
•	Any setting, firmware version, or remap I should check to get the button working again?  
•	Worst case: how do you adjust volume instead (Windows mixer, default audio device, in-game)?

Setup: Dream Air, pure PCVR/VR, used mainly for sim racing.

Thanks — just want to know if this is expected behaviour with SBoys3’s Custom Headset or something on my end.

Hey everyone,

I’ve been experiencing a frustrating issue with Custom Head 7 from S.Boys 3 on Automobiliste 2 version 1.2.0 Final. When the software is active, I’m seeing doubled images of distant objects — for example, at the pit exit, instead of seeing one white track line, I see two distinct white lines side by side. The duplication only affects objects beyond roughly 100 meters; anything closer is perfectly sharp and normal.

I’ve tried adjusting every single parameter in Custom Head 7 individually, and while I can spread or bring the images closer together, nothing actually merges them into a single image. The problem disappears completely the moment I disable Custom Head 7 and switch back to standard Pimax settings.

I haven’t had time to test this on other VR games yet, but I suspect it might appear on other titles too, though maybe not all of them. Either way, this is pretty disruptive — it forced me to switch back to Pimax Play.

Has anyone else experienced this? Any workarounds?

Thanks,

I’m using the Custom Headset driver by SBoys3 with my Pimax Dream Air, and overall it works great. But I’m running into one issue that makes some games hard to play.

Up close, everything is razor sharp and the image fuses perfectly. But for anything far away, the two eye images don’t seem to overlap/converge properly — I get a doubling effect in the distance that my eyes can’t fuse. It’s very uncomfortable after a few minutes.

I’ve already ruled out a few things:

•	It’s not a focus issue (close objects are crystal clear).  
•	It’s not my IPD offsets (tested with them reset to 0, same result).

It feels like a binocular overlap / eye convergence problem at distance specifically. Has anyone else experienced this with the Dream Air on this driver? Is there a setting I might be missing, or is this a known limitation?

Any insight appreciated. Thanks!

I was playing Assetto Corsa and switching back and forth between the two setups to compare performance.

But now, when I close S3boy3, uninstall its plugin, and switch my headset back to Pimax OpenXR, I still have a problem.

The game seems to launch in SteamVR anyway. I get sound in the headset, the Lighthouse base stations and SteamVR controllers are detected and turn on, but I get no image at all. On the Pimax side, nothing happens, as if the OpenXR runtime was still being controlled by S3boy3’s software.

Has anyone experienced this issue or knows how to completely restore the Pimax OpenXR runtime?

Any help would be greatly appreciated.

Hi everyone,

My current setup: SIMRIG SR2 actuators (3DOF), QSB T1 belt tensioner, two bass shakers (one under the seat, one under the pedal deck), and I play exclusively in VR — so whatever solution I add needs to work properly with VR motion compensation.

My problem: I’d love to add a yaw axis to my rig. The issue is that with my current setup, I always get the “rear stepping out” information too late. By the time I feel the car sliding, it’s already gone and impossible to catch. I’m looking for a real sense of grip loss / oversteer onset so I can actually save the car.

I know Qubic Systems does magical things in that department, but I don’t have €15,000 to spend. Replacing my actuators isn’t really an option either — it hurts my heart and my wallet says no.

Budget: around €2,000.

One important constraint: rig + driver together weigh about 220 kg, so any yaw add-on would need to handle that load.

Does anyone know of a solution (hardware add-on, traction loss platform, software tricks, tactile/harness tuning…) that would give me genuine early warning when the rear starts to slide, while staying VR-compatible?

Thanks!

Cette partie était déjà en anglais ; la voici légèrement remaniée pour une lecture plus fluide et en harmonie avec le ton des sections précédentes :

J’ai commandé le Pimax Dream Air chez Sim One, le revendeur officiel Pimax basé en France. Et franchement, chapeau ! Commandé début mai, reçu un mois plus tard. Pour un casque de cette qualité, c’est remarquable.

Le grand avantage de passer par un revendeur officiel comme Sim One : en cas de problème, vous avez un contact direct avec Pimax, contrairement au système de tickets d’assistance classique, souvent sans réponse. Quand on investit autant dans du matériel, savoir qu’on peut joindre quelqu’un, ça change tout. L’assistance a été impeccable du début à la fin : conseils, suivi, réactivité.

Confort : tout est une question d’accessoires.
Dès sa sortie de la boîte, le Dream Air est ultra-léger et compact, mais pour les longues sessions, il nécessite quelques optimisations. J'ai donc testé plusieurs modifications en parallèle :

• L'interface faciale Studio Form, ou des alternatives imprimées en 3D disponibles en ligne.

• Le bandeau Apple Vision Pro adapté au casque.

Attention au piège des tailles avec le bandeau Apple : leur guide des tailles me recommandait une taille M alors qu'il me fallait une S. Vérifiez bien avant de commander ; cela vous évitera un retour inutile.

Une fois tous les réglages effectués, le casque devient vraiment confortable. On oublie complètement qu'on le porte.

Qualité de fabrication : le compromis au niveau du poids.

Soyons honnêtes : il reste un casque assez fragile. Les matériaux pourraient être de meilleure qualité. Mais quand l'objectif est de gagner du poids, c'est le compromis à faire : on ne peut pas avoir des matériaux à la fois ultralégers et épais.

Le pilote SBoys3 : une compatibilité SteamVR native qui change la donne.

Pimax Play avec Pimax OpenXR fonctionne très bien avec le casque. Mais SBoys3 a créé un logiciel (Custom Headset) qui rend le Dream Air nativement compatible avec SteamVR, améliorant considérablement les performances.

Le hic : le suivi oculaire n'est pas pris en charge par tous les jeux avec ce pilote. Le rendu fovéal (DFR) n'est donc pas actif partout, ce qui affecte indirectement les performances sur ces titres. C'est prévu dans la feuille de route, et c'est assurément une fonctionnalité à attendre avec impatience.
Performances :

Côté matériel, j’utilise une RTX 5090 avec un Ryzen 7 9800X3D. Avec cette configuration, le Dream Air maintient 90 Hz en ultra dans la plupart des jeux. Fluidité, netteté et stabilité garanties.

Seule exception : Flight Simulator 2024, où je dois baisser les paramètres graphiques pour conserver 90 Hz. Vu les exigences du jeu en VR, rien d’étonnant ; et même avec des paramètres élevés, l’image sur les écrans micro-OLED du Dream Air reste époustouflante.
Résumé

Un mois d'attente, un excellent support de Sim One, quelques modifications essentielles pour un confort optimal (attention au problème de taille avec le bandeau Apple Vision), un pilote SBoys3 prometteur malgré l'absence de suivi oculaire partout, et une configuration RTX 5090 / 9800X3D qui permet au casque d'exprimer tout son potentiel. Le Dream Air n'est pas parfait — fragile, les matériaux pourraient être de meilleure qualité — mais une fois correctement configuré, c'est une expérience dont vous ne voudrez plus vous passer.