PicklePicklePickle

Thanks for the reply, this is very interesting because I thought it was the other way. For example, when I take the Pimax and move the IPD adjustments way off, i get that 'cross/wall eyed' effect, and it's so bad that even after I take the headset off it persists for a bit. If I get the IPD adjustment close to my IPD, then I don't get as much of that feeling although admittedly it only goes completely away on the reverb. Anyway, that's why I related the two, might be wrong. If it is true that the IPD does not cause this, then it is even more mysterious to me. The Index and reverb for example have similar comfort, brightness, pressure on head and both are running at 90Hz. Maybe the increased screen door effect on the Index and the smoothness of the Reverb image are the difference? Another thought I had was the physical distance to the screen. I've read that the 'vergence accommodation' failure that occurs on flat '3D' displays is worse the closer the screen is (i.e. the headache is less for a theater screen for example). The Reverb looks pretty 'deep' as if the screen is farther away from the eye.

These settings work for me as well, and has helped me greatly tuning my system. Thanks for posting them. I do also opt for the resolution vs the highest frame rate. I find as long as it stays above 45fps I can tolerate it. Being able to detect features like the surface of the carrier when attempting to land helps me a lot, especially when you get to see the carrier as close as I do, the additional detail is appreciated.

Hello, My first experience with VR was on a Samsung Galaxy Edge with the Gear case. While I found the experience impressive at the time, I could not tolerate it for more than a few minutes due to eye-strain resulting in headaches. Now this setup is not IPD adjustable so i assumed that might be the reason. Now years later, I got the Reverb G2. Of all the great things(comfort, resolution, clarity, no lighthouses,etc) the most impressive was how it was 100% eye strain free for me. I can wear it for hours with no fatigue whatsoever and when i take it off my eyes don't feel like they are 'crossed' for a while. While I have set it to my correct IPD (64.1mm), i find that it is not eye-straining for me even if I set it to something slightly different. Another great test is to look at an object in the headset that is a certain distance away, then take the headset off looking at a real object the same distance away. With the Reverb, it doesn't even feel like I changed anything, my eyes are focus at the same spot. I then tried a Pimax 8KX. Out of the box even with the IPD slider set correctly, it was as bad or worse than the Galaxy, could not use it for more than a few minutes. I later found out that the screens don't move with the slider and you have to also calibrate it using the IPD Offset setting which moves the image. While that improved things, it is still not as good as the Reverb G2, which feels as if I was not wearing anything at all. I then tried an Index. While much better than the Pimax in many respects like the huge sweetspot and a correct IPD (lenses and image moves) slider, at my(or any) setting it is still not completely eye strain free like the Reverb for me. I even went as far as measuring the lenses on the Reverb and confirming they are set at the exact same distance on the Index, still get more eye strain on the index. I also thought about the smaller FOV on the reverb so I set the Index to the samllest FOV and it still doesn't feel the same. I have gone back and forth with these 3, side-by-side many times and always the result is the same. What are your experiences? Does anyone have any idea why two headsets like the G2 and Index can be set to the exact same IPD and similar FOV, and yet one causes eye strain while the other doesn't? I have a feeling that the Reverb G2 working so well for me is just a biological coincidence.

An interesting turn of events. I was distracted building the PC for DCS and forgot to pack-up the Reverb G2 and ship it back to HP. Once I was done with the new PC, I realized I should test it with the new PC to confirm it behaves the same. While I was able to replicate the 4-1 error consistently on 2 machines with/without hubs, the two machines were somewhat similar (Thinkpad P72 and P17) and they were laptops. Well, as it turns out I haven't been able to get it to do the same thing on this PC. I am currently running a long test with the WMR idle timer disabled to confirm it runs for hours, and then i'll try it for a session of DCS.

