Search the Community

I am a long term G1/G2 user. I recently bought a Quest 3 along with a Kiwi H4 headstrap and Kiwi link charging cable. In spite of several weeks of fairly extensive tweaking I never got the Q3 to perform as well at the G2 and found the image quality, whilst excellent close up to be inferior when looking out of the cockpit. Also I had repeated occurrences of the dreaded water/debris in charging cable error which filled the screen and required fumbling for a controller to remove - typically at the most inopportune times whilst flying or racing! As an alternative I tried Virtual Desktop using a dedicated access point that runs at around 830Mbps which I though seems decent but some research show proper gaming routers are well in excess of. As the return window got closer I ended up returning it, the Oasis driver was released and the G2 is running nicely with Windows 11 24H2, so all good. However, reading reviews where people describe the Q3 as an upgrade I can't help feeling I missed a trick somewhere. Virtual Desktop was very poor compared to the link cable, so presumably a router/access point upgrade is necessary. What recommendation are there? Compared to the G2 the Q3 link cable wasn't as smooth. That said I find SteamVR motion reprojection smoother than the Microsoft one so always ran OpenXR with SteamVR as the runtime (maybe unusual?) Visually as mentioned I found the Q3's pancake lenses brilliant at displaying gauges and edge to edge clarity but the distance stuff seemed more blurry than the G2. A prime example is taking off, the runway looks detailed close up but halfway down suddenly turns into a blurry mess. Maybe it is because the image is so clear the LOD changes look more apparent. Again am I missing some settings in DCS, nVidia control panel or something else to make this less apparent? It is also especially noticeable in sim arcing where the track is great in front of the car but terrible in the distance. Is any of this fixable or am I limited by the compressed image over USB compared to DisplayPort? I appreciate VR can be quite subjective and maybe the G2 suits me more than the Q3 but was interested to hear from those who have had both specifically relating to DCS.

Thanks to MBucchia!

Thanks to the new Oasis driver for WMR, I pulled my Reverb G2 out of the basement again. Started DCS – and what did I see? A severe misalignment of both images (cross-eye effect). The tool for WMR that used to run via autoexec.cfg no longer exists. What can I do?

Hey, Love DCS VR, but I hate the tiny sweetspot of the G2. Furthermore I would like to replace mouse-control by any pointer system or handtracking. And G2 will not be usable in future to missing WMR support? Should I go with the Quest 3 with handtracking now - is it a great upgrade or should I wait for next generation of headsets with eye tracking? Thanks 4 your thoughts

Hi, I don't fly anymore so I'm selling my gear : Shipping to Canada only, or local pick up in Montreal. Let me know if you have any questions! I can provide pictures upon request. Grips : - Virpil Mongoost-50CM2 grip (like new) : 200$ + shipping - Thrusmaster Warthog grip (very good condition except for some red paint fading on the right side of the trigger) : 150$ + shipping Base : - Virpil Warbrd (like new) : 150$ + shipping Throttle : - TM Warthog Throttle : 300$ + shipping VR headset : - HP Reverb G2 (great condition, includes V2 cable) : 100$ + shipping

Hi everyone, Does anybody know a good 3D printable model to attach the Ultraleap (NOT the Leap) to the Reverb G2 ? Thanks

Hi there, I just want to share my experiance upgrading the system as the results are quite impressive. As the title says, I upgrated my GPU. Before I did so, I created a small session in Afghanistan and recorded the replay with MSI Afterburner before I made the changes. Afterwards, I run the same clip recording again with MSI Afterburner. These are the results: AMD 6900 XT 23-05-2025, 17:14:30 DCS.exe benchmark completed, 5091 frames rendered in 74.281 s Average framerate : 68.5 FPS Minimum framerate : 53.5 FPS Maximum framerate : 92.9 FPS 1% low framerate : 39.8 FPS 0.1% low framerate : 39.7 FPS RTX 5080 24-05-2025, 15:38:24 DCS.exe benchmark completed, 12052 frames rendered in 77.281 s Average framerate : 155.9 FPS Minimum framerate : 125.4 FPS Maximum framerate : 197.8 FPS 1% low framerate : 39.4 FPS 0.1% low framerate : 22.1 FPS Honestly, I did not expect this increase of performance. By test sites I expected about 80%plus, bus this is now 127% plus. I am playing 2D in 4k. My CPU is a AMD 5800X3D, 64 GB DDR4 3200 RAM, X570 Mainboard I know this a very short "test" and would not fulfill verbose analysis. Just one run - in Afghanistan in a F/A18 from inside and outside, no other planes and just ~75 seconds. However, I think this can help one or another when thinking to upgrade. @ED It would be great to have a common benchmarking function to get more reliable results across the whole community. Kind regards Limaro Benchmark_Afgh.trk options.lua

Does anyone else have this? This isn't a DCS problem; it happens with anything. I've been playing KCD2 and have been away from VR for a while. My GPU is a 7900 XT. The monitor still shows everything normally. The only fix I have found is to switch to 60 Hz.

Hope somebody can bring some light in this matter. And in my reverb Since recent my reverb headset is acting up in DCS. After a while (15-20 minutes into the game) the headset blacks out. It does this always in the same pattern. First the left screen, then both screens and then turn back on. And that repeats itself. In a regular pattern, sometimes it blacks out quickly, sometimes it take little longer but generally within a minute. I thought it was caused by the latest nvidia driver so I installed an older version (572.83) but no change It looks like there is no problem in MSFS in VR Looking at the log file (not really sure what I am looking at though) I see a massive amount of warnings and errors including errors in the GRAPHICSCORE (17804) Is there something obvious going wrong here? dcs.log

