Jump to content

5-String

Members
  • Posts

    2
  • Joined

  • Last visited

  1. Thanks for taking a look at this. While I did find a missing space in my command line between VR and the --switch for force_openxr, editing the space in did not make any difference. It crashed at the same point again, generates an identical logfile pretty much every time. Same faulting module (GraphicsCore.dll), same access violation code, etc. When I launch from within VR using Oculus Quest 2 K launch DCS.exe shortcut from desktop. I see the DCS Login progress bar, then NVIDIA splash, then 15 years of DCS. Then desktop goes away and I'm in white VR grid environment with DCS World Steam Edition Loading... hangs there. I remove Oculus headset to see crash message on monitor screen: This time I elected to gather addl debug info using dxdiag and I sent crash report, though I'm not sure it actually did anything. I might've seen a line saying something was full or not available or something to that effect. Looking at your command line, it appears you have your DCS installed outside of steam, whereas my executable path goes through steam. I'd have to uninstall/reinstall to configure my install that way, am I right? That only feels like a workaround, but it may be worth it if this issue takes a while to get sorted. Since other apps not using Steam VR work fine, I may consider this.
  2. First crash occurred after system start, upon loading of a mission. Hung at Sim Start. After reboot crash settled into same time during application launch, about eight seconds after double click. DCS shows crash dialog box with button options to send crash info, view in Explorer, etc. Application Event log logs ID 1000 every time. Faulting module is GraphicsCore.dll every time. Logs ACCESS VIOLATION 0x000005 every time. DCS without VR runs fine. Other VR apps not using Steam VR also run fine. Anyone see this? dcs.log
×
×
  • Create New...