I just finished putting together my attempt at the DCS 'hammer' PC tonight. Installed Windows, DCS, SteamVR and got right to it. So far, it is a dramatic improvement! I started with just the Valve Index to keep things simple, and the desktop monitor and headset both on the RTX3090. The first thing that I noticed is that if I just set the DCS preset to 'Low' and leave the PD at 1.0 and Steam VR at 130%, it actually runs at the headset rate of 90fps during the F-14 Caucasus free flight. My previous system never did that. Even if I set the PD to 0.5 and SteamVR to 20%, in addition to all low settings in DCS, my old system would still only get to 50-60fps with that unusable pixelated mess. It must have been a bottle neck with having the RTX3090 as an eGPU over thunderbolt, or something like that. An interesting thing I noticed is that if I test the i9-10900K with CPU-Z, it doesn't really test higher than the Xeon W-10885M in my old system. But yet there seems to be a huge difference. The Index and DCS stutters seem to be gone. I did notice that if I stress the system with prime95 the CPU temp reaches 89-90C. While it doesn't seem to go beyond that, it seems high so I might have to double check the thermal paste. I'm a bit out of my element so I don't know if it is normal. I will post more of an update once I do more thorough testing, but for now here are the system specs: Asus Maximus XIII Hero motherboard (Z590 chipset) i9-10900K with 360mm water cooler 128GB g.skill ram Samsung 980Pro 1TB system&DCS drive RTX3090 (MSI Ventus) Corsair 680X enclosure and lots of fans

Yeah, after recent my crash course in VR it really seems there are no perfect options right now. I also got to try the Index in addition to the Pimax, so i'm up to 3 headsets I've tested with DCS. Of the three, the reverb is the only one that resulted in absolutely no eye strain, no sde and the fact that it tracks without base stations is very convenient for a simulator setup. It is a shame that it seems to be plagued by defects. The Pimax is the most problematic of all. The IPD design where the screens don't move with the lenses is flawed. It has the fuzziest optics of them all. The tracking constantly shakes slightly when your head is still in the cockpit. It has LCD mura, and it is uncomfortable. The only good thing about the Pimax is the FOV, but it doesn't outweigh the other problems in my opinion. The Index is more comfortable like the Reverb and it has a proper IPD adjustment, although I haven't been able to find the sweetspot for no eye strain yet. The FOV can be very good and is adjustable. It uses the base stations which is a downside for sims imo. The SDE is pretty bad, but I thought since the resolution is the lowest it will run DCS great. Unfortunately. anytime I use it, I am plagued by constant stutters(not DCS, any applicaiton), and it is unusable. If I keep the rest of the setup static and just switch to another headset, the stutters go away. Someday...there will be a VR headset that works....

I know this is not glamorous at all, but it works very well for me. I have one of these right next to my HOTAS stick, as close as possible without getting in the way: Expert Mouse® Wired Trackball | Trackballs | Trackball Mouse | Kensington Since it doesn't move around like a regular mouse, it is always in the same place and I can effortlessly reach and move switches as needed. I also use VR, so i look at the switch in the cockpit and the cursor is already close, the trackball has little work to do. Again, super easy to find with the headset on.

Yep BIOS and everything else is up to date, but thanks for the suggestion. I also tried several hubs, and even different machines. It was definitely the headset in my case. Headed back to HP today.

I got the Pimax 8KX today...Reverb G2 owners should be thankful. This thing is instant eye strain, i'm trying to figure out if tuning will fix it, already found a gazillion threads with the same issue. More excited about the empty box I got from HP today, hopeful for quick turnaround!

Well now that you both point that out, i'm wondering if what i'm seeing is ghosting: I have motion smoothing/reprojection disabled. For example I set 'Use SteamVR settings' in WMR and set SteamVR to disable Motion Smoothing. I start the Caucasus free flight and look left, there is a thin coastline. I then roll left and right trying different roll rates, and I find that there are certain roll rates where that coastline is doubled. Once I see it I can't unsee it, and it happens in other situations.

Since I already have the RTX3090 and Samsung 980Pro, I looked at just buying the missing components from newegg and it was way cheaper than buying the Dell or OriginPC. Got an i9-10900K and a 360mm water cooler for it. If it's no better, then at least i tried!

it is very strange. While I wait for the HP box I have been experimenting with the G2 some more. I have left it completely static on the table running the WMR house or Minecraft, and even completely stationary with no cable movement it still fails in a few minutes. That usually points to something (like an eye pattern on the cable?) that changes with temperature as the device heats up. I'm curious to know what the problem actually is, but we might never know. I'm getting a Pimax 8KX tomorrow, it'll be interesting to see if it has the ghosting I saw on the Reverb. Since I don't have VR now I went back to 2D and I am able to replicate the stuttering I saw while banking by adding SSAA and looking out the side with the keypad. If I remove SSAA however, it goes away and runs perfectly smooth in 2D. I do not see any of the ghosting, so that is VR related.

