TED

To get those kind of frame times I'm guessing you have to dial everything down quite a bit and/ or be flying at fairly high levels?

For me definitely Radeon Chill on my 6900xt. It is completely smooth, no jitters at all even on 3/9. I’ve done repeated back to back tests and for me no doubt. 45fps seems like a sweet spot. The nice thing about Radeon software too is u can hotkey chill so it’s easy to test it. Right now I’m running 120% resolution and it’s extremely good. Solid 45fps even over cities.

What is your system- cpu and gpu? I'll be more than happy to talk you through the setup. The g2 is just awesome in dcs when all tuned in. You are in for a treat and will love it. I made every mistake in the book setting up and tuning so know most of the pitfalls by now as I came into all this with practically zero computer knowledge in the beginning.

There have been very few things if any I would ever call a “game changer” in terms of updates and mods to dcs. This openXR mod however, I will go out and a limb and say, at least for me, it was a game changer. I’ve been using it for several weeks now and it has made a huge difference. I have more flexibility in adjusting the load on my system, it has an inherently better image than svr and it means I am free from the svr/wmr awkward marriage. I have spent weeks testing and trying different configurations all with their benefit and the great thing is I can easily scale up or down, according to the mission load and still get great performance even in mp. These days I’m playing with 120% resolution on the g2 and it’s so clear, sharp and smooth, I don’t even need msaa or mr. if ED are not seriously looking at implementing this, they really should be. It’s such a low hanging fruit for what is now a proven way to improve the overall sim while we continue (after how many years??) to wait for the implementation of a better dcs engine and multicore.

@DeltaMike I’m actually using very similar setting ps to those you posted. I think the forest and scenery details are a little higher but all in all very similar. I’m all in on openxr now as I believe you are too, so I do use the fsr on the toolkit and set 75-80% with 100% in dev tools resolution. This allows me to use msaa x2 without much difficulty in sp. on my 6900xt I get great results using Radeon chill and locking 45fps. I know some others don’t but for me it irons out almost all micro jitters. I hate the motion smoothing so this is almost as good in terms of smoothness. I do set mr to auto in openxr dev tools. For some reason using chill and also locking 45fps in openxr toolkit works best. I was under the impression locking fps had no effect unless mr was enabled. I’m also still a big fan of process lasso where I separate dcs from wmr on the cpu and set dcs performance to real-time and ultimate performance. Let me know if you try PL and I’ll screenshot my settings. Taking off from Beirut, early evening with few clouds looks absolutely amazing. I’ve never experienced dcs so good as I have in the last few weeks since I got openxr working well for me.

I've started using msaa again and it's still giving good performance. It just looks that little bit nicer although actually pumping up the resolution in openxr to over 100% it gets pretty close to not needing it at all. For what it's worth fsr seems to be working a treat for me with the latest drivers anyway. Definitely gives a little more headroom when set at 80% with little if any noticeable degradation in iq. A good setup for pushing and testing the tweaking is in apache starting at Beirut with late afternoon sun and few clouds, high traffic. Takeoff and do a low level run up to the ridge east of the airport and sweep left around the city. If the setup is all working you'll easily get smooth 45fps until over the city where it may drop to 40 if u r low but pretty smooth. If the system manages that then it will manage anything really. This is generally my testing circuit. I get quite a bit of advantage with the fsr in this case.

@nikoelgood demo videos of how it looks when all is tuned. Very similar to my experience lately. Out of interest what fps are you getting? Are u using fsr and msaa? At the moment I’m using fsr and it seems to work well allowing me to fairly easily adjust depending on whether I’m going to do mp or sp. I’ve had no negative issues with it at all.

Strange. I guess all our setups do differ, but in my case I’ve been testing many different settings and combinations in the last weeks. I rarely get stutters with any settings and I’m pretty sensitive to it. I spent months tuning it out before openXR. Until I push the resolution too much above 100% there’s generally very little but sometimes close in and low it’s noticeable, but for me Radeon chill and locking fps in Xr toolkit to 45 gives a totally stutter free experience and no motion smoothing on.

I have a similar setup as nikoel but with a 3800xt cpu and less overclocking. My 6900xt is for is set on chill and I lock fps in openXR toolkit to 45fps and I get no stuttering. I have almost all dcs settings on high except textures. Something is maxing your cpu somewhere. I don’t think it’s a Radeon driver issue, but it is possible. I do run process lasso and have 2 cores dedicated to dcs and keep wmr away from them. Also I always make sure the wmr portal is not previewing so hit pause on that one and minimize the wmr window and all other windows. i would take a good look at all the background processes either using process lasso or activity monitor to try work out what’s going on in the cpu. I have the openXR resolution at 100% and openXR toolkit fsr enabled then in sp it’s at 100% and in mp 75-80%. I dont use any mr as it’s already totally smooth. a couple other things to check - do u have any Bluetooth devises running? If so try turning off Bluetooth and see how it runs. Try different usb sockets for the headset. Check the internet speed and/or reset the modem. Check bios that xamp is activated. Check cpu and ram timings in something like cpu-z. im able to get a good 45fps smooth over Beirut. im sure you will get this sorted and it’s probably something fairly simple, it’s just a real pia finding that “simple thing”. I think a lot of us have been there in our tuning adventures.

