Canada_Moose

Just reading this thread and noticing that quadviews and OpeXR toolkit should no longer be used in DCS? Is this just one persons opinion or fact? I use quadviews fixed in Quest 3 and seems to be fine.......

correct radio frequency / channel? Easy comms on or off?

This was a problem before the last patch. Are you upto date?

Some of those settings are way too high for a laptop, especially visibility at 'Ultra'. All the shadow settings are too high as well. SSS, secondary, blur, etc Clouds on 'Ultra' is a killer too

vsync is handled in the vr headset. It should be set to off inn the driver

Might be the GUI scale bug? Change it back to 1.0 if not already

Really need the scale GUI option for 4k screens. @BIGNEWY - Can we get this bug acknowledged? Thx

@BIGNEWY Can we get some insight into what is happening here? Thx. Track is already attached thanks to @joker62 The menu for ATC just says: Departure Ship. Taking Off F11. Parent Menu F12. Exit No inbound calls can be made. Frequency is correct. Radio used is correct Only seems to happen on certain missions.

I changed this as discussed in this thread but now the inputs onto the keypad are delayed along with many other button presses. Not sure the value of 1.0 is good based on my experience

This did not fix it for me.

Im seeing the same thing on the radio. Inbound no longer appears

Not if you know you want to change them before you start the game. This is true for VR where different graphics profiles are used depending on 2D or VR. I can now select the profile before I start the game thus avoiding loading the game, changing the options and then restarting.

VR / Pancake switching is very useful. Graphics options - many of them require a restart if you change them. This avoids that as well.

Just found this out on a saved mission. Dud bombs. This is ridiculous. Surely if you are introducing this hot mess (with very little docs) it would be wise to notify users that old missions would need updating.

Think the OP means the AI

When you look at the ground are there objects in view? Airfields with AI on etc? I notice a slow down at certain 'object heavy' areas like this.

Well, I have seen the complaints about ballooning in general but not one where somebody is specifically pointing to an FCS logic issue directly related to flap position control. This would appear to be a very large oversight if true, especially given the recent FM improvements that were applied by ED.

Has this been reported? It would seem to be quite a large misunderstanding!

Your issue is drag bombs in freefall mode. See linked post. Don't know why this is marked as 'cannot reproduce' its already confirmed.

Wing fold mechanism. Finally been mentioned. Thank you.

Hi all, just installed the Quad Views Foveated Rendering app on my Quest 3 and its really helped with performance and is generally not noticeable so really quite pleased except for one thing. When I glance down, the line between the high res and low res is quite noticeable because of the cockpit screens, dials buttons etc. Is there a way to smooth this out a bit without impacting the benefits too much? Its really only glancing down in the cockpit area that this is a noticeable issue. Thanks for any tips!

I left the up-scaling at the default of 0.66 and the sharpening at 0.8 as per ED notes Working well for me. Not seeing any ghosting

Are there any recommendations on the scaler options when enabling FSR2? It defaults to 0.66

Sometime in the last couple of years there were many requests and questions to ED regarding DLSS implementation. Most of these questions revolved around DCS customers and users deciding which GPU to buy, either AMD or Nvidia. At the time (and feel free to search for the thread) the answer from ED was 'DLSS is specific to Nvidia and we don't implement technologies which are dependant on one manufacturer' Based on this response, many customers opted for AMD GPU's, myself included. Now fast forward to today and ED have decided to support DLSS, which is totally fine. HOWEVER, based on the previous responses from ED regarding this issue, it would not be very fair to the rest of the user base who went AMD to not support FSR 2/3 correctly as well. To simply dismiss users asking about FSR in your post is not consistent with previous ED statements on this very forum.