These are very good points, and the reason I haven't pulled the trigger yet. Well that and my Reverb G2 took a dump so i'm dealing with that. After reading everyone's experiences on this great forum I am 80% sure I am going to be disappointed even if I get the fastest overclocked system that can be built right now. On the other hand, I'm not looking to get to 90fps. I am currently on a laptop(albeit a really beefy one Xeon W-10885, 128GB of RAM and Samsum980Pro SSD) with a 3090 as an eGPU which has a bandwdith bottleneck due to Thunderbolt. When i start freeflight Caucasus above the ocean, I get 45fps. Once I start moving around it drops to 30-40 fps, if I get close to the ground/dogfight maybe 23-30fps. All i'm really looking for is a constant 45fps with little or no stuttering, no matter what i'm doing in the plane. 45fps is fine for me, the problem is that it drops and even at 45fps the horizon randomly stutters. But during the brief periods that it is not stuttering, 45fps is seems plenty smooth for me. It looks like i'm going to be waiting on the Reverb RMA for a while, so now maybe i'll get a Pimax or something else. I'm not sure if HP is just going to send me the same hardware back(with the same fault) and it will just fail again. It is a shame because when it worked, it was very good.

Yes, I also have tested this in single player and it doesn't work either. Last time I tried it on the F-14 Free Flight Caucasus, and just landed at Novorossiysk. Powered down, rearmed then tried to the INS alignment, but stuck at 66. I looked and Jester does indeed type coordinates in, I can't tell if they are different from the original airfield because I started in the air. I asked some folks on the 162nd Vipers Training Server and they say it is a bug that an INS alignment doesn't complete after shutdown.

Yep, I RMA'd mine last night. Didn't even call HP just used the support chat. The asked 2 things: whether i updated the bios and if i tried a hub and then they just offered to replace it.

I found this interesting post: Reverb G2 Troubleshooting 4-1 error, Speaker issues, and a Review : HPReverb (reddit.com) Apparently, HP said to unscrew the speakers and make sure they are making good contact, or something along those lines. Might as well try.

Ouch, good to know. I guess i better talk to HP support. Now that you say that, i'm pretty sure mine does it right when i'm moving my head. Last time it happened as I was going inverted and looked up to keep track of the ground. On the CPU, I have an Intel W-10885M currently.

Thanks. The Reverb has a separate power supply and uses the usb for the tracking data, but i'll try the hub...who knows.

Hello, Now I started getting this error 4-1 in WMR. DCS runs usually for a few minutes, then the HMD suddenly flashes blue then goes black. The DCS desktop copy image continues to show for a few seconds then DCS and SteamVR crash. Afterwards WMR shows error 4-1. When this error is showing, if I look at the Reverb in device manager it says "Working properly but USB speed too slow". I've been using the USB-C port but using the standard USB ports with the adaptors doesn't fix the problem. Initially, I thought this was a hardware issue. I suspected the complex connector that slides into the HMD, which doesn't seem to have a true locking mechanism. I suspected it was getting loose with movement. However, after some testing, there have been several instances where the error goes away just by rebooting without any movement of the HMD or cable at all. So this seems to be some sort of software problem. Has anyone else experienced this and has any clues on a fix?

Hello, After spending way too much time trying to tune my P17/W-10885M/RTX3090 eGPU setup, I am considering a full size PC for DCS. As far as I can tell, the thermal/clocking limitations in a laptop(not being able to run a high clock rate consistently) along with possibly the eGPU 22Gbps bottle neck are limiting. As I haven't had a desktop in over a decade, I am looking for input as to what works the absolute best for DCS VR. There is one option that seems to get good reviews in general, and appears to support overclocking: Dell Alienware R11 i9-10900KF RTX3090 64GB(3400Mhz) 1TB M2 SSD However, this system does not support a second card when an RTX3090 is used and it has no built-in Intel graphics. Since this machine will be dedicated for DCS, has anyone run a VR headset as a single display? i..e boot into WMR/SteamVR and run DCS from there? I'm not sure if there could be some performance issue with sharing the card between the desktop and the VR. I've also looked at OriginPC and getting a system that has the built-in Intel graphics(or a cheap second card) for the deskop, so the 3090 only does DCS VR. Any suggestions welcome, i'm looking for whatever will give me the best chance of success(highest VR fps, lowest stuttering).

