Waxi

It could be that your light source is flickering, which may interfere with the tracking. Light sources often flicker at the frequency of the power grid (i.e., at 50 or 60 Hz, depending on where you are). This is too fast for most humans to notice, but for the tracking cameras it could be an issue. I think the Oculus software has an option to address this, but I am not aware of a similar feature for WMR headsets. Maybe using another light source (e.g., a portable lamp with a different light source than your room light) may improve or solve it...

I observe exactly the same issue using an HP Reverb at 60 Hz with an 1080Ti, 32 GB RAM, and i7-7700K.

I can confirm that reducing the refresh rate to 60Hz results in a very smooth experience, also on my i7-7700K and 1080Ti with the settings I mentioned in a previous post.

What helped me getting a very smooth experience with the Reverb on my i7-7700K with 1080Ti and 32 GB RAM was switching the Experience Options in the Windows Mixed Reality Settings of the Windows 10 Settings app from 90Hz to 60Hz. This essentially allows reprojection to kick in already at 30 FPS instead of only at 45 FPS. If you are not sensitive to the lower refresh rate, this may be a viable approach to improve your experience with the Reverb. I am using Steam SS at 150% (everything below does not look better to me than my Rift S), DCS PD set to 1.0, DCS graphics options all set to high, civil traffic to medium, heat blur and dirt and flare options to off, MSAA and SSAA both off, shadows both to flat, AA X16, global illumination and rain droplets on.

Yes, that's what I meant.

I experience heavy flickering at DCS loading screens with my HP Reverb and got used to it. I guess this is an issue with WMR headsets using WMR for SteamVR. If you do not want to look at the flickering screens, as a workaround, you could configure SteamVR to drop back to the SteamVR starting environment when applications do not respond.

In the DCS controls setup, where you can select the control sets for the different planes, select "UI Layer" and bind a keyboard shortcut or joystick button to the "Recenter VR Headset" feature (see this post with a video of what I mean). Then each time when ready in DCS after strapping on your headset, you press this keyboard shortcut to get the head position in the VR space right. I have the same issue when I start DCS with my headset lying on the seat in my simpit before I get ready.

I also observe this issue. I cannot hit anything with ballistic bombs in the Normandy target practice mission for the A-10A. The bombs just drift too much off target.

As far as I can see the "display resolution of XXXX every frame" seems to just control the resolution of the mirrors in the cockpit. It does not seem to affect the visual quality of gauges or displays in the cockpit.

If GPU usage stays low, it could be that your CPU bottlenecks the GPU. I was observing something like this on my system that runs on an i7-7700K at stock speed of 4200 MHz and a 1080Ti. After disabling hyper-threading in the BIOS and overclocking the CPU to 4800 MHz (Intel provides software tools for easy overclocking of unlocked CPUs), GPU usage went up to 95-97% in computationally demanding scenarios (such as flying low over Las Vegas).

Agree, but only with Steam VR SS at values above 130% (using WMR for Steam Beta).

I have the same issue but no solution.

I had the same comfort issues (visor pressing into my face that it hurts and fog on the lenses) with the Rift S until I realized that I wore it the wrong way. After adjusting the halo so that it sits slightly below the small bump at the back of the head (and not above it as I wore it originally), it is very comfortable and not pressing into the face at all.

White noise in HMDs only on first boot I have the following issue with my Reverb: When I cold start my computer and start WMR or WMR for Steam, my Reverb shows white noise on both displays. When I then reboot my computer, the boot process seems to hang for like 20 seconds until the computer beeps and continues to reboot. Note that on cold start it does not hang and boots swiftly. Once the reboot is complete, my Reverb is working fine without any issues or glitches. Another way to fix the white noise issue is to unplug and reconnect the USB and DisplayPort plugs of the Reverb. The issue occurs no matter which DisplayPort jack of my graphics card I am using. The USB plug is connected to one of the USB 3.0 ports soldered to the mainboard. The issue also occurs when using the USB 3.1 jack soldered to the mainboard. My system consists of an Asus ROG Strix Z270F Gaming mainboard, an Intel Core i7-7700K processor, 32GB (4x8 GB modules) of Corsair Vengeance LPX DDR4 RAM, and an Asus GeForce GTX 1080 Ti ROG Strix OC graphics card to which I have applied the Nvidia DisplayPort firmware update. I have not overclocked any of my system's components. I purchased the Reverb from HP Germany a few weeks ago. So it should be of the second hardware revision. Did anyone experience similar issues or has any hints on what I could try to solve it?

I was using Track IR with a 43" 4K monitor and then switched to the Rift S. Immersion was awesome but the relatively low resolution bugged me. Recently I switched to the Reverb and I think with this one the tradeoff between resolution and immersion is acceptable. Since I bought the first VR headset I have never used TrackIR again. But I still have it.

Same for me. I also ordered it from the German HP store, got an estimated delivery date sometime mid October, but delivery time in the end was two business days.

Yes it does.

I rearranged my pit so that it faces the room with the white wall in its back. This solved the tracking issues I described earlier.

Looking for Advice for Improving Tracking Any tips on improving tracking of the Reverb? The Reverb seems to have issues with fast head movements and with the white ceiling and white wall right next to the right of my pit. Both are not an issue at all for my Rift S.

I playing DCS exclusively with my Rift S since end of May and have never encountered any of these issues. I am also using VIACOM with Voice Attack. My Rift S just worked right out of the box without any problems. The only criticism I have is that the batteries in the controllers do not last long (I had to change them in the last days for the first time) even though I did barely use them.

Easier said than done. At least here in Germany. ;-)

Just press and hold the HOTAS activation button for the VoiceAttack radio you want to use and say "Options". The standard communication menu will then show up. I think you may have to enable this somewhere in the VoiceAttack options.

You can actually see the virtual hands controlled by the Rift S controllers in the cockpit. So you do not have to memorize where your controllers are because you just see them as black gloves in the virtual world. I have tried using the controllers only once until now to try it out. I found it rather difficult to use them and frequently hit my desk with my hands, but I guess this is just a matter of rearranging my setup and training.

I don't have these issues. Coming from Track IR to the Rift S I noticed that I have to get used to the gears getting contact to the runway on landings while still being several feet above the runway, which is realistic as the VR eye position is high in the cockpit and the nose of the aircraft is elevated due to AoA. This is for the FC3 F-15C.

Can I download the updated manual from somewhere? I am traveling with plenty of time to read but I do not have access to the machine on which I have DCS installed on.