Bader242

I had a similar issue. Launching the game as a VR session with the Skate Zilla 'DCS Updater/Launcher' fixed it for me.

Nealius - Were your drivers up to date prior to installing 528.02 or had you skipped a few updates? I've taken a performance hit with my Q2 - crazy screen tearing and stutters - to the point where it's back in the drawer. I had it running sweet as a nut, even in multiplayer but something just happened and I can't pin it to anything I've done other than the occasional driver update. Have you tried the latest 528.49? I'm about to as I've nothing to lose!

Update: OpenXR is now working for me. I launch a VR session via the Skate Zilla DCS Updater software. Under App.Settings, select Rendering Driver as SteamVR API and then launch the VR session by clicking 'VR On' from the left side options. This was after running the 'Per Game' install of Open Composite discussed above. However, having now got OpenXR working at circa 52fps, I have to say I am now returning to my original set up without Open XR as explained in the link below. I get 72fps with this method.

Is that the case even when I don't have the Steam version of DCS?

Update: No joy I'm afraid. I've done the per game install but still can't get the OpenXR menu up within DCS. I've changed the F2 key bind several times both with modifier and without to ensure there are no key mapping conflicts. I have found a log file in the Open Composite folder which says: [2023-01-20 20:54:12.204] Config::Config:207 - Checking for global config file... [2023-01-20 20:54:12.205] wini_parse:172 - No config file found at E:\DCS World\bin\opencomposite.ini [2023-01-20 20:54:12.205] Config::Config:226 - Checking for app specific config file... [2023-01-20 20:54:12.205] wini_parse:172 - No config file found at E:\DCS World\bin\opencomposite.ini Any ideas? Many thanks in advance.

Thank you for replying. I did not do the above so will give it a try, though as DCoffey mentioned, the link is down at the moment. I'll post results for community feedback.

Recently installed Open Composite and OpenXR Toolkit. Works a treat in MSFS but I can't get the menu to pop-up in DCS. DCS is listed as one of the recognised applications in the Toolkit and the blue box is ticked. I've cleared all F2 and Ctrl keybindings in DCS just in case there was conflict in the background. I followed the install guide, repaired DCS and so on but Ive clearly done something wrong but not sure what as it's working in MSFS. I've searched historic postings but can't find any similar topics/experiences. Any ideas? Hope you can help. I have a Quest2, MSFS is Steam and DCS is non-Steam.

My list of multiplayer servers is only 9 in total. I've no filters on and have checked my firewall. Not changed anything - just returned from holiday and find this. It will be a local issue I'm sure. Anyone had the same and what was the fix please? Hope someone can help. Cheers guys.

Just for general community info........ I've just installed the new Nvidia driver 511.23. I've not tried it under VR conditions or played with any new features yet but in normal 2d it's a 0.6FPS drop (80.2 to 79.6) which is okay by me. I haven't noticed any onerous or concerning differences e.g. stuttering, flickering, etc. Test conditions were a simple mission created for a Hornet at 1,000ft on approach to Senaki using FRAPS for benchmarking. Logging started at the exact some point in the terrain for each run and an average of 3 runs before and after install of the drivers. Previous driver was 497.29. PC is i7 11700 + 3070 + 32gb 3200hz ram

My tech skills are limited to what I can find on Google rather than hard core experience but I have been chiselling away at my Q2 settings. I find the Ocullus software manages things pretty well now and no longer use OTT. I have MFAA on in NVCP and all looked pretty good apart from the stutters. My DCS is on an M2 drive and I only have 16gb ram (32gb arrived today ). I noticed my stutters coincided with massive access to my Barracuda disk drive i.e. 100% load. I therefore moved the page file to the M2 Drive and that has stopped the stutters for me. Rest of PC is i7 11,700 and RTX3070.

Do you have Terrain Object Shadows on? I’ve found the shadows form a big part of the shimmer so I’ve turned them off. You don’t notice they’re gone but certainly notice less shimmer.

+1. Oculus software tweaks give me the best visuals and performance now. I run at 72hz with the slider one step off the far right whatever that resolution is. No longer use OTT but do enable sharpening in ODT. I made these changes after watching more recent You Tube content (you gotta be careful of old/outdated content on there now) that suggests OTT has been overtaken by Ocullus software advances in 2021.

I turn off Terrain Object Shadows because a great deal of the shimmering is the shadows on fences/trees and not the fences/trees themselves. Looking at your settings, it looks like you’re doing that? The only other thing I saw an improvement with was turning on MFAA in Nvidia Control Panel.

I experience a FPS drop if I go into the theatre map and then return to cockpit view. Not all the time and only in multiplayer. Is there any action like that you are doing that is perhaps prompting the drop or is it totally out of the blue?

