Maddaawg

That's true, but McAfee is garbage, and he mentioned using defender too.

All of DCS and Saved Games. Better yet, dump McAfee and running 2 antiviruses is a really bad idea. Make sure when start DCS, you have fully logged in - Top right wait for your username and language to finish loading. When you post a log file, you can upload the log file instead of copy and paste, it makes it easier to read.

That's probably the normal speed for Q2 on USB 3.1 What are your system specs and DCS settings. Did this just start or been doing it for a while? I've been having similar issues with Q3 and did switch to VD but then started happening on maps such as Syria and Afghanistan but not others. I saved my settings and then did a VR preset, worked much better. My system is just old and can't keep up. As I add more things back the issues start again.

Would this be a BT configuration of buttons something like PountCTRL? By up and down buttons you mean dial knobs like on the FA-18 altitude warning or dimmers? I could always use some dials on my HOTAS. What about the new one on the left hand and Slugmouse on the right, for dials. I'll be looking forward to seeing your progress.

I have a mod that does this for me, the Hanger in VR is headache inducing. So your probably missing some files, did you do a repair?

@Dangerzone which Reverb did you have? I have the G2+, and it has an insert that allows more room for Rx lens inserts. I never noticed my eye lashes hit them, but i did on the Q3 and bought an AMVR facial interface and it's further back than stock decreasing my FOV but keeping from hit the Rx inserts. I may get it back out and run a test on my non‐DCS system. There is a $5 tool that let's you do VR testing like FOV.

Measure your IPD to start with, there are apps for it or you can get it from where you got your glasses. Set your HMD at that and then go from there. Are you using DLSS? That can cause ghosting.

How do you feel the FOV is on the CL compared to the Reverb?

It's hard to say until the super is in the hands of reviewers and users. The CL seems to be getting good reviews but since it is missing any hand recognition I'm not interested until a solution like HTCC or PointCTRL can be used. I'm not yet convinced I will buy a Super either, which I did the $.99 cent deposit on, and would only do so if the new MR front plate was available and had hand recognition. Though my turn on the PointCTRL list is coming up around the same time the Super is available, so that may be an option if PC parts also become available to run the SC. I don't think it a question If DCS can provide enough visual details for the SC, but whether or not your PC can push those details that are available. The 50 ppd is going to be very demanding and I'm thinking a future system 5090 plus a 9800x3d will have trouble getting to high settings.

It's working but @mbucchia has this on his OXRTK page: So, while it works for many, some are having issues with it that use Quests depending on which update they have and in troubleshooting issues eliminating the extras that you don't need to run DCS are a good step. Reintroducing them once you have solved the issue. The statement I made is correct it is not needed, and development has stopped, it is an optional app.

I'm wondering if there is a need to modify the DCS.exe shortcut to not start OpenXR if SteamVR is the runtime? This is beyond my paygrade; I would put a post in the DCS VR Vive Discussion

I'm not familiar with the Vive and how it works. You can choose either SteamVR or OpenXR for the runtime? And if so, have you tried both of them? If you still have the additional command line settings in the dcs.exe shortcut, delete those since DCS runs OpenXR natively. If you're running SteamVR, that may require a different startup command. Nothing jumped out at me in your logs. You're running a program to park cores, like process lasso? There is a warning in the logs about possible stuttering because of some parking, but I am not thinking that would cause it to not start.

Did you try it without OpenXR Toolkit or other OXR apps?

The title of that is confusing, I'm not sure if they are having an Open XR problem or an Open XR Toolkit problem. The toolkit is an app to configure Open XR games and is not needed and is no longer supported by the dev. You probably can switch to OpenVR or SteamVR, even VD is VDXR, so there are options to try. I don't know the ins and outs of switching to the others except VDXR is selected in the VD streamer app with the other choice being SteamVR.

Did you run a solo mission or on a MP server? Do you have the ability to do as @Rushman suggested Also, I'm guessing you have run it with other games to be sure there is no HMD issue? Or even try WiFi with Meta Link?

I was looking at this and saying wow maybe that will be my next HMD and then fresnel lenses. They don't really advertise that because it's not a selling point and they know it.

Let windows set the page file. Adjust for best performance or minimal stuff like I have. Mine is optimized for gaming, not what Windows wants to wow me with. I think I followed a video from Jabbers, but not sure.

I've heard it makes an audible alarm sound, look at my edit above regarding your pagefile. Set your DCS to minimums and try a solo run of DCS. Is Windows set to automatically adjust the pagefile? I want to emphasize this part, your settings are all on high. The 4090 with a top tier CPU can't do all high settings, and you don't have a top tier CPU, so your CPU bound.

