Motomouse

Drac, do you have the same picture with your Reverb in the left and right eye? With the latest patch I had different LOD rendering in left and right eye. Objects did pop up at a different distance. (I am asking this because I also consider a hardware error of the Reverb, the render problem is not there with the CV1)

In my country HP support is not up to speed. Cable defect is at the clip (where the cable is clipped to the side straps). Not the long cable, but the short fixed to the HMD. Will report my customer support experience. But I really like my CV1 for the time beeing :-)

The performance in the CV1 is substantially better compared to the Reverb. I am able to fly at high settings with shadows on the channel map.

Important update: The render errors are happening only with the HP Reverb and the shared_parser false setting. Rendering in my Oculus Rift CV1 is correct with the shared_parser false setting.

My Reverb cable just started dying. I had to revert to my Rift CV1. And is not bad at all. Go for the Rift S! OP has got his quest already ;-)

I have a post to make you Oculus Rift users happy. The cable on my Reverb started dying today. I asked my son friendly to hand me back my trusty CV1. He complied ;-) I was in kind of a bad mood and not expecting much. But damn, it is not bad at all to be back in the Rift. Yes, the Reverb has the higher resolution. Else ...

Give low view range and shadows off a try. Not that I suggest it as an everyday solution.

@zildac you have to undesignate, once just before stepping through again to check, or the overwriting happens if you only step and designate without checking it works

@ED: Thanks for the unique VR experience I enjoy every day. I am looking forward to the resolving of the rendering issues in the current OpenBeta. Please continue to launch further content so I can throw my money in your general direction ;-)

What do you expect from the 2080 Super over the 1080ti? I would save the 300 and exchange the 1080ti for a next gen card later.

200% SS are not the native Res

60 hz and 90 hz are the only options for the HMD. FPS are not directly connected to the refresh rate, it is just a more fluid experience without stuttering if you manage to reach the refresh rate with your FPS. I have recently problems with the 90hz mode (white static noise and unreliability of the connection, perhaps a cable turning bad or a driver issue). But I prefer the 60hz mode without reprojection anyways. I experience it much more fluid than 90hz with reprojection. I always manage to get constant 60 FPS (In singleplayer I use cockpit shadows and flat terrain shadows too.)

Thanks, I also missed the undesignate at the end in my procedure (Which leads to overriding if you step through the stations again). Now it is easy peasy and a joy.

Get a Gladiator Mk2 as secondary joystick, not for the stick but for the buttons, and you have a nice VR "Keyboard". The buttons a very distinctable even during blind use.

It did not work for him and realistic TDC control is the default setting. ;-)

Complete it is not. But the richest experience is provided by the F-18 in my opinion.

I fly at constant 60FPS on my 3600X/16GB/1080TI/Reverb setup (shadows off).

It is possible to fly the map at very low settings with constant 60 FPS with my 3600X/16GB/1080TI/Reverb/ setup. (Shadows off, low view range, 0.8 PD) Do I want to fly this way everyday, no. This is just a headsup for those who think they can not fly the map at all, because of the poor performance with your standard settings. It is worth to try out the map at fluid 60 FPS with very low settings.

You have to push and hold TDC depress while controling the dive.

Try the stereo_mode_use_shared_parser = true setting. LOD will be fixed for many things. But supercarrier personal will only be rendered in one eye.

With the the update DCS 2.5.6.50321 I get lots of render errors with the default stereo_mode_use_shared_parser = false setting. Much less with the stereo_mode_use_shared_parser = true setting (also the supercarrier personal is only rendered in one eye, but this is preferable for me to the rendering errors with the default setting all over the place). After flying some missions with the true setting you can instantly perceive the wrong rendering when you switch back to the default false setting (It is quite nauseating).

So for now I have the choice: 1. Uncomfortable trees and mountains all the time with default settings 2. Uncomfortable personal on the supercarrier during launch and recovery with shared_parser true setting I go with number 2 for now. Looking forward what will be resolved first: trees or grapes ;-)

This is not only about trees. Mountains are also rendered different in both eyes when using the standard shared_parser false setting.

Easy peasy

To put it diffently the pop up distance is different in the left and right eye with shared_parser false.