PatMcKrotch

I was in a strike eagle yesterday on 4YA Syria, I had dropped a GBU 54 on a leopard and that's when I noticed the lines appeared. However in all fairness, I did miss with one GBU38 and had it impact the ground. Could it be the leopard? Or hitting the ground itself? I'll try again later tonight.

I'm hoping my log and video can help this problem. I was on 4YA Syria today, in a Tomcat. All was good, I'd seen no lines, then it just appeared. I think someone in a Kiowa may have shot something first on the ground first, not sure. There was also an F-15C and an F-18C loaded with laser guided GBUs. I was using TrackIR at the time, graphics settings were set all up to full. Hope this helps guys. dcs.log

Nevermind, Happened in desktop mode too. Right after I switched from the F10 Map, which is what I've been doing when it crashes in VR. dcs.log

Aaaaannnnd Crashing again. FML DDU no longer helping Verified No OC on the GPU Tried via virtual desktop and SteamVR What's different, NEW DCS Update New GPU Driver dcs.log DxDiag.txt

I finally got some time off work to play around with this. Driver uninstalled with DDU, driver reinstalled (however NVidia did release a new Driver) Updated the bios Installed MSI afterburner, confirmed no GPU overclock Anyway, thank you and the steps above worked. dcs.log

I had some time today to try out the fixes. I uninstalled Gamefirst (Asus program to boost system resources to games) Uninstalled AI Suite 3 (GPU was running on Smart mode in this program) Used the NVIDIA App to "Automatically tune" the GPU removed the chipset driver that ASUS installed via armory crate and installed the one from the AMD website support page. Shut down all non essential start up programs. Ran a repair on DCS, deleted all excess files. Along the way I tried running the game with similar crashes, but the repair run seemed to do the trick. The game ran for quite some time, there were a few stutters in game. I couldn't keep up in a dog fight in my tomcat vs a Viggen as the lag was making it appear to jump all over the place. The game did end up crashing when I switched to external view after being in the F10 map. I find if I switch views and go into the map too much, the game lags a bit more. It's definitely a step in the right direction and I appreciate the help. Ironically the computer is drawing less power and is a lot quieter without all that ASUS crap running it proving to me, that it's really doesn't help. DxDiag.txt dcs.log

Hello, I'm using a quest 3 via steamVR wireless link. The game loads fine in multiplayer and after a few minutes, the game freezes, my PC fans spool down, PC freezes and when it comes back I get the bug reporting tool popping up. This started after the last update as it was fine before. PC Specs 9800X3d X870E Asus Hero 96 GB DDR5 DDR5 8000 (PC5 64000) 2TB NVME Seagate Firecuda Asus 4090 Running AI overclock via armoury Crate Discord OBS (streaming Software) SRS USB wattage watcher (ASUS) Lian Li L Connect 3 (For CPU Fan Control Left on Full SP for DCS, other fans spool down, not these) Simapp pro And google chrome for music and streaming to youtube. It happened while I was live streaming and when I wasn't, I'm also listening to music on a web browser as well. DxDiag.txt dcs.log

On mine, I'm using steamVR as I find that Meta just crashes out of the gate. Virtual desktop works, but no hand tracking. The game runs fine for awhile, then my PC fans spool down and the system freezes. I just got the Quest 3 working, then it this started happening. FML DxDiag.txt dcs.log

I tried virtual desktop, but it rendered my keyboard unusable. SteamVR not only allows me to use keyboard, but there's a livestreaming app (LIV) that allows me to see comments from youtube, twitch or wherever I stream.

01441.650 ERROR: Can't move C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/F-4E/bin/HeatblurJester.dll to C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods/aircraft/F-4E/bin/HeatblurJester.dll: (225) Operation did not complete successfully because the file contains a virus or potentially unwanted software. 01441.657 STATUS: Can't move C:\Program Files\Eagle Dynamics\DCS World OpenBeta\_downloads\Mods/aircraft/F-4E/bin/HeatblurJester.dll to C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods/aircraft/F-4E/bin/HeatblurJester.dll: (225) Operation did not complete successfully because the file contains a virus or potentially unwanted software. 01466.302 === Log closed. Huh...set off my antivirus...

Fixed Sorry I haven't replied sooner, work has been insane lately. My Cable was rated for Max 3.0 GB/S, I was at 3.2 so I scaled it down to 2.7. Second, I stopped using the META PC Link app all together and got Virtual Desktop Streamer. My PC did freeze for a moment, all fans spooled down, but it came back after a couple of minutes and I didn't have an issue again. As for the META PC app? I give up on it, Virtual Desktop Streamer is the way to go with this. Hope this helps someone else.

I'm using an aftermarket cable from amazon. I'll pick up the official cable once payday comes and see if that helps. Cable Used: Syntech Link Cable Compatible with Meta/Oculus Quest 3S/Quest 3/Quest2/Pro/Pico 4/Ultra and PC/SteamVR, 16FT Upgraded Type C Cable with USB 3.0 Adapter, High Speed Data Transfer Cord for VR Headset

