ChariotOfFLAME

This is the official HP replacement: Go to https://partsurfer.hp.com/?searchtext=22j68aar the link may not work right, but partsurfer is what you need.

It may be due to some sort of USB management in windows. I highly suggest going to your USB devices menu and ensuring that all of your USB devices are not set to sleep when inactive.

You also may not need to upgrade: https://forums.mudspike.com/t/new-wmr-driver-reverb-g2-saved-on-windows-11/17333/5

Pimax QA strikes again… You likely have defective/improperly installed lenses and will need to work with Pimax to get a replacement unit. Check with their support first, but I bet this is what happened.

Yeah, check every driver, as well as the MOBO bios to make sure everything is up-to-date, and murder any and all bloatware

I also recommend increasing your resolution to 1.5x in either Oculus Tray Tool or Diagnostic tool. If you want even more Rez where you look, QuadViews with an increased center resolution can help too

I think getting used to the VR quirks with the Q2 is good advice, then switch up to Q3 when you feel like you’re in the groove

Ensure in your device manager settings you have set all USB devices to never sleep or power save.

Standard disclaimer that tracks from previous DCS versions may not operate as expected, or at all

This was may be due to the recent CPU issues in the previous patch. Try the hotfix from today and see if that helps!

But any X3D will do

My brother (@Brother_Leb) and I repeatedly fly a very lite mission on a self-hosted server with no mods and only 2 jets and like 5 static objects. Recently we both are receiving the following error when trying to load Replays of our flights: Here is the Track file: server-20250520-204029.trk Here is the crash log: dcs.log Here is the miz file: Paphos_Airshow_FILMING_v5.miz Here is a related issue, but I believe they may be different: https://forum.dcs.world/topic/343255-dcs-crash-when-loading-replays/#comment-5380922 Does anyone know why this could be happening? I flew a solo flight (on a multiplayer server I hosted with the same details as the logged flight) the other day, and I can replay that flight just fine. Its only when my brother flies with me that the issue occurs.

Well, just in case, I’ve stopped all updates to Meta Desktop and the Q3 until I hear from y’all theyve got this fixed

If the OVR service is the issue, does making Oculus the default OpenXR runtime make a difference? Or does Meta Desktop run in OVR?

@Qcumber you may have already posted this, but do you have a settings table with avg % impact of each setting higher than lowest? I feel like you’ve got enough data to do that at this point? I also understand how much work creating that can be