[̲̅D][̲̅A][̲̅T][̲̅A]

Trying out MP, set the autopilot to hold alt while I watch the missle do it's thing. The Missile is in a dive because it missed, come back and my plane is also in a dive and starting to correct itself just as I have come back to the regular F1 view. The controls of the aircraft seem to mimic the missile while in the F6 camera view. Anyone else experience this in the F14?

it's crashed twice on the P47D instant action free flight. but the clouds look cool.

What worked for me was bringing down my Vram usage, via lowering my resolution down by a lot and using super sampling from my oculus to bring the image quality back up, also lowering textures and draw distances. Once you get it to run stable at ultra low settings, you can turn things up one by one to see where your limit is.

I was struggling with this too. What fixed it mostly for me was to drop the settings down to the preset VR settings option, and lower my screen resolution. The reduction in VRAM requested helped out a lot. If the lower resolution settings is too much increase your pixel density to just before it becomes unstable again. Good luck!

What worked for me to make VR more stable was to lower the VRAM requirement on the hardware. By turning down the textures and resolution to something more manageable and bumping up the pixel density a couple of notches, VR stopped crashing as much as it was. This was AFTER I bought a new oculus link cable, deleted the steam version of dcs and downloaded stand alone, and completely overhauled my whole setup trying to chase down where the crash was coming from. My best guess based on results was just asking less of my hardware.

I'd also like to add my two cents. Oculus Quest running Oculus Link on a EVGA RTX 2070 XC Ultra (happens in OC and default settings) I will be playing in SP and MP, the screen goes black while DCS continues running in the background. Only happens in DCS, all my other VR games behave with oculus link. The F14B causes the crash to happen as soon as I load into the plane, 14A has some stability. Other planes like the F86 happen eventually. The oculus app will say that it was unable to see find my headset when the crash happens. I have gone as far as uninstalling DCS from steam and re downloaded the stand alone version to negate steam from the equation. I have no unofficial mods installed. It started with the VR stuttering and I had to tap the headset to put it into the passthrough camera mode to get it to stop doing that. Now it just crashes to the oculus home screen and i have to reconnect oculus link to hopefully get back into DCS. Process D:\Oculus\Support\oculus-runtime\OVRServer_x64.exe (process ID:9064) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} This is the event that comes up every time that DCS crashes oculus back to the home screen.

Update: Downloaded and installed the standalone version of DCS. Still crashes oculus link back to home screen. Also unplugged the USB hub that I had installed thinking that there was a USB power issue that was causing the problem. Did not fix anything. Also in more investigating, crashes happen with every module, not just the F14. The F14 just crashes the program faster.

Update again, reinstalling the F14 did not work. Tried other aircraft, other aircraft causes oculus to stop running. DCS is the problem. Played Blade and Sorcery for an hour without issue. F14 just causes the crash to happen faster. That's where I am at with this problem so far. Faulting application name: OculusDash.exe, version: 0.0.0.0, time stamp: 0x4b6e1b38 Faulting module name: OculusDash.exe, version: 0.0.0.0, time stamp: 0x4b6e1b38 Exception code: 0xc0000005 Fault offset: 0x0000000000427156 Faulting process id: 0x514 Faulting application start time: 0x01d71106caf04c36 Faulting application path: D:\Oculus\Support\oculus-dash\dash\bin\OculusDash.exe Faulting module path: D:\Oculus\Support\oculus-dash\dash\bin\OculusDash.exe Report Id: 2a73be1e-a942-4298-a666-0488ae421dbd Faulting package full name: Faulting package-relative application ID: Fault bucket 1353361737694256787, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: OculusDash.exe P2: 0.0.0.0 P3: 4b6e1b38 P4: OculusDash.exe P5: 0.0.0.0 P6: 4b6e1b38 P7: c0000005 P8: 0000000000427156 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAF91.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB33B.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB34C.tmp.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB359.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB36A.tmp.txt These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_OculusDash.exe_481bee853faf373699d44364c4943e7054b0bf6f_4b71f3e5_5e4b2b54-3719-414a-8e08-516959a308d6 Analysis symbol: Rechecking for solution: 0 Report Id: 2a73be1e-a942-4298-a666-0488ae421dbd Report Status: 268435456 Hashed bucket: 849e9991b1ae686db2c81b547bdf1e93 Cab Guid: 0

Update: Reinstalled oculus software and it completely broke my system. Had to uninstall Oculus and install back onto another drive. F14 still doesn't work. Going to have to delete the module and reinstall to see if that fixes the problem. Will update again.

Thank you Paul for the reply. I am indeed using v25, and after my tooling around trying to fix the issue. I've successfully made the whole oculus link program unuseable. Updating to v26 and trying again. Thank you again for your reply and letting me know that it's a Oculus problem and not a me problem.

At first I thought that the oculus link cable was the problem, so I threw $85 down for a new Oculus Link cable. Not the issue. DCS will stay running while the Quest boots me back to the home screen. I then have to pause the game and restart oculus link from the Oculus home screen . Sometimes I will be able to start back where I was, other times I will just be looking at a black screen in the headset while tracking resumes on the PC monitor and I have to just exit the DCS program from there. This ONLY happens on the F14 and I am out of ideas. I can not find any errors in the logs. HELP dcs.log