Today I learned how to access Oculus logs, unfortunately I still don't know how to read it. I've been a bit busy lately and I haven't really had time to mess around with this. However I came across an OpenXR log and thought, maybe there's an Oculus one? I loaded up DCS with the oculus. At 0110, the game froze again and unfroze at 0116. Oculus Client Log [DCS.exe (26712)] 04/10 01:09:54.462 {WARNING} [OXR] OXRSessionData::WaitFrame adjusting predictedDisplayTime from 352568843942 to 352568845626 [DCS.exe (26712)] 04/10 01:09:57.477 {WARNING} [OXR] OXRSessionData::WaitFrame adjusting predictedDisplayTime from 355610342623 to 355610346883 [DCS.exe (26712)] 04/10 01:10:18.344 {WARNING} [OXR] OXRSessionData::WaitFrame adjusting predictedDisplayTime from 376455678176 to 376455680067 [OculusDash.exe (28588)] 04/10 01:10:22.331 {DEBUG} [Client] HMDInfo Changed [DCS.exe (26712)] 04/10 01:10:22.331 {DEBUG} [Client] HMDInfo Changed [oculus-platform-runtime.exe (7084)] 04/10 01:10:22.331 {DEBUG} [Client] HMDInfo Changed [DCS.exe (26712)] 04/10 01:16:05.930 {WARNING} [Tracking:Filter] Prediction interval too high: 288.686361 s, clamping at 0.250000 s [DCS.exe (26712)] 04/10 01:16:05.998 {DEBUG} [OXR] SetSessionState from XR_SESSION_STATE_FOCUSED to XR_SESSION_STATE_VISIBLE HMDInfo Changed? Anyway, that's all I got for now until I figure out what this means, or think of something new. Oculus_Logs_DESKTOP-NUITSK2_20241004_013112.zip dcs.log DxDiag.txt

My wifi router isn't good enough (Yet) for a wireless connection. I do have virtual desktop, but I'm using a cabled connection with the Q3. Based on this site, there might be a conflict between Oculus software and Openxr. I have some more reading to do on this. https://communityforums.atmeta.com/t5/OpenXR-Development/Quest-3-v-68-conflict-with-Open-XR-Toolkit/td-p/1223282

nullDialed all graphics down to the lowest setting, same issue. Total system freeze for about 5 mins. It doesn't seem like graphics settings are the issue here.nullnullnullnull DxDiag.txt dcs.log.old

nullFirst time I've ever seen this page. I set it to the recommended size. I'll have to try DCS on low settings later on today and see what happens. null

Perhaps the headset itself is thermal throttling? I'd like to find a way to test that.

I tried the outlined process today, and I had a total system freeze within 5 mins into a game. The freeze lasted for 6 minutes at which point I was kicked off the server for a timeout. The quest 3 had discharged from 100% to 93% before I shut it down. I'm also getting a notification from the Meta Quest Link app Before, I was hitting the reset button and now that I know I can wait a few minutes, this should allow me to collect better data. I also downloaded quick CPU, but it'll take me some time to figure out how to use it. After running the repair on DCS, I turned on "Allow ED to collect anonymous Data". Hopefully that will help as well. Last but not least, I bumped up the graphics settings a little bit in VR. nullnullnull DxDiag.txt dcs.log

Just ran again to collect Data, I haven't Tried your procedure yet Maddaawg. I'm hoping that'll work tomorrow when I have the day off work. The only thing different about today is, I let the game run in a frozen state and didn't shut it down. It was frozen for about 5 minutes, then I got a "Connection timed out" showing that I was kicked out of the server. I tried connecting to 4YA Syria again and it froze again once I had picked the apache at Allepo. Also, my keyboard has lost power twice just typing this out so I'm looking at my power plan. nullnullnullnull dcs.log DxDiag.txt

Tried again today, Again, connected via direct PC link (Cable). The game froze again once the batter reached 90 percent. I disconnected the cable after DCS Froze and shut down the headset, so running a DXDiag would have been useless. I'll try again later I wanted to try today because the META Quest Link App recently updated along with its' drivers. I was also running core temp at the time, my CPU never went above 68 C, so I can rule out thermal throttling. I'm going to recharge this and try it again later today as I noticed that wifi is on an auto connect through Oculus. I'll try switching that off and see if it affects anything. dcs.log

Sorry for the late reply, works been busy lately. I added the Force Enable oculus because DCS uses OPen XR by default and I'm trying to narrow down reasons why it it's freezing. I ran it just a few moments ago with the Force Enable oculus (Loaded and froze immediately) Then I ran it with OpenXR. I got to a server selection page, began loading, then froze when I got a "Allow SRS to Load" notification.

I lucked out a bit today, The game froze, but I was able to Run DXDIAG while the game was frozen. Headset was at an 84% charge when I started. Maybe this has something to do with Oculus' charging system while it's plugged into the PC? But it's not affecting other VR games. I had also used "--force_enable_VR --force_oculus_VR" in the command line. dcs.log DxDiag.txt

@Phantom711 Didn't help. I'm leaning towards a disconnect of some kind. When my G2 disconnected, the game froze as well as DCS doesn't have an in game toggle between VR and desktop mode. However my USB ports aren't on any power saving plan and I'm using a USB hub for everything but the keyboard, mouse and headset. Or maybe it just doesn't play well with Metas software. Either way, I've got myself a mystery and I really want to figure this out. Would you know of any tools that can log what's going on behind the scenes in the game? I'd like to run something like that at the same time. Thanks.

Tried the Q3 again this morning, with limited success. I'm using a direct PC link (Cable) via the Meta Quest Link App. The game was running fine for about 10 minutes then my PC froze. I was unable to run DXDIAG at the time, but I did run it after restart. I was also running SRS and playing music via web browser (Google Chrome). I'm looking to pick up a new Router so I can run the headset wirelessly as people are suggesting it runs better on wireless than a direct cable link. dcs.log DxDiag.txt

I experienced a Desync not too long ago. I was on 4YA Syria and the Desync was pretty bad. I didn't figure out what was going on until about 3:40 in the video. It seems to be something with Syria. The video is unlisted but is accessible. I tried that same server last night and there were still desync issues, but not as bad as watching missiles fly backwards from an F-15.