Sr.

I reported this same behavior/"fix" for weeks after 2.9 released... Still no resolution. Repeatable in VR headset too. Simply by touching the input sensor located between the lenses. The issue persists to this day. good luck For everyone... at the same time, for one particular application only? And only immediately following their switch to MT with v2.9? Unlikely

Nope TBH, I can't even get it to run in 2D mode. But I haven't really tried very hard.

I would like to get on the list please for one of the less complex UH-1 type pictured far right. Shipped to Texas?

Same. I must have missed something because, I ran before and afters and they aren't as far apart as what's shown in the video. 5000msreport.txt 15msreport.txt

If you're running the OpenXR Tool kit Companion App, try disabling or runnig it in safe mode. Mine recently started doing the 5 sec freeze. I was testing something else and switched off turbo mode, problems for me started after I switched it back on. After realizing the stutters went away in disabled mode, I uninstalled then reinstalled OXRTK and it's fine again.

Not yet... once I get my OXRTK issue resolved I plan to take a closer look.

Seriously though... I can no longer get DCS to run using OXRTK. Menu loads, then it's a constant freeze fest inside the HMD, Until it ultimately crashes.

Same. My best example: I use the VR cursor and 2 modifier mapped buttons on my stick for mouse control. Once I center the cursor, I just enable it, look at what I want to click. Without the anti shake, it's more difficult to pinpoint buttons I want to press, and I've noticed it more difficult to target the IHADSS gun cursor in the Apache without it.

Man! Don't ever disable turbo mode for testing something. It's almost impossible to re-enable. Now it causes DCS to crash mostly and if it launches at all, there's a never ending lengthy freeze frame effect. For now, I am only using the "anti shake" feature with OXRTK.

Problem seems to have fixed itself. I unchecked the box under settings (gameplay or other) that synchs in game controls to HOTAS etc While I could see the in cockpit adjustment knobs rotate while operating the mapped HOTAS knobs, I guess the brightness was stuck outside a range my control knob wasn't reaching.

It's been a while since I messed with the Apache. Just reinstalled the module, after a slow repair install. I can flip the monocle back n forth, but can't see any symbology. I have it's brightness etc set to same knob as all other aircraft HMCS, and those are fine.

Oh wow... didn't even realize that was on. Thanks for the heads up.

gracias

Do you have a link to the latest? Mine doesn't seem to be working.

Thanks man. DO you know if your haze fix is currently working after the 2.9 patch?

I've not had these freeze or jittering in mission or at the menu screens. My issue has only ever been having to brute force my way passed the mission loading... once that happened, it was (and still is) smooth flying.

My system HT enabled, cores unparked, all enabled. Current n vidia drivers.

WOW! WOW WOW! I honestly don't care if anything else was fixed... but I am thrilled to no longer have to sit with my headset on my face taking micro-naps waiting 2-3 minutes for a mission to load, and praying it doesn't CTD. Whoever fixed that, has my nomination for ED employee of the month. Posted elswhere: I'm happy to report the freezing after selecting a flight (which before for could take MINUTES) has been fixed... for me. I just did a few test: And the first airframe/terrain load took a little bit (expected). Was like I recall in days passed if you cleared shaders, you'd have to let them rebuild for each aircraft and terrain. Once that was done, I can now start a flight in seconds, quit, choose another click Ok, and it's actually single digit seconds when the cockpit/briefing screen appears. Switch to another aircraft... same initial wait like first shader like, then quit/switched a few different missions... seconds. Even after switching BACK to another aircraft/terrain... seconds to the briefing screen/cockpit. SSS weirdness is fixed... though I still see little use for it. The smearing (F3 flyby) is still there but, that may just be a product of DLSS. Is it just me or, did they add cockpit shudder when firing cannon? Noticed it in F-16 and A-10II C.

I'm happy to report the freezing after selecting a flight (which before for could take MINUTES) has been fixed... for me. I just did a few test: And the first airframe/terrain load took a little bit (expected). Was like I recall in days passed if you cleared shaders, you'd have to let them rebuild for each aircraft and terrain. Once that was done, I can now start a flight in seconds, quit, choose another click Ok, and it's actually single digit seconds when the cockpit/briefing screen appears. Switch to another aircraft... same initial wait like first shader like, then quit/switched a few different missions... seconds. Even after switching BACK to another aircraft/terrain... seconds to the briefing screen/cockpit. SSS weirdness is fixed... though I still see little use for it. The smearing (F3 flyby) is still there but, that may just be a product of DLSS. Is it just me or, did they add cockpit shudder when firing cannon? Noticed it in F-16 and A-10II C

Honestly, this all seems like a lot of unnecessary system configuration for an issue that clearly wasn't present until OB DCS 2.8.6.41363. Not only does it not work for everyone, but is something that should have been identified and possibly reversed by now. Has anyone even properly identified what was "added", removed or possibly broken with the OB DCS 2.8.6.41363 release?

I get the same. 5800X3D Win11

Thanks I'll try anything once. Well, I'm happy to report that after using CPU Unpark, I can successful launch DCS MT again. Even switching between airframes. this while remoting to my home PC and running non VR version. Will check VR side this evening. I have used the previous version of Quick CPU in the past to create what was my power plan. This new version is the ticket. Mucho Thanks!

Interestingly enough, even though mine under the current power plan both set to 100% and after having done the registry edit last night and rebooted... I still have cores parked. wtf null

Mine is and always has been set to Ultimate since I installed the 5800x3D null