Charlie-1

Thanks, I did follow the instructions and OXR is running, but for me SVR is clearer and headtracking is more responsive. It was worth the try, but no benefit for me especially not worth the loss of necksafer. I have to say I am really pleased with the VR performance in DCS at the moment, but we all know that may not last!

Guys..I'm running a Reverb G2 and thought I'd try the OpenXR mod to see how VR perfomance improves having read everyones feedback on the positive results they experienced. The strange thing is for me the performance is worse with OpenXR than with SteamVR which was really dissapointing. I can run solid 45FPS with reprojection at 0.8PD in DCS and 100% SS in Steam VR, but the same settings with OpenVR result in 30FPS. All I did was replaced the two files 'openvr_api and D3DCompliler_47 in my bin folder and added opencomposite.ini. Am I missing something? When I installed OpenXR Toolkit, I just get a blank screen, Any ideas?

I just cannot get smooth view panning at 60Hz and do not know what else to try. What I am seeing in DCS now is the image is stepping round, up/ down etc rather than pure panning , which I am seeing in other Sims. I have tried Vsnc on/off in game and NCP, limited frames to 59, 60 or 61, turned on/ off adaptive sync in the monitor. I have tried with Open track, mouse, joysick control but nothing can pan without it looking Jerky or more like 20Hz movement. If I set my monitor to 100Hz is much smoother, but it limits my graphics setting choices to maintain FPS. I've seen many posts about similar thing with Track IR, but the stepping/ jerky issue I am seeing is regardless what is being used for view rotation.

I spent the best part of a day trying to get smooth headtracking from the cockpit view after the 2.7 update, but then realised the problem is confined to the Channel map. I can see overall FPS performance has improved a lot on this map after this update, but even with solid FPS matching the monitor refresh rate at either 60 or 100Hz with Vsync on I just can't get smooth turning of view from the cockpit. I have tried with mouse view with same result, Other maps are working perfectly smooth with head truning.

I've had that quite a lot...I presumed I'd gone into a different mode or something as has come back, but without really knowing how. I've also lost the ground radar elevation adjustment without knowing how?

That would be a help wouldn't it. . The only reason I looked to use the SA was because I couldn't see anything on the surface radar.

Oh I see.. so the plane isn't detecting them, they're loaded into the plane's data with the map:megalol: Thanks for clarifying. I thought I'd used them before to get a target on a ship with the Flir. Must have imagined it.

Thanks but how come it detects and displays land based SAMs but not ships?

As the title says, but is there a reason for this or a bug?

Thought I was going mad, just reinstalled the module to see if it was corrupted or something but no luck. Especially as those indicators are working in my 2.5 install.

I don't know the cost my friend as its evolved over time. It started out as a min spec VR capable (just about) machine 4 years ago and cost less than the just the graphics card in it now. Thing is that PC ran DCS 1.5 really well even in VR, but that changed when 2.5 with 'deferred shading' happened. I think we need Vulkan and some major code optimisations to happen next. :(

I'm guessing you're not flying VR or with head tracking?

Managed to capture some performance measurements in 2D, I've not tried VR yet based on how how its running so far. Buildings and trees seem to be the usuall enemy for FPS. See video below with stutter over built up areas at 1:20 and 6:30

Not good performance at all...Worse performance than Normandy when released and pulling an RTX2080 down in to 40 - 50 fps at just 1920 x 1080 over built up areas. Other maps running perfectly at even 3000 x 1080 pixels. Why do these maps always look so 'clinical' too!

No worries, sorry I missed that one. I'll try the examples you posted and see if the stutters are repeated.

Do you have track recording enabled? I found the best way to fix random stuttering is to disable track recording with an autoexec file with the config file in the saved games folder.

I'm not sur if this belongs in performance or VR section, but wanted to ask if anyone else has noticed a backward step in VR clarity in 2.5.6? It most noticable trying to read MFD's which are once again fuzzy, whereas 2.5.5 I had them very legible from normal seating position. It's most noticable in the FA/18 even with the readabilty MOD. It seems like the same step backward in clarity when deferred shading was introduced. I would post images, but obviously not easy from a HMD.

I had this and cured it by disabling track recording. You can see the thread/ history here incase it's the same casuse for you. https://forums.eagle.ru/showthread.php?t=263567

So sorry, it's me. I was opening 'Carrier take off' not 'Super carrier take of' :megalol: Thank you.:thumbup:

I'm not seeing any animated crew when starting from the FA-18 missions. What am I doing wrong?

So I've had some more time to do VR testing (Rift-S) with 2.5.6 compared with 2.5.5. I'm seeing just 20FPS when in or around airfields in 2.5.6 compared to min 40FPS in 2.5.5 for some reason with exactly the same relatively high settings. (No I don't want to reduce them as all's good in 2.5.5) Strange thing is my system resources don't appear to be stretched at only 50-70% accross all and in both versions of the sim. On a positive note, out in the desert away from airfields it's running ok Test mission is 4YA Nevada capture bases, but with convoys removed. EDIT: Some strange things going on with shadows at low sun too where they appear and dissapear with head movement plus seeing some 180 degrees in wrong direction.

I found you can use device manager.. There is a "roll back to previous version" button under the properties /driver tab of the Nvidia display adapter.

I rolled back to 26.21.14.4219. I'd updated to 26.21.14.4587 earlier this week, but had no idea it had broken the F/A 18's middle MFD SA page for some crazy reason.

Many thanks for that...you were spot on :thumbup: I have no idea how a graphics driver could decide what MFD to dislike, but back to normal with a roll back.

After the last 2.5.6 patch this week, when I turn on the SA page in the F/A-18's centre MFD the FPS drops from 90ish to 20. If I turn the SA page off I'm back to 90FPS. The SA page works ok on left and right MFD, just the centre one now causes massive FPS drops. Strange thing is the same is now true when running 2.5.5 when I know it was fine before the last patch for 2.5.6. Can the update have modified a config setting or something common to both installs which are running on separate drives?