Hoirtel

I do agree with nearly everything you say, one bit is I doubt the professional customers want a whole world. I wouldn't expect much real world transit training is required. After that it probably doesn't matter what or where it is. Mostly just tactics and working together rather than anything else.

To be fair world maps have been a thing on civilian flight sims for a long time. Even back in the 90s a world map with some scenery was possible. So today it could be much more do-able with reasonable detail. I could see the ED store being filled with various airfields and high detail scenery packs. That way we could build the world we want, and transit across the areas we are less interested in, or just stay in the smaller high detailed areas similar to what we have now.

It should remove buildings too

I guess the scenery remove trigger could provide a workaround? Or a helicopter!

I can agree with others here G2 or Q2 its pretty subjective with people liking both. Perhaps the Q2 is a bit easier to set up if you haven't done it before. However given that today is 20th October 2021 don't buy any VR headset. This month will see some major announcements from Varjo, Oculus and Pimax so its possible landscape is due to change. As for input.. I use the mouse, and click as much as I can in the cockpit. I don't find this a problem. Some buttons will need to be bound to hotas and button box (maybe part of a throttle) is handy for flaps, gear etc. Try not to use the keyboard at all. Its easier than you think. I can find the esc key for menu, and have f buttons marked for views (although these are rebindable). To be honest even when I was in 2D I could never remember any two or three combo keyboard modifiers anyway!

Yeah, I've never really been sure how/when to use it, so I haven't. The fact that it is under a cover could possibly mean that it is only for occasional short term use? Taxiing? I have spring loaded pedals and only switch yaw AP on when cruising but I'm not sure this is correct. Hence following this thread!

I think he is referring to the pedal damper on the front cockpit panel, under a red cover.

Ah ok, I've not tried VD so not much help. Just if it helps airlink seems to do that if you have a bitrate set at anything other than 0 (default). Might not be your issue though.

have you tried airlink?

No, as oculus can't achieve that either. Possibly just due to settings, we wont be able to see much detail on the recorded mirror

I had to set up something similar as I really struggled to use both in the method described in the viacom handbook. Best to keep them to separate bindings if you have the buttons. Things also get additionally complicated if you are trying to use discord on a PTT also. The binds to create this are done inside viacom and SRS, just decide what you want and go through all the applications to set it up. FroZone's is similar to what I used to have but I separated SRS radio select and PTT so that the Viacom Tx1 and Tx2 also select the same SRS channel. Holding either of those means I speak to viacom, releasing and pushing the centre of the hat I speak over SRS. This allows me to bind another of the four way for discord PTT and another for intercom. Pretty confusing but does work once you have it set up and you can fly on servers that use SRS or discord or both without having to rebind and with full control over who you are talking to. Worth noting that for added annoyance discord does not seem to be able to tell different usb controllers so a PPT on my warthog will also activate PTT for the same number button on all the other controllers I have. MFDs, joystick, button box etc etc. I got around this by mapping the discord PTT to a keyboard key, and then using viacom to map my warthog controller button to activate this keyboard key - a kind of pass keybind through. So many workarounds! More complicated than a real jet probably...

Good point about the reprojection... But as the answer said I think DCS supports varjo natively so an addition to what you have said above. Not sure as it's only been a commerical thing so far...

Not sure if it's related but one of my wheel brakes axis started to behave odd. Same showing activity when there was none and then not being able to deflect it fully. Turn out the bolts to change the pedal pitch were not don't up tightly enough, the pedal moved a tiny amount and threw it all out. Reset, re tightened and recalibrated. Good as new.

I am getting the sense from the internet and some marketing emails that Varjo may be due to announce a consumer grade headset on the 21st this month (October 2021). I seem to remember a while ago a post from ED stating that Varjo was going to be supported natively. Does anyone know if this is the case or do they require the steam vr "bridge" as with WMR.

Oculus quest 2 working with dcs just fine.

Same here. A little piece of tape on the middle buttons of each side helps me know where I am.

I hoping that it reduces the strain in areas with lots of objects so that there isn't such a large difference in fps.

So you need to have steam, and then get steam VR. Add DCS to your steam library (assuming it is not the steam version) and open it all up. Make sure enable VR headset is checked in the DCS options. It's a bit of a faff but because WMR is not natively supported by DCS they need to talk via a steam VR. Once you got it all set up it's fairly easy. Follow the linked guide above.

Check enable VR headset. You need to bridge DCS through steamvr to use WMR.

Happens when things start to get a bit too much. Try upping the VR pre-rendered frames in Nvidia control panel (if you are Nvidia user). It can help with this.

Yeah I think the shimmering did get worse in 2.7 but this is also a VR issue as it happens other VR titles too. High resolutions are the best way to reduce it but in the future with higher res displays and faster GPUs it will improve. Are you running oculus v33? Do you have link Sharpening enabled?

So I have recently been using the Nvidia Control Panel MFAA set to on (on top of DCS MSAAx2) and I really do feel that this helps reduce some of the newer aliasing that the link sharpening has brought in. The MFAA option has always worked in DCS VR but previous had very little effect visual effect combined with a minor impact on performance and I never felt it was worth it. I have been doing some testing just on my own bench tracks and but not recording frame times etc. I mainly do it all subjectively. MFAA still has some minor performance impact but I am now going to fly with it for a while as I really think it is helping with the new aliasing problems. The most obvious visual impact I can see where is making a difference is the long grass. If you have grass and clutter on, load up a C&D aircraft (I've been using channel map) and look out. Without MFAA the link sharpening really creates many small sparkles across the grass tips MFAA on seems to really reduce this. I'd be interested to see what others think if they also try this. I may try and do some proper frame time recordings to really gauge performance impact.

For a 10 series card look to using a rift S, quest 2 will probably run at base resolution but things will be blurry. I run Q2 on 3090 at full resolution, 80hrz and x2 MSAA. No headroom for supersampling. This is fine most of the time, some stutters over towns on channel map, syria. Marianas goes pretty bad. VR always wants more, older cards are better with older headsets as smoothness is the key. You do need a beefy processor too.

Inline with how ED want us to manage liveries and kneeboards for aircraft, I would prefer them to enable custom kneeboards from within the saved games kneeboard directory, but as expected this does not work with any of the maps, not even Caucasus or Nevada. Generally there is a surprising lack of attention to the kneeboard implementation although I am expecting ED has something in the works as I the current kneeboard isn't really properly implemented in VR. Although I use it as it is and it doesn't bother me that much.