Hoirtel

Because there is no performance overhead, so those people who do less PC maintenance and upkeep struggle and those who trim all the fat off their PCs and learn the processes behind optimising struggle less. 2D DCS isn't completely plug and play but the fps rates required are much easier to obtain and therefore less vulnerable to general system overhead and marginal setting tweaks across the board. VR has been around for a few years but as a new area for consumer tech it is still climbing to reach its potential. In another 3-5 years crisp and smooth visuals will be much easer to obtain and so it will therefore be much closer to plug and play. Probably cheaper too.

Higher anisotropic filtering values are most noticeable from cockpit when sat on a runway/taxiway. 16x looks great, I also don't find this has much perf impact so I wouldn't go lower than 8x but I would have thought 16x would be fine for most people. Texture filtering in the Nvidia control panel is best at high performance, regardless of system. You likely won't see any quality difference but this has lower latency, its a small gain but helps ease those ground stutters. "Higher resolution will reduce aliasing jaggies and shimmer in the distance but not improve muddy/blurry textures". - Bearing in mind that the thread was about improving distant detail, using a Q2 at low res with 1.3/1.4 supersampling looks sharp close and bad far away.

Oculus software is base resolution not supersampling. 1.0 means you are under sampling. Ignore the 1.X values here, they are irrelevant and I'm sure oculus just did this to confuse people. Leave DCS pixel density and OTT at default and set software as high as you can first Then if you want you can use ODT to multiply (supersample) it. But it is a percentage of your base so the larger the base is the larger increases ODT will create. I don't supersample at all on a 3090 as max is enough.

In short the detail in the distance is harder to get, its a physical limitation of the resolution of any of the VR headset, with the possible exception of the varjo aero (yet to try it). As per other threads preferable performance and quality is to raise the resolution in the oculus software device settings before doing anything in OTT, ODT or DCS (in-game). This will give you the best native detail, before you go multiplying it. Sounds like at the moment you are multiplying a lower base resolution. Worth remembering that the latter three controls (OTT and ODT work the same control) are multipliers of each other and ultimately of the resolution you set in the main oculus software. I run high settings at max resolution and my 3090 will not take any super sampling at all. The visuals are very good. Don't bother changing ingame PD. Not really worth it. For ref: ODT = oculus debug tool

Oh yes.. MSFS isn't nearly as good/smooth in VR as DCS.

I since the Q2's link Sharpening option was introduced I now use NVCP MFAA on in addition to MSAAx2 in-game. MFAA seems to slightly reduce the impact of some shimmers introduced as part of the sharpening. Never used to do much for me before that.

Shame for no roadmap but I don't blame you. Always ends up with pitchforks for the rest of the year. Newsletters are great - glad they are staying as they are. Looking forward to another great year for DCS.

3090ti inbound very soon... Same VRAM few more cores... 450w TDP...

Is that not it at 18 seconds in?

As one of the people who has gone through the "button bind split up option" to manage SRS and VIACOM i can say that the approach in the manual does work, I did find it a little tricky to sort out and if I remember correctly some servers it doesn't work on - I think this might be to do with the server side SRS, I'm not sure though. My main reason for splitting was so that I could be 100% confident that I was not transmitting viacom commands to other players. I think the button split works really well if you have the switches available. I too am really interested to see how viacom and the new voice chat work together. I am expecting that at least initially a similar button split approach might be required. I would hope for a greater degree of simplicity in the longer term. I guess it depends upon how the new voice chat and the existing default ATC and AI menu commands work together.

Oh ok thanks. Always nice to have a heads up if there are problems as I got caught out and couldn't revert once before. To be fair they are usually quite good and I don't think I've ever notice any negative performance changes on DCS.

Oculus don't permit roll backs unfortunately. I remember trying once before. If you have opted into the beta you can opt out and it will revert but that's it. Whats wrong with v35? I assume you mean desktop app.

I'm hoping for those technicals tool. Current aircraft will blow them up just fine!

Thanks for sharing this. When I first started with the Q2 about a year ago I used to use high encoder values with high bitrates however I have read that for the last few months it has been advisible to leave both these on default (0 in ODT) and let oculus scale it for you which it will do down to hardware. I have high end hardware and have had great results with these at default. I wondered if you have had different experience. I also read that for a very long time oculus would set the width for you based on bitrate value. Other than this I run nearly the same settings as you, although my preference is not to super sample and only limit FOV to 0.9 in both directions. Just preference really. I will restest my setup with these resolutions and bitrates (I didn't know width would go that high!) And see if I get anything different now I have been running on default for months.

Oculus tray tool works the oculus debug tool for you. So yes it controls main oculus settings and saves them which the ODT doesn't.

Well.. I agree with the last paragraph... So therefore I use VA as a great workaround. But it's not for everyone I guess.

What about sfc /scannow?

I think I missed that. What's broken with it? I couldn't find the thread.

Not really. No more luck needed, it works. The workaround is fine if you happen to use Viacom/VA anyway. Why bother with yet more plugins if you have something that will do it. It is a Viacom (and therefore VA) thread after all.

It's not quite a completely unrelated conversation... Bit restrictive to have to change threads if a discussion evolves a little... Apologies if you were upset.

I've found if you launch oculus first and the headset is switched on then steam VR doesn't open for me.

Yes, discord doesn't recognise game controllers separately so if you map it direct to the throttle, every other controller you have will also have that number button also activating discord PTT. I mapped discord to a single letter key, and then map viacom to "press" that same key via the button I choose on my throttle Bit of a workaround.... To make things more awkward you have to alter the activation options/behaviour in viacom so it works as a hold and release. I did start with a separate press and release command but found a single "repeat command" worked better. I was having trouble with it either not holding or pressing on and off infinitely. I would presume other keybinds conflict, I really don't use the keyboard for much when I'm actually flying other than a couple of main keys (cant see - VR) not noticed any conflicts though. Viacom settings

Yes, sort of. For most maps there is a folder inside the map files called kneeboard which you can add these pages to, these will show up for all aircraft on that specific map. However this is currently broken for syria and several other maps you need to add this folder in as it isn't there natively. For caucasus and nevada these folder also contain the many airfield charts you see which is nice but I find too many to cycle through, you can delete them but they re-appear on patches and repairs. This is an example of why I said the kneeboard is a forgotten corner in DCS, unless you use a mod, probably like the one above.

Just seen a reddit post saying that there is a Virpil Black Friday 26th - 28th Nov 2021.

Sounds like a tracking error. I would have thought off and on again would fix it.