Bullant

Champion! Thanks mate.

I know this sounds crazy, but try setting Shadows to at least Medium. Entirely removed all in cockpit flickers on hard edges.

Stupid question time, recently upgraded from Rift S to Reverb G2. I am wondering if there is any way to turn off the screen mirroring in WMR? I understand that the screen mirroring in the DCS app itself is zero-low "cost" GPU/CPU wise, but not so sure about the WMR mirroring and it feels really strange having two separate applications mirroring the VR display.

This is a pretty important, and commonly overlooked, line from the WMR guide So the goal is not to hit 45, but to hit ~60. If you are just managing 45 then you are going to get dips below 45 at which point the reprojection will turn off and you will get "stutters". My goal is to get to a steady 60fps so reprojection can do its magic. Turning the reprojection indicator on is very helpful as it will indicate if reprojection is off, on but limited by GPU, on but limited by CPU or not required as you are at 90fps+

Absolutely mate, was just adding some input from the guys who built the headset. To my eyes, and I think that's important because everyone's eyes are different, I see a massive difference in clarity between 54% and 100%. The hornet MFDs are a blurry mess at 54% (without leaning in like I had to on the Rift S), but at 100% I can read them from the normal seated position. With my 2080 I am never going to hit 90fps without turning everything down to minimum, so I'm working with settings that give me a stable 50fps so that reprojection can do its magic. Will be a different story when I get my 3080, at which point I will definitely try your settings. They really have made it confusing in Steam VR SS settings. The first setting is a global percentage. The second allows you to set for each specific game. However, unlike most settings where the game specific setting would override the global setting, the steam SS settings are actually multiplied, so: Steam SS = Global Steam SS x Game specific SS If you set global to 54% and game specific to 120% then you will get an actual SS setting of 65% What the reddit article is saying is that the G2 was designed to need a certain amount of SS for optimal clarity, and that SS happens to be the 100% setting. I guess that makes sense then as to why 100% is the default value!

Nope, less processing, PD is harder on the CPU than SS. Apparently.

Not wanting to dis your findings, but here it is straight from HP themselves ... the 100% setting is where it is at I've actually found that running at 150% and an in game PD of 0.8 makes for an even better experience both in performance and image quality.

Newest version of simappro didn't help me, CPU frametimes still at 28+ vs 10 without the exports.

Glad I am not the only one. i7-10700k@5Ghz 2080 32Mb ram "High" default settings Reverb G2, in game PD 1.0, Steam SS 100% With the WW exports included (and all other exports disabled) - CPU frametime - 28ms With the WW exports removed - CPU frametime - 9ms!

Mate I just upgraded from an i7-6700K@4.2 to an i7-10700K@4.7 (not overlocked it yet) and all I can say is ... do it. It made a noticeable difference to DCS in VR (with Rift S, Reverb G2 is on the way), and rather significant difference to F2020. RTX 3080 will round it out nicely.

Mine is rock solid, although I do tend to go easy on it considering the one that popped off during the review.

Wow I raised that initial bug report 2 years ago, and now it's closed without being addressed? That's not a great look ...

Love my Rift S, but ... hate the audio popping/crackling hate the lack of support would like to be able to read the Hornet DDIs without having to "lean in" so my face is almost against them (virtually). So I've been looking/waiting for a replacement and this sounds like it might be the one!

Was able to complete an AAR topoff from near empty in one go, when the best I'd attempted previously was staying hooked up for 3-5 seconds. Pretty much says it all :)

Both. I use the built in speakers, I tried plugging in externals through the jack and get the same issue. I'm not alone, there is a large thread on their support (aka post here and we'll ignore you) forum.

Man they have really dropped support for the Rift S. And still no fix for the audio popping/cracking that I've had since day one and was promised "would be fixed soon"

Still alive, just super busy. Not really made any more progress on the pit unfortunately, but planning on probably building a version of the openhornet pit.

I am having this problem as of yesterday. Zero ability to connect to any MP server. I have removed all mods (not that I had many). Repaired. Twice. Rebooted my router. No changes have been made to my router, or PC in a long time. Checked with my ISP that I am still on a non-GCNATed connection. At my wit's end, just want to fly with my squadron buddies. Is there anything I can provide that would help to diagnose the problem? edit: all sorted now, it was caused by having the A4 community mod installed. Weird, as it wasn't a problem 2 days ago.

Necro! I have been playing multiplayer every day for the last 3 weeks or so, no problem at all. Yesterday I started running into this exact problem. I've cleared out all mods, run a repair twice, still no dice. Anyone else suddenly having problems. This seems to affect every single multiplayer server, not just the ones I usually go on.

Thanks for all the people making suggestions about using voice recognition, or the mouse, or whatever ... but I am asking in the nicest way possible if we can keep this thread on topic. I, along with many others, would really like to be able to drive the comms menu with controls that can be bound to button presses/keys. There are oodles of other threads talking about voice recognition solutions etc and believe me I have read most of them, but they don't solve the problem we are trying to solve here. So I don't know if ED read this forum or reply to threads, but it would be nice to know if this is something that is possible/would be considered or is just never going to happen?

Just checked - I am using English - UK (as I am an Aussie), will give the US one a go.

Using VR mate, mouse is a PITA. Plus .. I want to use my HOTAS as a HOTAS not a HOTASEWFFTM (HOTAS Except When Fumbling For The Mouse)

Gladman, set a deadzone (I used 10) on the axis and the zoom starts to work as expected :)

Deadzone of 10 fixed the issue.

Yeah mate it is definitely showing as centered at center. Good idea on the deadzone, will give that a go.