I must have watched every You Tube video on OQ2 settings for DCS. I was pretty disillusioned shortly after Santa delivered my OQ2 but quite happy now. What I’ve learned so far: 1. According to many, Ocullus app runs things pretty well these days. I have my device settings as 72hz and the slider one step off the furthest right position. I find cockpit text is clear and is marginally sharper than any resolution settings I tried in OTT and DCS. 2. The shimmering annoyed me but on closer inspection during all the FPS tests I did, it’s primarily the object shadows that shimmer (around trees, etc). I’ve therefore turned off Terrain Object Shadows and am finding it much improved. There’s quite an FPS boost too. 3. I have Visib Range on Medium. If you slide ‘Tree Visibility’ to max, it masks the ‘trees sprouting out of the ground in front of you’ characteristic of low and medium Visib Range settings. 4. I no longer use OTT having watched a few videos suggesting the advances in the Ocullus software this year have pretty much made OTT redundant. Don’t shoot the messenger but I tend to agree - I’ve personally not seen it add any value despite many different setting changes. 5. I enable sharpening in ODT. 6. My Nvidia Control Panel settings are default apart from MFAA enabled. This improved what shimmering remained for a very modest FPS hit. It kinda induces an MSAA x3 level if there was such a thing in DCS - a nice halfway house. Hope the above points are of some use to those of you out there who, just like me, got a VR headset for Xmas and entered a whole new world of pain! My PC is an i7 11700 + RTX 3070. Happy flying!

Thanks for responding. It's on the Caucasus map where I am encountering the problem. I have an 17 10700, RTX3030 8GB and 16GB RAM and struggle to get over 36 FPS at 1,000ft in Caucasus. Okay, some may say 36FPS isn't too bad and I agree, but it's so unstable. If I so much as sneeze or go on the F10 map, the FPS fall through the floor. I've spent most of Xmas watching You Tube optimisation videos - all of which contradict each other (I accept the ageing of content is the main factor here). I have tried settings in OTT, ODT and NVidia CP, all to little or no effect. To be honest, I'm finding just letting the Oculus software do it's thing is giving me the best results with the graphics slider far right and 72hz. At 80hz and above I get stuttering. Graphics settings in DCS are at the 'typical' VR settings - nothing over abitious. Just can't understand why it runs so poorly on what is a not too shabby PC. I'm resisting a clean install because of the hassle factor. Frustrated to say the least.

New to VR with the OQ2. Flying low level I am getting 36 FPS but when I view the F10 map and then return to the cockpit I am down at 27 FPS. Is this a common issue? Is there a solution?

That explains it then - I thought that was the case. The video posted by Evilnate above suggests a slew > designate > pickle > slew > designate > pickle etc approach that I did try but with mixed results. To be fair, I was in a hostile multiplayer environment so was rushing a bit so I’ll create a test mission and experiment. As an aside, I presume ED state ‘correct as is’ because that’s how it worked with a real FA-18 dropping real JDAMS. Anything less would be disappointing.

Hi all, I’m struggling with dropping multiple JDAMS in a single pass using TOO mode. I have watched several vids on You Tube that show it but I can’t get it to work. Has ED changed something? I’m wondering if the vids are out of date? If it is still possible, could someone post a link to a vid that shows the up to date method? Many thanks in advance.

+1 Yes, I am seeing this too - just random drop outs of MIDS. My experiences of the last week or so are: a) Random dropping out of MIDS at range. b) Merged with a Mig, lost visual so checked SA and he’d vanished from that too. c) Lost MIDS where there was a donor F16 ahead of me flying hot towards the bandit. The last one left me particularly baffled. I assumed it was correct as is and that I just needed to read Chucks Guide again but now we’re here……….

+1 I am in the process of learning the targeting pod but have been struggling a little as the available You Tube content doesn’t seem to reconcile with what I find is happening in the cockpit. I dismissed it and assumed I had missed some detail somewhere but my problems have centered around what is commented above. I will watch this thread for further developments.

I have recently gone through the very same learning curve for the radar. Firstly, I watched all the relevant content on You Tube. I spent an evening searching and saving videos to ‘Watch Later’. I then viewed them in order oldest to newest. The thing is, they’ve generally added more functionality as time’s gone by so watching them in order does give you an understanding of the evolution. Secondly, as already suggested here, I created a radar practice mission. However, my mission had a single unarmed MIG-29 that started 80nm out heading hot straight at me. At about 30nm it turns 90 degrees to starboard and after 5 mins or so it then turns another 90 degrees to fly cold away from me. I found this mission particularly helpful in understanding the scenarios where you can lose lock in the Hornet. Just keep replaying the mission over to compare different settings. Good luck. Hope the above is of some use.

My first thought was crosswind which can be a challenge at times but if you’re sure that isn’t a factor then how about increasing the dead zone on your joystick?

Yes, unchecking Compatibility Mode for DCS.exe via the Properties menu resolved my issue. Thanks for your help.

Thanks cOff. I’ll try that and post an update here. The PC is only 6 months old from PC World (made by Wakefield based company PC Specialist) and came with ‘Windows 10’ pre-installed so not sure where the Windows 8.1 throwback is coming from.