nikoel

I respect a man who can say this - If you let me give you a little bit of advice in regards to the DCS settings that may enable you to get the FPS you want. I understand you were using the F14 (rather than the soul and fps sucking Apache) I don't know what settings you're running but here is what I would do Set AA = 0/off | MSAA=x2 | Clouds to Standard | Shadows to low | Terrain shadows to either flat or off | water to low (or medium) | vis to high/medium | Turn the grass/vegetation slider to zero| | The same for chimney smoke | All three tick boxes on the bottom left unticked | Then reduce the resolution you had in OpenXR by say 10% I think you will be pleasantly surprised

Twenty dollarydoos on them not reading any prior posts and having an AMD graphics card

You are correct on all accounts I used 45 as a generally a good number to shoot for as it's half the refresh rate; thus you get the potential advantage of having this off brand v-sync. But the same can be done at higher frame rates. It's not as smooth as reprojected 45FPS as no artificial frames are inserted into the pipeline to form 90FPS; however you don't get the artefacts, ghosting and other bubbles. Based on how important 90fps is to you, I'd say this is not a good solution for you. However this gives an other solution for those who can not stand reprojection and are getting juddering/stuttering at 50-70fps P.S. Changed wording to better reflect this You can use inbuilt steam's verify installation/files. I would also encourage you to use the standalone as this is what basically everyone uses or ends up using. You won't lose your purchases, they can be transferred over

If you have an AMD card. Are able to render above 45FPS. Are really not into this kinky reprojection business but still a connoisseur of smooth tracking and are getting stuttering/juddering. Enable Radeon Chill and set 45FPS min and 45FPS max. Enjoy your locked 45 without bubbles/artifacts. This will come at a small cost of slight ghosting when merging at Mach 1.3. Might be worth the tradeoff (As was pointed out by @Baldrick33 it doesn't need to be 45FPS and you can set it to whatever, however going down to 1/2 refresh-rate still produced best results in my testing YMMV

Try altering the field of view slider inside ToolKit. I got the same effect when I changed it from 100 to 90% to get a better real world perception of speed

You got to google how to overclock your GPU. But the gist is that in DCS I don't let my card downclock and then upclock (a power saving feature which with any other game actually works really well) however it can give kangaroo performance as the card is rapidly up and down clocking. Especially in CPU limited scenarios where the graphics card is waiting for CPU. Here are my settings, (Don't copy and paste them, also ignore the 10% as I have upped the power limit of the card via MorePowerTool). Notice how close Min Freq is to Max. Go through the AMD Graphic Card threads and learn from them as they still apply equally to OpenXR

If you get black screens during play try adding this line into OpenComposite.ini 'enableLayers=false' Then also try without OpenXR Toolkit Also have you locked your Graphics card 100-200mhz of maximum speed it can handle?

Also, what specs are you running mate? I also don't run motion smoothening and have a super smooth 45FPS experience with the Apache in Syria everywhere I go

Okay. I’ll add this can you please write exactly what you’ve done or anyone who is reading this for that matter (in a tutorial kind of format) as I don’t have any experience with this and I’ll copy and paste this P.S. Nawwww… thank you

Anyone with mouse troubles I would like to double check that you’ve read the tutorial properly and applied the mouse fixes (two lines at the bottom of the .ini that I’ve attached) whether it’s yourself or by using mine instead I believe the one on GitHub does this automagically You’re welcome but all credit goes to Jabbah and Mbucchia - I’ve just done the testing alongside many others when you say you’ve upped the PD. I hope you don’t mean the PD inside the DCS settings. It will give you bad performance and worse image No matter what platform you’re using no matter which headset or API’s this should *ALWAYS* be left at 1.0. You can use the per app resolution slider in SteamVR or in this case OpenXR Tools.m Have you tried different versions of OpenXR Toolkit. There is a specific DCS version attached to the first post. There are a couple of official ones which need the file to hack the view

People who are struggling with SteamVR launching make sure you actually install OpenXR Runtime (And of course you have a clean install of DCS as well)

Please launch WMRP before launching DCS - please let me know if any of you get different performance doing this vs just double clicking the icon - please restart your system between the two tries. Suspect something is not able to launch in time within WMRP whilst it and DCS are loading at the same time Also I've been told there is something weird with Steam version of WMRP, and to use MS Store version. I don't know, but thought I'd leave this here as well

Also, turn shadows to Low and Terrain shadows to flat - the exchange is worth it

IPD setting inside DCS's VR Options. IPD is a very poorly named choice - world scale is a much better word for it If you are using OpenXR instead of SteamVR then you can use Toolkit to adjust world scale

Reminds me of a joke I once heard. Goes something like this: Wife calls her husband and says, “Be careful driving home. Some idiot on is on the news! He is driving the wrong direction on the freeway.” Husband frantically replies, “No! It’s not just one guy going the wrong direction! There’s hundreds of them!”

My friend let me guess. You are running a 6900XT (or something the like) AMD has the integration for DX12 FFR only. This means we are second class citizens when it comes to FFR integration for DCS as it's DX9 that parades as DX11. With that said, I am running 45FPS constant in Syria inside the Apache now so it's not needed. We are officially CPU limited. It won't help us, neither will FSR

Unfortunatley the classic Scaling via the 'Developer Settings' Tab is working wonderfully for me (I don't have or use the supersampling inside the ini file) Here are two screenshots of the game running at 100 and then 200 percent How about you dial it up to 300% and see what happens

Okay boys Experimental build of OpenXR Toolkit with support for FOV Fixed Render for DCS Guinea Pigs please click the file below OpenXR-Toolkit-1.0.4-DCS.msi

Hey TED a quick question. I saw you participated in the Apache VR Slideshow Bug thread. Are the findings [posts] with OpenXR or SteamVR? Whilst the performance is smooth for me I was shocked to see 30FPS and on the ground at Syria 18FPS before picking back up to 45 once in the hover/forward flight I suspect we are cpu limited but wanted to see if you had success with other settings?

Hmmm… let me see what I did when I played around with resolution and get back to you

Yes. This is expected behaviour since unticking the OpenXR box will then provide you with dynamic resolution see my other response above

It’s for you to add if you chose so supersampleRatio - float, default 1.0. The supersample ratio in use - this is similar to what you would enter into SteamVR, a value of 145% in SteamVR is a value of 1.45 here. A value of 80%in SteamVR is 0.8 here, and so on. Higher numbers improve graphics, at a major performance cost.

By not having the box ticked OpenXR dynamically changes your resolution based on a MSAAx4 10% calculation of the VRAM Don’t ask why or what that formula actually is as this is all I know According to @edmussthat resolution is around 60-70% for a 8GB 3070

This doesn’t work It’s based off screen resolution. In our case screen being the physical monitor it will show that it’s working if you launch the game in pancake mode below the native resolution. But because it doesn’t understand WMRP/SteamVR/OpenXR this is currently not possible You can give FSR inside the toolkit a go though. In my experience through the moving picture is significantly worse than it should be. I don’t know why