MiG crashing to desktop in 1.2.12 final.

[Art-J]

Allright, after months of flawless fun with MiG since its release, I guess time had to come for me to hit the wall of problems :D. The story of my MiG flights today:

 

1) Installed 1.2.12 update for "regular" DCS copy today (never messed with beta version);

2) First try to fly the MiG - CTD :huh: It happened exactly in the middle of second loading bar (the one after "loading ground textures" etc.);

3) Repaired the DCS, because I thought Mustang's shaders mod I use might cause a mismatch. Clicked/unclicked the custom pit livery option a couple of times, fired up the MiG, the plane works OK, did a couple of quick and instant missions to check published fixes; The only repeating issue I noticed was the fact that after hitting "fly" button, game always freezed for 6 seconds checking/loading something before I could look around and take control of the aircraft (nothing like that happened in previous version for sure);

4) Installed Mustang's shaders again, MiG loaded up perfectly, did a couple of test flights again with no problems whatsoever.

5) Decided to start fiddling with "cockpit language" and new "custom cockpit livery" options, because I've read that you can have Russian pit and English tooltips by certain combination of these;

6) Tried to load up the MiG - bam! - crash to desktop :(. Restored previous settings but that didn't help, MiG crashes now every time (again, exactly in the middle of the second loading bar).

 

CTDs are not "complete" - I get standard "DCS stopped responding" message and when I hit "cancel", the game gets back to to post-mission screen (displaying "could not make debriefing" or whatever...).

 

I have no idea what to do now. I don't think the problem is related to shaders mod, because the MiG worked fine with it for some time... before I decided to test the new cockpit feature, which, I'd hazard a guess, is a main suspect here.

 

Any suggestions? I can post some post crash logs If only someone tells me where to find them (never had such stability issues with DCS so far). Win7 here, no alternative MiG cockpit mods/textures installed, other DCS modules work perfectly.

[Flagrum]

I can post some post crash logs If only someone tells me where to find them

C:\Users\<username>\Saved Games\logs

 

Upload me.log, dcs.log and possibly related (timestamp of crash) *.crash files.

[Cobra847]

C:\Users\<username>\Saved Games\logs

 

Upload me.log, dcs.log and possibly related (timestamp of crash) *.crash files.

 

These will be very helpful.

 

Thanks!

[Art-J]

Here You go, Gentlemen. I included the first and the last crash report from yesterday. Quick glance does indeed reveal some errors, but I'm not qualified to judge these :D.

 

Forgot to mention I use GTX780, running on 13.441 drivers.

logs.zip

[Flagrum]

In which mission(s) is this happening?

[uboats]

Here You go, Gentlemen. I included the first and the last crash report from yesterday. Quick glance does indeed reveal some errors, but I'm not qualified to judge these :D.

 

Forgot to mention I use GTX780, running on 13.441 drivers.

 

what about deleting the options.lua (optional: input key folder for mig21) under saved games and then re-configuring dcs completely.

[Art-J]

Today I did further testing.

 

#Flagrum: probably any mission - I tried first instant and first tutorial one, then tried a couple of quick ones with any airbase/blue/red/payload combination I could imagine. Then tried a couple of cockpit language, custom cockpit livery, cockpit shadows, texture detail settings, edited hint_localizer.lua file by changing RU and EN parameters in fifth line - all for nothing, game crashed time after time.

 

#uboats: didn't delete options/lua, because by looking at it, there was nothing extraordinary in either my gfx or gameplay settings. Besides, all other modules work with this options.lua perfectly. Moved input folder from saved games to see what would happen, no positive result though, so I moved it back.

 

All and all, I decided to do the same thing as yesterday - repair DCS, then reinstall Mustang's shaders. As a result, MiG works OK... well, at least for now. Who knows when it's gonna go out on strike again ;). Just to be on the safe side, I think I won't even touch any cockpit settings again. With "English" language and "custom" box ticked (I've set them like that before repair, so I wouldn't have to fiddle with them later), I get Russian pit with Eng tooltips and this is pretty much what I wanted.

 

I'm still puzzled what the issue was/is and how to avoid it in the future. I would also like to know why after hitting the "fly" button, game freezes (including controllers and trackIR) for 6 seconds before objects and AI units pop up and I can do anything. Obviously this time period is hardware dependent - my DCS is installed on normal HD drive, so You SSD guys probably don't even notice anything like that. Nevertheless, it seems that during these 6 seconds, some script is working and doing errr... something, which was not done in previous version, and I'm not sure if it's doing it right.

 

I hope You can decipher something useful from my crash logs. Thanks for the feedback, I'm off for some flying :D.

[Dolphin887]

Art-J,

 

with the package you have installed you got broken clickabledata.lua file. Cockpit failed to load causing breakdown of MiGs DLLs. Proper Lua base files are essential to DLLs. Manual change or customization is not recommended. In your case, the very first line contained incorrect symbol.

 

This is what your log says.