Plane crashes in career mode if game interrupted before landing

[Cleo9]

I'm new to the game, been playing it for 2 months. I used to be a big fan of the original IL-2. I purchased BOS, BOM and BOK  a while ago, but I needed a new PC to play the game with optimal settings. I have acquired my new rig a couple of months ago and am now playing SP, improving my skills in order to eventually play online

 

Since the latest update (3.201) I have noticed that anytime I leave the game after completing my critical objectives but before landing back at the base, my plane is considered to have crashed. It happens all the time, systematically. It was not the case before, if I remember correctly. Is this a known bug of some sort ? Sometimes, returning to base can be long and boring, so I generally prefer to cut it short and just leave the game after completion of my objectives, but now it is not an option anymore. Kinda frustrating... 

 

 

[Utopioneer]

I also noticed this. I primarily fly PWCG co-op campaign, and we used to finish mission if everybody was in good shape and we were over friendly territory. After the most recent update we realized our planes were being considered lost/crashed. We now have to land ever mission if we don't want to run out of planes.

[PatrickAWlson]

9 minutes ago, Utopioneer said:

I also noticed this. I primarily fly PWCG co-op campaign, and we used to finish mission if everybody was in good shape and we were over friendly territory. After the most recent update we realized our planes were being considered lost/crashed. We now have to land ever mission if we don't want to run out of planes.

 

Need to look into that more from a PWCG perspective.  If the logs say the plane crashed then it crashed, at least as it stands today.  At least with PWCG I might be able to do some coding to detect crashes at the very end of the mission and ignore them.  Unfortunately that doesn't help players outside of PWCG. 

 

Would prefer that 1C simply change this logic as that would save me some work  .  My speculation is that this is in place to prevent MP players from quitting when they are in a tight spot.   A possibility is only do this on multiplayer dogfight servers and not single player (why?) or coop (coop is by invitation so presumably participants can be trusted not to be butt heads).  

[Utopioneer]

Yes to clarify this was definitely a change in the game engine logs and not something Pat changed.

 

At least in my squadron of players, logic that ignored a crash state right at the end of a mission would solve it. We used to make the decision as a group to finish mission, usually to speed up getting back in the air for the next one.

[RedKestrel]

52 minutes ago, PatrickAWlson said:

 

Need to look into that more from a PWCG perspective.  If the logs say the plane crashed then it crashed, at least as it stands today.  At least with PWCG I might be able to do some coding to detect crashes at the very end of the mission and ignore them.  Unfortunately that doesn't help players outside of PWCG. 

 

Would prefer that 1C simply change this logic as that would save me some work  .  My speculation is that this is in place to prevent MP players from quitting when they are in a tight spot.   A possibility is only do this on multiplayer dogfight servers and not single player (why?) or coop (coop is by invitation so presumably participants can be trusted not to be butt heads).  

I may be imagining this, but I thought that the option to simply 'quit mission' was disabled in most dogfight servers when you were in the air already?