Dump all the reshades and start over with a clean dcs bin folder that's all original. See how your performance is then with msaa off and svr res at 90 % and pd in dcs to 1.0 Do a simple sp test mission on map of your choice. Then just use that as test reference bench. After that I'd install openxr and follow the guide so u bypass steamvr opening at all. Make sure nothing else unecesary is open on your pc and minimise any open Windows and check your Internet speed. If u can run ethernet, do it. If u on WiFi the make sure its fast and preferably 5ghz. This i learnt the hard way as ibwas using a poor 2.5 GHz broadband WiFi and it struggled. Finally Google dcs optimization for pc nvidia. Lots of good adjustments you can make in Windows settings and nvcp. I'm absolutely sure you can be getting a solid 45fps and smooth in apache with high dcs settings.

There is just no way you should be getting this bad performance. I was using a 3080 for a while and running svr at 100%, pd 1.0. Mdaa x4 will tank any performance. Just turn that off and see how u get on. That alone will make a big difference. Other than that, I cant recommend highly enough the openxr route. Check the thread and follow the guide and it's pretty simple. U get more control, plus fsr and should get some more appreciable gains.

I have found i absolutely don't need MR anymore. For me with svr, mr and msaa we an absolute must. Non negotiable. Now I have a better image and smoother without either on oxr. My 6900xt is running very well. My test mission mostly has been apache out of Tel Aviv with high traffic, ultra visibility, low, late sun and broken clouds, shadows low and flat, af x16. So plenty to push the system. Oxr res now at 115% and toolkit scaler to 90% with fsr on. Sharpening to 70%. MR off, fps unlocked. Even over the city at low level it's steady on 45fps and smooth. There are almost no shimmers or jagged edges at all. It is by far and away the best I have ever experienced dcs, and I've tried a fair few mods! I'm done with my tinkering and adjusting now. This is what I've been looking to achieve for a very long time and it's awesome. Now I just enjoy dcs in all its glory. When I moved over to the caucuses and the harrier it was even better with steady 60fps. Whether they fix the bug or not with mr will make no difference to me. I will not need it or be using it. I totally get why they should fix it though, and we all have different setups that work differently. With svr I wouldn't play without it, so I'm sure there are some still in that boat with oxr depending on hardware.

I've got everything working nicely with openxr and had zero problems. I've been like a kid with a new toy since I first installed it. One thinh is confusing me a bit though and that is the relationship between the between the custom resolution in openxr tools and upscale percentage slider in the toolkit. I've been adjusting up and down and seeing various changes. The scale in toolkit appears to raise the amount of pixels as the percentage is decreased. Right now I'm running 115% custom resolution in openxr tools for Windows and 85% in the openxr toolkit, with fsr enabled and working and no motion reprojection. This seems to give a very clear, sharp image with no need for msaa and a good performance. It actually looks as though msaax2 is applied even though it is not and there is of course significant performance benefit to not enabling msaa. So all works well, but I'd like to understand why and what exactly these settings do. It's absolutely not clear in the toolkit user guide.

try dropping the vis range from ultra to high. resolution to lowest on dcs menu (its your screen, not vr headset) lens effects off AF off. Set openXR to 100%. I get steady 45fps in the missions you described with mr on.

For me now with a 6900xt and 3800xt this has been a monumental shift in the right direction, unlocking the true potential of the gpu especially. Big thumbs up to @nikoelfor bringing this all to our attention and getting the discussion rolling. I’ve been resting in sp and mp and tweaking and made a few observations. Out of interest I wanted to see what dcs looks like in vr all maxed out with all eye candy and forget performance, just to see what may be possible. To my utter amazement, not only did it look amazing it was also flyable. I set custom resolution in openXR to 120%, dropped msaa and af altogether as they are unnecessary at this resolution and flew an sp mission with 4 apaches achieving a solid and smooth 45fps. Never did I imagine dcs could look this good. I’ve been flying helicopters for 25 years professionally and spend a lot of time in level d sims for work, and man this looks waaaaay better than our sims. It’s the closest to real flying I’ve seen in a sim. For whatever reason it seems like steamvr was really crippling us g2 users and or 6900xt users. mp is a bit different but still amazing results for me. I had to drop resolution to 95%, shadows down and it rest all maxed.

