TED

Good write up @nikoel. It’s great to see more people testing and tweaking and it’s clear to me there are different routes to go to get great performance. I agree with a lot of what you say and may well give a go. For now I’m a big fan of motion vector and motion smoothing so tune to that. I totally agree with the pixel count being all important. My view is very much to get it up to or as close to native resolution as possible then implement fsr to allow some other benefits and msaa. I have both a 3080 and 6900xt and in my view the 6900xt is a clear winner in dcs although it took a bit more tuning and rethinking of the logic. But in the end I was able to get considerably better, smoother and more pleasant performance from my 6900xt, mostly with a10c. There are of course huge differences from terrain to terrain and multiplayer often requires some other sacrifices and there it is quite personal on what you fly and what you are and are not willing to let go. im taking a break from multiplayer for now and focusing more on campaigns until we see multicore and Vulkan allow us to squeeze some more out of the CPU’s in high unit terrains. with native resolution on my g2, mv and motion smoothing, msaa x2 it’s very smooth even looking out the side at low level. Most dcs settings high, but grass and clutter off, shadows flat. With openfsr applied it’s really excellent performance.

im running motion vector (auto - not always on) and motion smoothing (enable not forced) so that locks it pretty much at 45. I’m not totally convinced how much the Radeon software fps control works but I just leave it alone now on 45. A few other observations from the last couple days. OpenFsr makes a huge difference for me. I’m running 0.9 sampling and 0.8 sharpening. Force dx11 is critical in wmr. clutter and grass detail in dcs has a much bigger effect than I expected. I now leave it at zero and barely notice a difference visually but big performance effect. If you have not tried adjusting this, set it to zero and see if it helps. Make sure supersampling is off in svr. Nevada map is one of the less taxing but flying low over Vegas is a good test. With my settings now of 2x msaa and 4x antisopotric, 130% svr res, 100% per app setting it’s all very nice. im using 90hz on the headset. I tried 60 and while it did increase some performance the flicker was just too much for me for a minimal increase in performance. In fact in some situations I had more stutter with 60hz so it’s a no go for me.

I had same problem today. It all worked fine when I did the full mission but I later tried to just skip to the AAR bit only and the tänker just wouldn't respond. Frequencies all correct and I could hear shell reporting his positions. I wonder if a trigger is missed or there is some timing in the mission edit for the tanker to start?

Done.

Check out this link too. Some useful stuff. https://www.youtube.com/watch?v=14QSlEvvzoA

First make sure motion smoothing on in svr. Dint go above 2x msaa in dcs Very important. So much so I will say again - very important - check you have removed every last bit of your old nvidia software and drivers. Check gpu settings in windows are set to ultimate performance. In task manager or process lasso set dcs.exe to highest priority (real time) Minimize all other windows except dcs on desktop. In Radeon software turn pretty much everything off to start with in graphics settings. Then add perhaps Radeon boost. Increase min frequency to 1-400 under max clock frequency. Increase max power to 15%. Check the video I posted earlier. Go through things in this thread slowly and follow as many of the steps as you can and check dcs again. You should be able to get a lot of improvements. Fpsvr can cause stuttering in my experience btw. check your ram and optimize if necessary. I use gpu-z and cpu-programs for this. Both free.

Ah ok thanks. That explains it. I'll try that. It's a bit odd as I seem to remember being able to set the cloud base right down to the deck previously but was probably a bit of a while ago now.

I've been trying all day to make an ifr training mission with an ILS to rwy 21 at Nellis. I used the overcast preset in mission editor which should put a cloud base to 300ft. But it doesn't seem to. I tried everything including dragging the base down to its lowest. Setting fog with 2000ft thickness and visibility of 1500ft. Even so I always seem to break out at about 800-1000ft agl on the ILS. What am I missing? Anyone have any ideas?

I also found this to be very helpful, although I did set it about 500 under my max speed, but definitely reduced a lot of the spikes.

You make that look very easy. I don’t know how you do that. I find the hands disappear too often and lose tracking. I will have to play with the settings again and see if I can improve it in the a10.

