I recently upgraded to the Reverb G2 (from Samsung Odyssey, also WMR) and noticed something was shimmering or making me feel cross-eyed in DCS (but not in MSFS2020).
By closing one eye at a time, I noticed that the trees are rendered differently for the different eyes. The left eye seems to be seeing trees farther out than the right eye, but the closer trees also seem slightly different, perhaps in lighting or detail.
This happens when I am getting 60fps on the in-game counter, but also at 90 fps in the Mi-8 over Caucasus. It is especially jarring when I have tree visibility set to 50%. I can work around it by setting both tree sliders to max but it is still present then, though less noticeable. Of course, I donāt make it to 90 fps anymore then.
Motion reprojection is enabled, could that be it? Seems unlikely because it also shows at 90 fps.
I am running the following system:
Ryzen 5 5600X
Radeon RX 6800XT
32GB 3600CL18 RAM
I will be cleaning out my shaders now but keen to hear if anyone recognizes this.
Am also suspecting āWMR for SteamVRā since it does not happen in MSFS which uses the OpenXR stack
Thanks for the quick replies, cleaning the shaders did not help. I can clearly see the most distant trees rendered are much bigger in the left eye than in the right. Used Mi-24 Caucasus Free Flight instant action to test.
I cleaned up all directories referenced in this script:
Tested with F-15 free flight in Marianas this time, since that mapās shaders had not been re-built yet, and same result. I can see trees about 100-200 meters further out with the left eye. So, which config files did I change back when I had the Odyssey?
The search continuesā¦
It is nauseating, you would have noticed. Must be something specific on my system. Just realized I am running that modded DLL for AMD FSR, letās try without that.
I occasionally have the same problem with my Reverb G2. Also happens with smoke sometimes. Seems to be rather random, and if I notice it and reload it goes away.
Thatās a good thought, and could be the issue, but it doesnāt seem like it. Iāve had the alignment problem with my old Odyssey Plus and had to align it following the guide, but the Rift S and Reverb G2 have been perfect (seemingly anyway) out of the box. Scenery such as buildings, ships and the cockpit itself seems to be fine, but some āautogenā scenery such as trees and chimney smoke often only appears in the left or right side alone.
Thanks for all the replies! I just packed the Reverb G2 back into the boxā¦
To take it with me on vacation to the inlaws! They also play flight sims, but donāt have VR, so fun to try. That GTX 1060 will be sweating it though.
Mostly, they just bought an Ender 3 3D printer so I am hoping to print a modded gasket to bring my eyes closer. There are tens of designs on Thingiverse. As I have been using it, I have had to push the cushion into my face so hard to get to the sweet spot. So a thinner gasket should fix that.
With all of your help, I will have enough things to try when I get back. Sorry in advance for keeping you waiting.
On the upside, the box still smells of lavender and new cables
I run the repair and delete shaders occasionally for other issues, and still run into this every now and then. Restarting DCS seems to fix it. I assume itās a bug, it used to affect the clouds too but the new clouds seem to have fixed those for now.
So I just had this issue on the Marianas, and noticed that when I turn the forest visibility (distance the trees spawn in at) either all the way up or all the way down it goes away. It seems to be something to do with the LOD and one eye possibly being slightly further away from the object than the other, maybe?
Anyway, now Iām running that setting all the way up and seemed to fix it. Of course I canāt test it any further yet because my PC crashed again a minute agoā¦ finally have time for DCS (paternity leave this week ) and my PC is giving me fits with BSODās. Aw well, I probably need to be helping the wife anyway instead of playing games.
This might be the same issue, itās caused by a WMR setting I probably changed:
Fixed : "In the WMR settings for Headset display under experience options if you have it set to Optimise for performance you get the object desync. Set it to Best visual quality and it works as it should. " found by user Dayglow
Wow thanks @WarPig , great find! I did indeed change that setting, though I had forgotten about it. I will let you know if that works in a week, but this must be it.