That last image with the warning of not finding the headset from Meta Link makes me think you're having a Quest problem, either software, cable or HMD. Have you played other games with it? Tested the cable in Meta Link? Tried a different cable? Though my headset would lockup too with a frozen image in the headset, I never saw that Meta disconnect warning. It could be that I didn't wait long enough. But I moved onto VD and it happened there too. Make sure your cable is testing good and better yet try another one just in case. You have everything on high, that might be an issue, especially on servers. Try it the other way around, everything on low. Mine would lockup constantly on a PD higher than 1.1. What's your PD setting in Meta Link? Also, In your DxDiag I see a huge page file size at 82GB. This kind of usage will severely degrade your system. Is your physical memory 128GB? If so that page file needs to be either at the minimum or have no page file. It's possible that your 4090 is too much for you CPU to process and frames are going to the pagefile.

I use QuickCPU to make sure my power plan is working for full performance as well as stopping the parking of cores. Depending on the CPU you have, this may be of help. This is especially helpful with newer Intel and the "E" cores.

I see two things in your log that are not in mine. First is Debug, yours has a lot of that I have none. Second, you end with "ERROR VISUALIZER (Main): OpenXR xrWaitFrame failed with error: XR_ERROR_SESSION_LOST". I don't know if this is a result of another issue causing the OpenXR fail or that is showing an OpenXR issue. I'm hoping the procedure I have done fixed this issue as I have not seen it since I did this. 1. Make a backup of saved games/dcs folder 2. Delete the saved games/dcs folder 3. Run DCS in 2D to let it recreate the folder 4. Move back to the saved games/dce folder a. Saved Games\DCS\MissionEditor\logbook.lua b. Saved Games\DCS\config\input\*any aircraft keyboard and control bindings you want* 5. Run DCS full repair 6. Test in VR

In ME or in game? I don't think it is supposed to be there in the ME. Are you using the original or the updated version from @Draken35 Draken35 version of SP

So, ditch the accessory items like OXRTK turbo and OTT. Set the in game PD to 1.0 and Meta software to 1.3 at 72HZ which is then max resolution with the slider all the way to the right. Set the DCS preset of VR and test. These are kind of the minimum settings and then work your way up from there. Trying first with settings in game and not OTT or OXRTK as many have issues with Turbo Mode and OTT PD settings, some its fine and everyone's PC and tolerances for VR are different. Next if that works start with 2x MSAA and adding more details like cockpit res. Once you get the basics going and not stuttering, then QuadViews with your CPU should help. Even though the Q3 doesn't have tracking, it will still work in fixed foliated. For me I could not get it to work well but my CPU is older gen. You may not need this at all with a 4090, but if you want to run MSAA 4x and higher graphic settings like clutter/grass, forest and LOD, you may need it. The Res of 1920x1080 is the mirror image on your PC while in VR, so change that to the minimum. What does your cable test at in the Meta software? It should be about 1.4Gbs. I ditched Meta for similar issues and use VD, but that does also require a solid WiFi connection. Mine is a dedicated WiFi 6e and VD works much better for me.

I use Process Lasso and prioritize DCS to other cores and those are for the other system apps and processes. For the upgrade either the new 9000x3d's when they come out if they test better than the first Zen 5's, otherwise I will go with 7800x3d, and MB, and RAM will be what is a best match. I do want to add more M.2's than my current 2 and the new MB's coming out look like they have better options for them. I have always used ASUS and the current YT's are busy jumping on the hate bandwagon against them so, I haven't decided yet. I will be jumping to 128GB though, not yet needed but its easier to a match set of 4 than to add 2 later if needed. For GPU, it will be either a 4090 or 5080 or 5090. All depends on announcements and needs. Looking at a Pimax Super and it may need a Super computer to go with it.

So, I really don't like the idea of a wipe becasue I am shopping soon for upgrades and that will include MB, CPU, RAM, and more M.2 drives and then a GPU and VR headset after that. Last night, I renamed my Saved Games/DCS folder and restarted DCS forcing it to recreate the folder. Then I copied over only my controller info and the settings file. Then I did a full repair and extra file removal. Followed by a shader's cleanup. Today, I removed my one mod (VR Loading Screen Fix) and removed all OXR apps such as Necksafer, HTCC, and OpenKneeboard. Then I removed the DCS mod for WWII so I can have others look at the track if needed that don't have that mod. I recreated the Syria map mission with a Super Carrier group and some static targets. I have done 2 missions so far without any issues. After the 1st mission, I added back in the Necksafer and HTCC. The only issue was a slight microstutter on the carrier as I moved out from parking initially. I used F10 constantly as will as multiple views constantly and going back in and out of F10 without a problem. Next mission I will take off from a base to see if it still works well over land as the current mission was just over the ocean with land in sight but not flying over it. Maybe something was corrupt in the Saved Games. Here is the log just incase you want to see if there are any changes you notice. dcs.log