[CAN NOT REPRODUCE]Mission Editor CTD Upon Quitting

[TheHighwayman]

I just started work on a new mission, and during early, preliminary testing, DCS crashes to desktop when I end the mission and select "Quit." Note, I am not selecting "Quit to Desktop," just quit.

 

I have no other issues with DCS, or any of the modules. What is different from the missions I normally build is I am using the Tu-146. I suspect it could be causing the crash when I exit the mission.

 

- .Miz file is attached.

- DxDiag attached.

Fleet Defender - Persian Gulf.miz

DxDiag 9.17.19.txt

Edited September 18, 2019 by BIGNEWY

[BIGNEWY]

Hi

 

Thanks we will take a look

Edited September 18, 2019 by BIGNEWY

[BIGNEWY]

It seems to be related to the F-14B

 

If I remove them from the mission I don't get a crash

[TheHighwayman]

Interesting! I just built a couple Persian Gulf missions with the F-14, but had no such issue.

 

https://www.digitalcombatsimulator.com/en/files/3306293/

https://www.digitalcombatsimulator.com/en/files/3306208/

 

Thank you for working on this.

[BIGNEWY]

Yes something strange about this mission that I can not put my finger on.

 

Did you manually modify the mission in anyway?

[TheHighwayman]

I started building the mission from scratch. I have not used any modded elements.

 

I ran an initial test to see how the bombers behaved and if their missiles would be successful when deployed against the fleet. That was when I noticed the problem, at the end of each of my tests.

 

As I recall, I did the following in this order:

 

I built the fleet, re-naming the ships from "Unit 001" & etc to useful names. I then placed them in a reasonable formation for transiting the Strait. I placed their route, and set their alarm state.

 

I next placed the F-14s. I placed five additional F-14 pairs and set them to late activation. The idea is they will be called up in a series as the mission unfolds. I then placed the Tu-142 bombers and set them to Attack Group.

 

Finally, I set the player F-14 group to Late Activation, so it would not be part of the initial test.

 

The tests worked fine, but I got a CTD each time I ended the mission to return to the editor.

[BIGNEWY]

I can not reproduce if it do it from my own mission, only see it in your mission.

 

Very odd.