Jon Fenton

I have one for sale (no controllers) here in UK. Hardly used. Happy to take an offer on it if you are interested and want to PM me.

BTW - I think BIGNEWY means IPD setting, not PD setting in reference to this.

Stealth fighters?

Thank you! Resetting the custom path in the Viacom config seems to have fixed it.

Request for help please from someone more knowledgeable than I! Everything working fine in game for me before latest patch. I use Warthog and Viacom ant the PTT switch worked fine enabling me to call the radio menu up only when requested via an "options" command. However now, irrespective of module flown, the radio menu appears evry time i press the ptt switch, or, it seems, every time it hears a noise in the mike?! This is annoying as I fly VR and it brings up the associated dot pointer for the cursor which needs to be deselected etc. I also notice an "Auto" caption above the radio menu that I seem to think was not there before? It is obviously a setting somewhere that has changed either in DCS or Viacom but I have no idea what. Can someone shed any light? Thanks!

Request for help please from someone more knowledgeable than I! Everything working fine in game for me before latest patch. I use Warthog and Viacom ant the PTT switch worked fine enabling me to call the radio menu up only when requested via an "options" command. However now, irrespective of module flown, the radio menu appears evry time i press the ptt switch, or, it seems, every time it hears a noise in the mike?! This is annoying as I fly VR and it brings up the associated dot pointer for the cursor which needs to be deselected etc. I also notice an "Auto" caption above the radio menu that I seem to think was not there before? It is obviously a setting somewhere that has changed either in DCS or Viacom but I have no idea what. Can someone shed any light? Thanks!

As I understand it, you select the beta program that you wish to enroll in and then that will auto update. For example, when I right click on WMR for SteamVR and select properties, then Betas, it gives me an option if I want to opt into the "beta - public beta" or "lkg_release" or "none". My point about the resolution numbers vs the percentage bar is that, I believe, depending on which beta you select, the bar will show a different scale. ie : 100% in one beta will give be a different resolution than 100% on another beta. ....just more variables to confuse everyone and invalidate comparisons!

The resolution bar figures (percentage vs pixel number) are dependent on what beta for WMR for SteamVR you are opted into. Latest Beta is much higher pixels for percent than the lkg beta for example The whole thing is a mess and open to different people reporting different results using different hardware and software.

....that might be the case, but it certainly gave me a big performance improvement. The advice given by steam was detailed in the other thread and said the following : After the recent detection issues are you still able to launch the Windows Mixed Reality portal and have it detect your headset without issue? To begin troubleshooting, please opt into both the SteamVR and Steam Client Beta. · To opt into Steam Client Beta, open the Steam Client and go to "Steam" > "Settings" > "Account" and enable Beta participation. · To opt into SteamVR Beta, find Steam VR in your Library, right-click and select "Properties" > "BETAS" tab and select SteamVR Beta. You should also opt into the LKG Beta for Windows Mixed Reality for SteamVR. You can do this the same you would for SteamVR. Right-click in library "Properties > "BETAS" > enable Beta LKG Build.

Something I have just discovered (and I think is responsible!) for a huge performance gain on my rig... opt in to the Steam WMR beta "lkg_release" via right clicking on WMR for Steam VR, then properties, then Betas and select it. I had pretty much set up Bignewy's settings and was getting reasonable results with MSAA x2 and a few increases in various DCS setting with NVidia 3D settings as per the suggested ones at the top of this thread, but this new beta seems to have done something to vastly improve things. I note it now selects a resolution of 2708x2648 on the default marker line for global video settings - giving a SS rate of 150%. (Note much lower than the previous Beta which gave stupid high resolution at the default marker) This new resolultion selection would have been unplayable in the previous beta (I was running at 56%) but now this is giving me 50-60 fps and at well under sub 20ms frametimes. and locks into 45fps when things get tough and re-projection kicks in. And the clarity is hugely improved! I have a 2080ti and 9900k at 5GHz and 32GB RAM

Great platform to learn core skills on. And bombing without computer calculations is a challenge!

If you have an Xbox or Playstation gamepad around, plug that in and you can access the Steam VR menus using that. o my Xbox controller you press and hold the left menu button to access the Stem menus within VR and select items using the pointer dot and the controller trigger.

Def the way to go for 2D then IMO. Very happy with mine and it is great to work on outside of DCS too.

I have a Samsung 49". It is very good and, I thought, very immersive with TrackIR etc. ....then I got a Reverb G2 last week and my benchmark for "immersive" changed considerably! Good as the 49" monitor is, it just does not compare with the depth perception you get via VR. Yep, VR is a pain to tweak and set up at first, and it still has much potential to fulfill when GPUs catch up, but IMO it already surpasses anything that any monitor can provide in terms of immersion in a flight sim application. I note your specs and I would recommend you try VR with that system. I have exactly the same spec but with a 2080Ti being the only difference.