tn_prvteye Posted September 18, 2018 Share Posted September 18, 2018 I don't have a log to post right now, but I was just seeing if anyone's seen this with the latest OB hot-fix. Can't pin down any rhyme or reason for it. Usually happens within 5 minutes of a mission start. Running a few mods...the USN Deck mod and the Shaders mod (I'm guessing this is the culprit). Just wanted to know if anyone else is having the same problem, or if I've screwed something up (highly likely). I'll test with with the Shaders mod disabled when I get home from work. Link to comment Share on other sites More sharing options...
tn_prvteye Posted September 18, 2018 Author Share Posted September 18, 2018 Seems to be the Shader issue. Disregard. Link to comment Share on other sites More sharing options...
tn_prvteye Posted September 18, 2018 Author Share Posted September 18, 2018 Okay, I disabled the shaders mod, repaired, and deleted the FXO and metashaders folders, and still getting a CTD. I attached what I could find on the crash.dcs.20180918-215111.zip Link to comment Share on other sites More sharing options...
MadDog-IC Posted September 18, 2018 Share Posted September 18, 2018 Okay, I disabled the shaders mod, repaired, and deleted the FXO and metashaders folders, and still getting a CTD. Can't give to many words of wisdom, but the following errors standout: Looks like you are running a Dynamically spawning mission script and it is producing several errors, so it might be incompatible now, Run a "DCS_Updater.exe Cleanup" command to check that you have actually removed all mods, try another mission that is similar if possible to see if you get the same results or not. Crash is happening within you graphic card drivers, so might not have installed correctly, try uninstalling and reinstalling or a different version. Best to have any antivirus software deactivated whilst doing this. 2018-09-18 21:42:55.972 ERROR SCRIPTING: MIST|doScheduledFunctions|1005: Error in scheduled function: [string "C:\Users\Steve\AppData\Local\Temp\DCS.openbeta\/~mis000036DA"]:1651: attempt to index local 'myGroup' (a nil value) 2018-09-18 21:43:09.093 ERROR SCRIPTING: MIST|doScheduledFunctions|1019: Error in scheduled function: $1[string "C:\Users\Steve\AppData\Local\Temp\DCS.openbeta\/~mis00000EBF"]:43: attempt to index global '_observer' (a nil value) 2018-09-18 21:43:13.079 INFO SCRIPTING: Dynamic AI group spawn script loaded. 2018-09-18 21:43:13.079 INFO SCRIPTING: Dynamic AI group spawn script running. 2018-09-18 21:51:11.289 INFO EDCORE: try to write dump information 2018-09-18 21:51:11.294 INFO EDCORE: # -------------- 20180918-215111 -------------- 2018-09-18 21:51:11.296 INFO EDCORE: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_adc520364db29861\nvwgf2umx.dll 2018-09-18 21:51:11.298 INFO EDCORE: # C0000005 ACCESS_VIOLATION at CC170D44 00:00000000 Regards, Ian. Asus p877v-pro, Intel I7 3770k 4.2ghz, 32gb Ripjaw X ram, Nvidia RTX-2070 Super, Samsung 32" TV, Saitek x52 pro Joystick and Combat rudder pedals, TrackIR 5, Win8.1 x64 with SSD and SSHD protected by (Avast AV). DCS Tech Support. Link to comment Share on other sites More sharing options...
tn_prvteye Posted September 19, 2018 Author Share Posted September 19, 2018 Well if the patch has killed my missions using this script, I might be done with DCS. There's no way I'm doing all that over again. However, usually with scripting errors it won't CTD...just give me the Pop-up Box error. For the graphics card driver, I'm running the latest Official releases...it's kinda hard to screw up installing those. I do a clean install every time I update. Maybe I'll try an earlier version. Thanks for the info. Link to comment Share on other sites More sharing options...
tn_prvteye Posted September 19, 2018 Author Share Posted September 19, 2018 It likes not all the files from the Shader Mod may have been removed. Which is odd since I use JSGME...and I removed it using that. I'll see if that was the problem. Link to comment Share on other sites More sharing options...
tn_prvteye Posted September 19, 2018 Author Share Posted September 19, 2018 (edited) Nope still got a CTD. Back to testing. Got a CTD from a "fast mission"...while the LOG report was generating, I got a BSOD with a Kernal Security Check Failure WIN10 error code. Looks like I'm in for a long night...<sigh>dcs.log-20180919-012419.zip Edited September 19, 2018 by tn_prvteye Link to comment Share on other sites More sharing options...
Recommended Posts