Desolcm

Sorry for not being more clear. I was referring to the two lines in the missionscripting.lua file. When commented out, I get crashes. If I put them back to default then it works, but no state is saved between sessions. --sanitizeModule('io') --sanitizeModule('lfs') I thought this would be an easy repro but it seems not. I'll try some of your suggestions and see if I can narrow things down any better.

I did some more test scenarios. I verified if I set persistence back to defaults, no crash. Once I commented out the two lines, crash occurred. I went into triggers and blanked out the script "income". No dialog, but the crash occurred. I went back to vanilla and deleted the bank scrip. I get an error on startup but the mission can play. It gets no dialog about money, but it also does not crash. I'm thinking something called by those functions is hitting a bug with persistence being disabled. That is all I was able to spend time doing. If I can narrow down further I will let you know.

I just did a repro as a single player on my local box. I got a Chinook out of Nalchik. Here are answers to your questions and some additional info (helpful or not, I'll let you decide) Crash - DCS completely shuts down. No errors or messages. Just back to the windows desktop. This occurs right after the "new funds" dialog in the game comes up. In this run it was aprox 190 seconds after dropping off troops at that power plant thing to the south of Nal (first objective) and capturing it with troops. I was in the new Chinook and on a return flight at the time of crash. Modifications - No mods to the mission itself, just a Stright download. Other missions appear to run fine, including pretense. I do have blackhawk and hercules mods loaded. Now running SRS, although I don't think I was when this first started. I don't think I have the stopGapGUI loaded unless it came with something else. Folders - I removed the "saves" folder and the "Expansion (data)" folders prior to the test. I know, hard for you to figure out the cause/problem. My bet is that it is something to do with the funding system and code that executes, as that seems to occur the first time and trigger the crash. Is there any easy flag to disable the funding or force it differently to rule it in or out as a cause?

My buddy and I recently found this mission and it seems awesome. We played for a few hours but had forgotten to adjust the persistence. Since fixing that, we are now seeing it crash after the very first objective capture and the attempt to bank the money shortly there after. We have tried a few things to figure out the cause (solo, multi-player, different host, etc.) but it is consistent. If there is anything else we can do to help you identify and fix the issue, let me know. This was with 1.50 and 1.51.