born2beflyin

I just ran DCS with FaceTrackNoIR instead with no issues ending and restarting missions. I swapped the PS3 Eye for the C110 since the latest PS3 driver I have installed per OpenTrack (libusb-win32 driver via Zadig) isn't recognized by FaceTrackNoIR. I guess I'll resort to the CL Eye driver and FaceTrackNoIR. I consider this issue closed as not a DCS issue. Thanks for looking into it and trying to help.

I know about this, and done. I didn't have an NV_Cache folder. Brand new memory, ran WMD, and no errors. Older mainboard and DDR3 memory. No XMP. I tried a Logitech Webcam C110, disconnected the PS3 Eye, and used OpenTrack with both the proxy DLLs and the real TrackIR DLLs to no avail. DCS still CTD just after loading the second mission. Files attached (no .dmp was output with 013516). Is there a way to attach a debugger to DCS to stop at the exception and view the call stack? When I try with VS 2019, DCS ends immediately presumably due to protection from attaching a debugger. dcs.log dcs.20220406-013516.crash DCS-SimpleRadioStandalone.log dcs.20220406-012952.crash dcs.20220406-012952.dmp DxDiag.txt

I've had this problem for a while intermittently, but now it seems very consistent with the latest release. When I initially load and run DCS with OpenTrack 2022.1.1, everything is fine. When I end a mission and load a new one without exiting DCS, I get a CTD just after the second mission starts (no crash reporter, just straight to the desktop). I was hoping the problem would be in OpenTrack's proxy DLLs for NPClient.dll and NPClient64.dll. However, if I replace the NPClient.dll and NPClient64.dll files from OpenTrack with the real ones from TrackIR 5.4.0, I get the same error. If I run DCS without OpenTrack, there are no problems. I can run a mission, end it, run another mission, end it, and keep going ... no problems. I'm not sure if this is an error in the NPClient DLLs or how DCS calls the NPClient DLLs, but it's definitely related to using TrackIR / OpenTrack. I'm also using a PS3 Eye with the libusb-win32 driver installed via Zadig 2.7. I don't have a good way to tell whether that's a factor. The only mod installed is SRS, but I was running a single-player mission (the Hornet 1989: Close Air Support mission) while testing this so SRS wasn't active, though I imagine the DLL loaded. The errors in the log and dxdiag often point to zlib or some nVidia driver file, but I feel like that's just an after effect and that somewhere earlier in the stack is the real error. dcs.20220405-072128.dmp dcs.log dcs.20220405-072128.crash DCS-SimpleRadioStandalone.log DxDiag.txt