VirusAM

Yes...as you can see in my signature I happily use a Valve Index and I am in the VR alternative reality since 2017 (rift cv1). So I think I know what i am talking about. I usually use the default head mouse movement, but I tried the “use mouse” option and it does exactly as I described above...with it ticked you can move your mouse cursor (the one for operating the switches and buttons in the cockpit) with your mouse....independently if you are using the radio menu or operating switches in the cockpit. Also if you use the awesome pointctrl you have to do exactly the same thing, as for your PC and for DCS that device is just a mouse ... @milesd and all the pointctrl users will be able to confirm that (i used it and I am waiting to the v2 for buying it myself). Could you try? if you won’t be able to operate the switches independently from the head movement let me know...I will do a video of that functionality for you and for the OP. Yes it does by default

Just tick use mouse in the VR options tab. This way the head movement and the mouse movement will be decoupled Mmm why do you say that? The option I mentioned above has been there for a while... Ticking use mouse in the VR tab is the solution. When using track ir the mouse doesn’t move with the head by default.... So I don’t understand why you say there is a problem.

Your link settings are crazy...try to lower to 1.3 You have a pretty powerful GPU, but raising the rendering resolution raise also the VRAM usage....and your car md is pretty poor in that department for this kind of usage

It was flyable and landable on a carrier in flanker 2.5... It was awesome.

Yeah resize bar is SAM (smart access memory) it is on auto.... I am not sure the rtx 2080ti supports it.

The image quality doesn’t seem to be affected...even at 150mb/s encoding setting.... What worry me is the stutters, ghosting and double vision while moving the head that could be due to the link cable, or the oculus software as it doesn’t happen with the Valve Index despite higher rendering resolution setting (with SS)

Well...I was going mad at this ahahah.... Very well, i did the mission twice, just because I thought I made some sort of mistake

Good... But is there a source to learn how to convert? I passed this particular mission finding targets with the tpod. And tought that the coordinates were just for the general area of the target. Thanks, I made my post earlier without reading this answer. Very well. In the 11th mission I encountered a similar issue (don’t want to spoiler here)...so I had to rely on the wingman to do the job, and after he had hit a target i found the other ones with the TPOD...there the given coordinates seemed to be the precise ones, but again when set in a waypoint (with precise set) it was in the middle of nowhere. Would like to know which kind of conversion was needed there?

Well...better to reach to the fpsvr developers then...maybe they will have a fix for it. I will try as well as soon as I can

About sam...yes I put it on auto... But I don’t think the rtx 2080ti is enabled for it... And yes that is why apart from changing cpu and motherboard i changed also my ram

You could have a pretty enjoyable experience lowering your settings and using an oldergen headset (rift S for example) probably index or reverb are no-go for your system. The most powerful of the nowadays systems cannot run dcs in vr at high settings and 100% resolution on the hp reverb and have good frames

This also is impressive. I still don’t understand much of the AMD platform, i am running at pretty stock settings, with just the ryzen master auto OC (it asked me to do on the first launch). My ram also is 2x crucial ballistic 3600 dual ranked. Everything is in 1:1:1 ratio (1800). What I could do to still improve performances? What is ultra powerplan?I don’t have it...I have balanced, high and the process lasso one. Pbo overboost and limits are set in Ryzen Master or Bios? What is the negative curve optimizer? Thanks....as said above I am pretty noob of the AMD platform.

Well that’s huge....little big monster of a CPU. I hope it will be possible to find it at a proper price before the end of January

Yeah....I noticed the same. With PBO auto I have better performances. That is quite strange.... Could it be a placebo?

Image clarity in the quest 2 is good. Better the Rift S. But this is not the whole story, there is also the overhead of the link encoding. @dutchcoolhand I am testing a quest 2 and need to understand if some stutters and ghosting issues can be solved or are related to the link or comes from the Oculus software itself. So my better advice is to try it , and if it is possible buy from somewhere with a good return policy like Amazon, so you can return it if not satisfied. I probably will be returning it and keep my Valve Index

Don’t worry....it is just an empty weekly newsletter. Today is Friday but probably they just didn’t fill any content.

Because frametime matters most in VR. To maintain 90fps you need to be in the land This is impossible even for the most beefy hardware. So the next goal becomes to be under 22ms to have a smooth experience with ASW/Motion Smoothing. Frametimes are the time that the cpu uses to prepare a frame for the GPU and the time that the GPU uses to render it. 1000 milliseconds/90 frames = 11.2 milliseconds.

It could be. I need more testing, but with the Index (with an higher rendering resolution via supersampling) I get better performances. With the quest 2 my system performances are not bad, but I have big issues when moving my head or with fast movements (stutter, double images)...and that could be caused by the encoding part or by some bug of the oculus software.

Dcs does not support WMR mode at the moment. In order to use DCS with WMR headsets you need to use steamvr and the mixed reality for steamvr application. Ask if you need more informations

Happy 2021 to everyone.... Let’s forget this crazy 2020 for good

Well...i had my first approaches with VR in 2017....i feel that DCS VR has never been in a good shape like now... I am sure it will get better

With the quest 2 you also have to consider the overhead of the encoding and compression of the image

Well I disagree...we had no 50% improvements....but little optimizations here and there.... Then we will have vulkan which hopefully will bring a lot to the table...

We just need to wait. A porting of the EDGE (dx11) engine to Vulkan has already been announced and in the works. Last official word was before all the covid stuff...so probably there is some delay on it. But I don't think it is too far away. They mentioned also a rework on the entire engine but that will take much longer probably for accomodating the core number race (vs the previous GHZ race). So you (as me....a VR addict as well) just need to have a little bit of patience. Bye

This is exactly what I meant..... And the scenario you described are exactly the use cases which I was referring to and where the CPU raw power (aka IPC) counts a lot. And I never said that the GPU doesn’t count as well...but in that specific scenario it will be sitting half utilized if the CPU can’t keep up with all the calculations and draw calls. As the rest of your post I agree also on everything else you wrote. In the end an high end gaming system needs to be balanced in all its components.