This I totally agree. I’ve tried leapmotion, mouse, vr hand controllers. Nothing is better than some physical controls and switches. As baldrick says, pretty quickly your muscle memory learns where they are and it’s very easy. I’ve taken to making my own switch boxes. Very easy with a cheap Cnc machine and some cheap switches. Then just mount them where ever.

No worries man. Believe me, we all did too! It’s a minefield in the beginning but starts to all make sense after a while once you see the logic of how it all works. Keeping it simple is the key.

Steam vr global resolution set to 100% and per app setting to 100%. In dcs pd set to 1.0. with fsr I adjust a bit but start with 0.85 for the scaling then 0.9 sharpening, radius around 0.9. I allow hotkeys (set to true in config file) and Ctrl set as modifier , the can just press ctrl and f4 to increase sharpness and ctrl f6 to adjust radius once in the cockpit.

Nope, I didn’t touch any of those settings in Radeon software. The only thing I have now enabled is in custom tuning - setting minimum frequency to 2100mhz and upping the power to +15%. There is a lot in the Radeon software that has no effect in dcs. I don’t think steam vr integration works for dcs and g2 so never used it. To be honest I do the minimum necessary in the Radeon software. I’m not using steam openvr either. Other than that I’m just using wmr for steam and it’s works perfectly fine.

Yep, I agree. But we often also fry our systems with so much other junk ,apps,software, settings and dont realise what it's doing. Then blame dcs for the problem! . Don't get me wrong, I don't easily or often defecate rainbows. I'm quick to voice my issues if I think somethings not right. But credit where its due, and for me dcs is running beautifully right now, so u guys have done something pretty damn right. I couldn't be happier with dcs right now. Onward and upward. Can't wait to see what other improvements are in the pipeline. Not yet, but thanks for the tip. I'll check it out.

Glad its all working out for you. There’s so much to learn and try, especially as we are all still a bit nvidia biased in our thinking, but I totally agree - the 6900xt is very well suited to dcs. I have no beef i the argument, I’m just a lucky bastard who happened to end up with both a 3080 and 6900 and got to play extensively with both. Thoroughly enjoyed it too, but I have to sell one as I will only use one. After several months it’s just obvious to me now the 6900 is the better card. I’d have been totally happy with the 3080 as well if I hadn’t had the choice. I just flew one of my test missions in the a10c2 - Syria, a couple Sam sites, some btr groups, all low level, over the trees, through the canyons and valleys, engage the sams , the; onto the btrs then low level back to ramat. Smooth as can be, no jitters, judders, spikes, even low, through tight canyons looking 90 degrees to the side - just a dream come true. I’m so damned happy with my setup and dcs right now that I’m enjoying my sim flying more than my real life job flying . I couldnt ask for better performance right now to be honest. It’s just doing everything I want. I feel for the likes of @BIGNEWYand others, constantly in the receiving end of complaints, but the reality is the variables in all our systems that are hard to factor for, but if a complete idiot like me can get it to work with some tuning and tweaking and a lot of trial and error anyone can, so I’ll keep posting my findings and hopefully will save someone some time and money and they can enjoy this crazy hobby as much as I am right now. The latest settings I’m running are 100% svr and per app res. 1.0 pd, msaa x2. Fholger fsr, mv auto, motion smooth on, all dcs on max, cpu core affinity to separate dcs and steam vr, the amd tuning as per the video linked, amd software min freq 2100 max 2650, power set to +15. All tested, same results with a10, f16, AV8B, ka50. F…… awesome, and I’m ocd about jitters and stuttering so anything and I notice it! Amd tuning