Ahhh of course. Yep. I don't need it anyway but was just curious. Same for me, last night I was online Syria server with 23 other players, mostly apaches and was getting 45fps and smooth. This was unthinkable before for me. And yes the cpu is definitely the limit. I still see occasional stutters as its trying to load AI. U can notice by just looking at ai and watch fps take a little dip. Incifently I did reduce custom resolution in openxr to 80% with almost no degradation in image but keeps fps a bit steadier.

@nikoelI downloaded the latest beta and all works great but I can't seem to access kr find the fixes foveated rendering options. Any tips or ideas?

It's not strictly true that the oei torque required will be exactly twice that of the aeo (all eng op) tq. The coefficient of drag effect on total drag is not linear. The drag equation is - D = Cd * A * .5 * r * V^2 Drag = coefficient of drag x area x 1/2 rho V squared. Very simply put - So with the reduction of thrust to weight ratio a higher relative aoa will be required to compensate for the increased drag. The net result is that the required single engine - oei tq, will be higher the aeo tq x 2. How much more depends on the drag coefficient of the particular aircraft. I don't have access to the ah64 perf charts but this is common to all helicopters to some degree. Whether it's correctly modelled in dcs or not, I can't say, but it's fair to say it should be more than simply twice aeo tq. Hope that makes sense.

This was very much with steamvr. I just started testing with openxr and so far both sp and mp it's a significant improvement for me. I need to do more tests and I can still see it has some hiccups but overall vastly better now svr is gone so it was probably eating up some cpu processing. I won't say the problem is gone at all, but it's much better and now playable at decent settings. I still maintain we are massively handicapped by single core and no amount of wizardry can make that core work for everything dcs is now asking of it.

It was even easier….there was box in openXR tools . It was a late night!

I agree. Lowering graphics settings has almost no effect for me. I’m currently experimenting with openXR and therefore cutting out steamvr altogether and it helps with some things but I still see issues at the processing level, further re-enforcing my view that this is an issue caused largely by modules becoming more complex, the dcs environment becoming more complex therefore all requiring more processing power to render, but everything being limited to single core processing.

This is definitely working great for me. Only thing is does anyone know how to get rid of the little red box in the tip of my view that is showing a small overlay of performance. Basically it shows red if at 45fps and green at 90. Nice to know but I can’t hide it for some reason.

Wow.. Stumbled on this thread after getting a bit frustrated since the apache seemed to hit the system hard. I honestly didn't expect much but gave it a try. What a huge difference!!!! It's a different game for me. 6900xt all max resolution and I never seen such a clear, crisp image running so smoothly. I never liked steamvr but didn't realise it was screwing so much up. I only did a quick sp and quick mp test so need to tweak and test more tomorrow but so far all default it's waaaayy exceeded my expectations.

It seems like this is getting more and more common. I’ve had stellar performance for a while now in both sp and mp, but this week mp dropped off and is borderline unplayable at times with stuttering and poor fps. it seems to me, and please correct me if I’m way off, but adjusting graphics settings down does have some effect but no where near as much as one would expect. I reduced resolution from 100 to 70%, msaa off and almost no difference to fps. I can see the huge jump in cpu load in mp since a few weeks ago when monitoring it. This all leads me to suspect that our problems are far more cpu processing limiting than gpu and pure graphics. Whist I’m really pleased with all the wonderful things ED has been doing recently with new modules, ai, and systems to existing models, my feeling is very much that we have reached the saturation point whereby no cpu can process it all effectively and we have overload as we are existing on an engine limited to just a single core. All of these great things ED are developing are therefore never going to be able to be utilized fully, especially in vr whilst the engine is being throttled in performance potential. Again, I may be way off, and many will disagree with me, but my view is simple - I’d be very happy if nothing else was released or developed until multicore is implemented, and all effort went into this, therefore actually allowing us to actually benefit from all these great new developments. Until we actually get multicore working all the great developments are somewhat a waste of effort, especially for vr users, as all they do is serve to further overload an aging and crippled engine. And until we get multicore, dcs is rapidly becoming an SP game as MP becomes more and more overloaded and handicapped. Amd 6900xt, amd 3800xt, 32gb 3600hz ram, 1tb ssd.

I’ve just started getting this exact same issue this evening. I’ve been shooting target since day 1 without any problems then suddenly today in mp servers he does exactly as the OP describes. All parameters are met, he says “engaging” or “firing” but never actually fires, I tested with different ranges, heights, laser codes, LOBL, DIR, HI, LOW, LOAL. nothing. In the end I left the server and gave up.