someone is still using Reverb G2 with Open XR ?

WMR, Reverb G2, Win10 See, example (Big smoke, but also visible with burning vehicles) RotatingSmoke.miz LastMissionTrack.trk

As in the title of the topic, mbucchia is doing the miracle and Reverb G2 and G1 will stike back because support for W11 24H2 will come for fall thanks to mbucchia. Also the others WMR headset will be supported by the new Oasis driver. Mbucchia is a living legend!!!!

Nice to see the replies here, as a newbie to systems i dont really know too much. I did however buy at the time the best i could for dcs to get the best graphics. I may not bother doing this then. Im running a nvidia 4090 with 7800X3d and use HP Reverb G2 Vr, personally thought about replacing the reverb with a pimax crystal light for better visuals..... my be worth doing?

Ho gia un reverb g2, passare a un pimax light non ne vale la pena?

Hey all. Not too sure if anyone else is having this problem with their AMD Radeon graphics card? Everything seams fuzzy in general with lots of ghosting and after the patch. I initially made no changes to my settings, but putting on FSR made no improvement. In fact, I also started getting micro stutters. It was running perfect before the patch. I have a 6900XT on a decent PC. Anyone else?

Last couple of days Dcs vr is working as intended on oasis steam driver again.Win11 pro 25h2 Not sure what changed...maybe running DCS as administrator solved it. Plug in reverb g2 power...run dcs as administrator...steam vr starts and loads into dcs hangar.

Hp reverb

Da windows 11 24h2 microsoft ha rimosso il portale windows mixed reality, abbandonando del tutto la tecnologia. Tutti i visori che usavano wmr, tra cui il reverb g2, sono diventati dei fermacarte. Questo finchè un buon samaritano non ha deciso di mettersi lì e sviluppare nuovi driver free, gli oasis appunto, per riportare in vita i visori abbandonati da microsoft. Ormai non ho più il reverb g2 per verificarne la qualità, ma a quanto pare funzionano. Per cui se hai già un reverb g2 non ti serve altro: scarica quei driver e inizia a volare, il visore che cerchi lo hai già in casa!

Resolution is good (2160 x 2160 per eye), the only downsides the Reverb had at the time was the Fresnel lenses; comparatively small FOV and the lack of eye tracking. it was a very solid headset and if the OASIS driver had come out sooner i would likely still had one.

BTW, speaking of inside-out-tracking, I've not had any issues. (fingers crossed since I've not upgraded Pimax Play...yet) I have a physical, motionless Viper cockpit and three walls surrounding it, with a door on the left. Tracking is flawless for me, similar to my Reverb G2.

Dopo avere letto un post precedente ho provato sti driver, sapevo che avrei fatto una cazzata, infatti il mio reverb poi risultava acceso ma completamente nero, fortunatamente ho disinstallato tutto, riavviato il pc e tutto e ritornato come prima, l unica cosa che ho fatto e cambiare posto al connettore sulla scheda video.... mai seguire il primo consiglio che leggi... Tanto il mio reverb continua a funzionare anche aggiornando windows 11....

A dire la verità il mio reverb g2 continua a funzionare ho aggiornato windows pochi giorni fa..... Dici che non vale la pena spendere 200 euro in piu per il pimax light?

EDIT: I determined conclusively that this is caused by activating force feedback. Turning off force feedback eliminates the issue completely. It seems likely that this is caused either by something introduced in the last couple of patches or it's related to my new AMD 6900XT. EDIT 2: I have an update that I think completely solves the issue without using the "input = { threaded_ffb = false }" line in the autoexec.cfg file! This new solution is better because it comes without the negative performance aspect of using that autoexec entry. I stumbled onto this by happenstance while researching a completely unrelated problem. All credit goes to user l3VGV from the Russian language IL2 forums. The solution is simply adding the linked dinput8.dll file to the DCS World\bin folder. https://github.com/l3VGV/FixFFBStutterH/releases/tag/v1.02 No lag, no measurable negative impact to performance. Force feedback forces appear to all work correctly. Problem solved. Bug: 0.5 second control input lag when force feedback is on and Microsoft Force Feedback 2 stick is in use. All controls including keyboard affected. Also affects opening menus ex. Esc to open menu. Can I reproduce it 100%: Yes. 100%. Just turn on force feedback and play any mission with the F-14A or B with Microsoft Force Feedback 2 joystick in use. How to reproduce/ description: Turn on Force Feedback in DCS Settings Menu. Easiest way to observe is to launch F-14 Dogfight from Instant Action. Input lag may not be immediately noticed by moving joystick. Repeatedly pressing the escape key to open and close the game menu makes this obvious, as it will lag anywhere from a half second to a full two seconds. This lag is also present in all other inputs, most importantly, flight and weapon controls. Turning off force feedback completely eliminates the issue. DCS Version: OpenBeta 2.5.6.60966 System Specs: Intel 7700k AMD 6900XT 48GB RAM SSD OS: Win10 Peripherals: Joystick: MS Force Feedback 2 + CH Fighterstick for buttons + Leo Bodner board for axis inputs Throttle: Thrustmaster Warthog Pedals: Saitek rudder pedals Headtracker: HP Reverb G2

Check out the preview branch of Oasis that just dropped. They've had trouble with the G1, but G2 supposedly works. It won't necessarily be perfect, but that could keep you going with the Reverb for a while longer.