Almost the same set up I have. The only difference is I have a 3800xt cpu. You should be able to get very good vr performance with that setup. Smooth and jitter free pretty much at at least 100% svr res and pd 1.0. i say that because I am getting that. I download the whole Radeon software. You can use msi afterburner as well if you prefer it but I just find it all simper to use Radeon own software for over clocking, undervaulting, tweaking and messing. Definitely use something like ddu to remove absolutely all nvidia drivers and software. I have been continuing the testing and now focusing more on single player performance as mp server is so variable depending on factors outside my control. It’s at the point now on mp that sometimes it’s fantastic performance, then the server mod changes something and performance drops a bit. Generally always very playable now and stable though. In sp I’m now using mv auto and motion smoothing in svr, 100% svr res, and sometimes higher. All settings high. A few other things I’ve done and realized. Empty room for wmr helps a bit. Making sure the wmr portal is in pause and minimized helps a bit. Cpu affinities to separate dcs and svr, wmr. General windows health stuff with as little running in background as possible, gpu performances set to dcs as highest possible, everything else power saving. I’ve also installed the fholger openfsr and that helps quite a lot. Took a bit of adjusting the settings for sharpness and radius but now looks really good. Generally I use msaa x 2 now as well to try control some of the jagged edges. Turn of fpsvr - it seems to definitely cause spikes when it’s open. all in all now sp performance is “butter smooth” even looking out the side, low level in a harrier or a10c with lots of ai. Flying around in gazelle or ka50 is very smooth so I’d expect the Huey to be as good or better due to the lack of any other screens in the cockpit.

Now that is an interesting idea I hadn’t thought of. I will have to try that later. Pausing the wmr screen makes sense. If nothing else it will help unload the gpu and cpu a bit, helping frametimes.

I get no warping or ghosting. Definitely I don’t use Radeon chill. U use either default or under vault. early on I did get warping with mv but force dx11 sorted this I think. There are just so many variables it sometimes gets a bit hard to know exactly what affects what, but I’m trying to slowly break it down and simplify it. Right now it’s all working good. I have definitely found I need to take the resolution down a bit in Whatever reason mp performance seems has have got worse in the last few months. I just do this with pd and leave everything else in svr. For mp often I need around 0.8 now.

I’ve actually modified things a bit and now using mv and motion smoothing as well. So far it works well. I’m constantly testing new things but it seems this definitely works now. I actually set mv to auto now, not steamvr per app setting.

Same for me. Amd 6900xt. I've tried with both 3080 and 6900. Happens with both, but significantly worse with 3080. Cpu barely stressed. All other times frame times are under 15ms. As soon as get near other units it can start spiking with high frame e times and low fps. Usually recovers after a while.

Use something like fpsvr and try to see also if u r being bound by cpu as well or gpu. These issues are quite common but the good news is once you know where to look they are often relatively simple to work out. There are just so many settings and variables between windows, svr, wmr and dcs. Make sure your cpu is not working in lots of background processes. Just check task manager for this. Set priorities in task manager accordingly with dcs being highest and vr compositors also being high. Anything else can be set to low priority. You can also set cpu affinities in task manager and separate the cores dcs and svr are using. I’ve had some success with this but it’s not the first thing I would do. For offloading the gpu - Make sure your monitor resolution are all set to lowest, both through windows and also in the dcs settings. In windows settings, system, display, graphics settings - u can select various apps and options and set their gpu priority to high performance (often defaulted to “let windows decide”) Likewise set any other other large apps to power saving if they are not critical. Have all other windows minimized when using dcs. Miniseries wmr, steam settings, and anything else. Ideally nothing else should be open, perhaps srs and voice attack, but minimize them too. Make sure HAGS is off. Game bar off in windows settings. start with these few things and see how U get on. If you’ve done all that, then it’s into bios settings and usb settings and overclocking.

https://forums.eagle.ru/topic/290816-amd-6900xt-tuning-and-settings-for-vr-in-dcs-my-optimal-recipe/

I created another thread specifically with the steps I've been trying and using and will try to update it as I learn more but so far it's working very well and now I to the very small % tuning. One thing I did find I needed to go back on was the cpu tuming. Dcs definitely works better on dedicated cores not all cores, and from those cores you should try to remove as many other heavy processes as possible, but not all. I created some problems when I removed everything as a lot of system processes for some reason need to be on all cores. However separating dcs, steamvr, wmr and any other programs/appa running in the background that are not critical to the system is the most effective way. I'd actually start with just separating dcs, wmr, voice attack and see if that works. After that u can fine tune and take one process at a time off the dcs cores and make sure it doesn't affect overall system stability.

I should add one more important point i just found out as I have been adjusting further. Be careful when setting core affinity. It would appear especially system processes need to be on all cores.