I don't think you're wrong, let me clarify what I meant. With the default Windows setting that lets WMR use the Reverb sensor, and with WMR Portal closed, I start (standalone DCS, manually added to Steam) DCS from the Steam tray menu(I don't use cliffhouse). This automatically starts WMR(without cliff house) and Steam VR as well as DCS. I then put on my Reverb G2 and windows detects that I put on the headset through the sensor and disables the mouse in DCS. I think this is different from whether or not the mouse works in WMR/Cliff House. In order to make the mouse work in DCS I had to do one of 2 things: Either take the headset off, ALT+TAB to WMR, press Win+Y, then go back to DCS, put headset back on Or disable the Win+Y auto detection in Windows Mixed Reality settings. Anyway, just my personal experience, it might work different elsewhere. DCS+VR+Windows isn't exactly a paragon of consistency across systems.

I am curious about this as well. From what I have seen, even with reprojection turned off if I bank at a specific rate and look out the side I can see doubling of features with the G2. The free flight Caucasus is a great example. When it starts, on the left hand side there is a thin coastline with a lake on one side and the ocean on the other. If I look at this while banking I can find a roll rate that makes 2 coastlines appear and that's without reprojection. I don't understand what in DCS could be causing that, one possibility is the HMD display itself(or maybe something in the graphics card) using a refresh technique(like interlacing) that momentarily shows both images. Another possibility is the response time of the LCD in the Reverb being too slow for 90Hz, yielding the double image effect. If the latter is the cause, then the effect would go away if an OLED HMD is used. Presumably it would also go away if going to 60Hz, not sure I have tried this.

The OP has a point. On one hand, DCS with VR is simply the most amazing experience in flight simulation since I started flying Sublogic's Jet and Chuck Yeager on the C64. It is quite simply a culmination of the immersion and experience that any combat flight sim enthusiast has longed for. When you climb into the Heatblur F-14 on a moonlit night and turn on those instrument lights...wow. On the other hand, it is frustrating to be so close to this flight sim 'nirvana' and not being able to enjoy it or being interrupted due to stutters, low frame rate, sparkling, blurry etc. Spending days tuning only to not get any improvement at all. I think fixing performance should be ED's highest priority. It doesn't matter what new features they come up with if they run badly. I am having the same experience as GunSlingerAUS, everything I get is <45fps and I have Samsung 980Pro, 128GB RAM and RTX3090 although admittedly it is as an eGPU. I am now looking at getting a desktop i9-10900 system just for DCS, and I could very well be disappointed because there is so much inconsistency in performance, there is no guarantee it will work. They could literally charge for the Vulkan update and I would buy it, if it gets DCS working smoothly like every other VR game.

OP I had the same problem. The solution was: Open Windows10 Settings->Mixed Reality->Headset Display and set Input Switching to Manually switch using Windows logo key + y. Otherwise, the system uses the light sensor inside the Reverb and it assumes that when you have the reverb on you don't want to use the mouse. You can override this by lifting your headset and doing ALT+TAB to select WMR and then Win-Y, then switch back to DCS but who wants to do all this. Then set DCS VR options to use mouse and limit mouse to app window. With this setting, the green cross hair disappears after a few seconds and it doesn't interefere with my view when i'm flying around. But if I move the mouse, the green cursor appears and you can select switches with your head for the general direction and the mouse for the precise switch. Works great. Also, a side note. If you fly at night, I recommend to disable the 'blooming' effect in the VR panel. This makes the green crosshair cursor and the tooltips on the switches to have a halo around them, which makes it look like the headset lenses are dirty. If you turn off blooming, this goes away and the cursor looks much better when the cockpit is dark.

This. I noticed 2 things. First, the sweet spot for me is with the lenses sitting a little bit lower than where I intuitively place it. It feels like the bottom of the headset is sitting too low on my cheeks, but it puts the sweet spot right in the middle. The second is experiment with just pushing the headset against your face and see how the sharpness changes. I found it has to be snug to get to the sweetspot. All that said, these Fresnel optics are a compromise and it will always be blurry away from the center sweet spot. But to get the best experience you want to make sure the sweetspot is right in the middle and sharp.