Magnum Posted April 15, 2021 Posted April 15, 2021 (edited) Surely I can't be the only one seeing crashes like "C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;". Crash logs: dcs.log-20210411-153600 - This was before the 2.7 update dcs.log-20210415-024639 - This was after the 2.7 update. Oddly there is a lot of garbled text in the .crash file and I also had to remove the .trk file as it was too large to upload here. I've tried windows updates, dcs repairs, complete re-installs. Not sure if websymbols is something my OS is just missing and the MS documentation is quite vague on how to ensure its installed. 2.7 has it's own issues, but hopefully my logs can show this was existing before and after dcs.log-20210411-153600.zip dcs.log-20210415-024639.zip Edited April 15, 2021 by chevelle970
Toumal Posted April 17, 2021 Posted April 17, 2021 I get these weird crashes too. Very annoying. dcs.log-20210417-111900.zip
Magnum Posted May 5, 2021 Author Posted May 5, 2021 dcs.log-20210428-211953.zip dcs.log-20210429-174635.zip dcs.log-20210429-204204.zip dcs.log-20210501-154200.zip dcs.log-20210501-221221.zip dcs.log-20210502-091743.zip dcs.log-20210503-041455.zip dcs.log-20210503-203918.zip dcs.log-20210504-055232.zip dcs.log-20210505-004049.zip dcs.log-20210505-030205.zip
Magnum Posted May 9, 2021 Author Posted May 9, 2021 Haven't changed a thing and issue still occurs on 2.7.0.5659 dcs.log-20210509-130514.zip
Magnum Posted May 10, 2021 Author Posted May 10, 2021 (edited) I've added debug via autoexec.cfg, hope this helps... dcs.log-20210510-145520.zip Edited May 10, 2021 by chevelle970
Magnum Posted May 10, 2021 Author Posted May 10, 2021 Fairly fresh install of Windows and the dedicated server(within the last few weeks). All drivers are up to date and I am running tacview 1.8.6 but will try updating to 1.8.7 Beta1.
Magnum Posted May 10, 2021 Author Posted May 10, 2021 And the latest one. I noticed this time however that event viewer mentioned Flight.dll... dcs.log-20210510-184507.zip
Magnum Posted May 12, 2021 Author Posted May 12, 2021 Most of my crash logs seem to point to "wAirdrome::createLandingTaxiRoute". I've no idea what this points to but I have a feeling it's to do with AI somehow interacting with the airdomes on The Channel terrain. I also noticed within one of the last updates that airdome frequencies changed slightly on The Channel yet I did not see much mentioned within the patch notes about this. I suspect other changes have been made recently. I've started running two versions of my mission for side-by-side testing, with and without AI to verify as this does not seem to be an issue with the scripting that's being used.
Recommended Posts