Just had a strange thing happen on the Odessa map...

[BlitzPig_EL]

I generated a coop mission with Vander's Easy Mission Generator.   Four IL2s escorted by four Mig 3s.  Attack truck convoy.

I played it alone as I was testing the mission.  Flew out from Odessa No.2, attacked the column, flew back, and I landed first and taxied over to the large hangers on the south side of the field.  I shut down the engine and was waiting for my AI flight to land looking out of my cockpit when my plane suddenly was thrust straight up into the air, then it nosed over and crashed and exploded, ending the mission.  I had no control over anything.

 

I don't have a track, sadly.  Is there a record of the mission hiding somewhere I can send?

[kraut1]

2 hours ago, BlitzPig_EL said:

I generated a coop mission with Vander's Easy Mission Generator.   Four IL2s escorted by four Mig 3s.  Attack truck convoy.

I played it alone as I was testing the mission.  Flew out from Odessa No.2, attacked the column, flew back, and I landed first and taxied over to the large hangers on the south side of the field.  I shut down the engine and was waiting for my AI flight to land looking out of my cockpit when my plane suddenly was thrust straight up into the air, then it nosed over and crashed and exploded, ending the mission.  I had no control over anything.

 

I don't have a track, sadly.  Is there a record of the mission hiding somewhere I can send?

in your IL-2 BoS/data folder are mission report txt files of each mission. Maybe there is some information recorded?

Concerning your issue was something wrong with the landing gear of your plane? Maybe partly damaged?

[BlitzPig_EL]

Kraut1, I had taken damage on the mission.  Rear starboard elevator and canopy were missing after I encountered a pesky tree on the side of the road.

Still I was completely stopped with the engine off, just sitting there watching the AIs bimble about in the landing pattern when my IL2 leapt straight up well above the tops of the hangars, then it fell nose down and exploded when it hit the ground.

 

I will try to replicate it today sometime.

[Zooropa_Fly]

I take it there were no enemy bombers in the area at the time ?

[BlitzPig_EL]

No, and there was no explosion until my levitating plane stopped levitating and came down and hit the ground.  It was like spawning a parked aircraft several tens of meters above the ground, then it fell.  My plane was in it's three point attitude, like it was sitting on the ground, as it moved up, then as it came down the nose dropped and it went nose first into the ground and exploded.

 

Strangest thing that has ever happened to me in game.

[BlitzPig_EL]

So, I re-made the mission and moved to Odessa 1 as home field, ran the mission and completed the objective, took damage from enemy fighters on the way to the combat area.  Flew back to base with one 20mm damaged, and missing the right aileron, plus numerous bullet holes and the "engine damaged" icon on.  Landed fine, taxied to the repair area this time, shut down the engine, and after a few seconds was levitated and then dropped which exploded the aircraft and ended the mission before my flight could land.

 

Very strange.  I was flying the IL2 41.

Fun mission otherwise.

[MaxPower]

This sounds like a collision geometry issue to me.  Some kind of collision overlap that should be impossible occurs, and ejects the dynamic object at great speed in order to resolve the collision.  Could be something else but it does sound like a classic collision problem.

Edited October 5, 2025 by MaxPower

[BlitzPig_EL]

I did brush a tree again when attacking the German vehicles.  Seems odd that the collision would somehow wait till after I flew 50+ km and landed and shut off the engine before kicking in.

[kraut1]

3 hours ago, BlitzPig_EL said:

So, I re-made the mission and moved to Odessa 1 as home field, ran the mission and completed the objective, took damage from enemy fighters on the way to the combat area.  Flew back to base with one 20mm damaged, and missing the right aileron, plus numerous bullet holes and the "engine damaged" icon on.  Landed fine, taxied to the repair area this time, shut down the engine, and after a few seconds was levitated and then dropped which exploded the aircraft and ended the mission before my flight could land.

 

Very strange.  I was flying the IL2 41.

Fun mission otherwise.

Although I know that there are sometimes repair areas I have to admit that I have never used the repair / refuel function.

Have you tried to shut down the engine far away from this repair area?

As far as I can remember my plane has been catapulted in the air 2 or 3 times.

1 time after retracted accidently the gear after landing and 1 time after my gear collapsed during a crash landing with a damaged plane. But at least one time without explosion / pilot survived.

[[CPT]Crunch]

Make sure you raise flaps before shutting down, it's a common thing that happens if you don't have them up in online repair areas.

[Aapje]

7 hours ago, BlitzPig_EL said:

I did brush a tree again when attacking the German vehicles.  Seems odd that the collision would somehow wait till after I flew 50+ km and landed and shut off the engine before kicking in.

 

It's very unlikely that this is the cause. There may be some hidden objects on that airfield or some weird interaction with the flaps and the repair area like Crunch said.

 

You should upload the mission report so the devs can take a look.

[Jaegermeister]

9 hours ago, [CPT]Crunch said:

Make sure you raise flaps before shutting down, it's a common thing that happens if you don't have them up in online repair areas.

 

It sounds like a bug with the repair process. Has anyone reported this. It would probably be a good idea to do a thorough bug report

[JG4_Moltke1871]

@BlitzPig_EL @Jaegermeister

 

It makes me remember a bug I experienced in flying circus on Flugpark server. If your ailerons damaged and you start a repair your plane gets instand destroyed. It seems this bug is still in the game? 
 

[BlitzPig_EL]

Interesting.

 

[BlitzPig_EL]

Well here is the flight log...

 

missionReport(2025-10-04_20-52-30).zip

[Aapje]

@LukeFF See the previous message.

[BlitzPig_EL]

Thanks Aapje, I didn't remember to alert the team about this.

[LukeFF]

17 hours ago, BlitzPig_EL said:

Thanks Aapje, I didn't remember to alert the team about this.

 

It looks like the mission file isn't in that attachment. 

[BlitzPig_EL]

Hmmmm.  Can you point to exactly where it is located in the Data>Bin folder?

 

Or maybe I'm just a dumbass with Windows 11, which I am still getting used to for some things.

[LukeFF]

It's the file with the .mis extension, in the folder where you saved the mission.

[BlitzPig_EL]

Is the highlighted file the one you need?  I see none with a .mis extension.

 

[BlitzPig_EL]

@LukeFF

 

I hope this is what is needed.

 

Odessa Attack.zip

 

 

[Wruin]

@BlitzPig_EL

 

FYI, the default behavior in Windows 11 is to hide 'known' file extensions. Because the Odessa Attack.mis file appears to be associated with notepad, Windows thinks it knows the file extension and is thus hiding it from you. You should probably turn this behavior off; I personally find it very annoying!

 

[BlitzPig_EL]

God I hate 11 sometimes. I cannot for the life of my find the properties window that shows those options.

 

I give up.

Edited October 7, 2025 by BlitzPig_EL

[No_85_Gramps]

8 hours ago, BlitzPig_EL said:

God I hate 11 sometimes. I cannot for the life of my find the properties window that shows those options.

 

I give up.

With file explorer open click on the three dots and select options and then the view tab.

[BlitzPig_EL]

OK I just checked and my properties are set exactly as Wruin's image shows.  

 

I still see no files with a .mis extension, just  MISSION file.

Edited October 7, 2025 by BlitzPig_EL

[AEthelraedUnraed]

3 hours ago, BlitzPig_EL said:

I still see no files with a .mis extension, just  MISSION file.

That's because @LukeFF must've been elsewhere with his thoughts and actually meant the .mission extension when he said .mis

 

The Mission file is the one you're looking for.

[Jaegermeister]

The other file is .msnbin... short for mission binary, and is actually faster to open in the editor. If you only send the .mission file it takes a few minutes to create the binary file before it will open the mission.

 

Either one works, just putting that out there FYI.

[BlitzPig_EL]

Thanks for the clarification gents.  I thought I was losing it there. 

[No_85_Gramps]

My thoughts were like yours BlitzPig. I wonder if an update changed the file extension? I swear at some time they were .mis, might just be my age.

[BlitzPig_EL]

I'm not a spring chicken either Gramps.

[Aapje]

 

Literally, in this case.

[BlitzPig_EL]

 

[LukeFF]

From one of our mission designers:

 

"I played this mission and couldn't reproduce the bug. It looks like a bug with the maintenance vehicle.

1. "hangers on the south side of the field". Is that them? (see screenshot). If so, it is no longer a maintenance area.

2. Is the mission cooperative, did he launch it through Multiplayer/Cooperative? Or did he save it as a "single" and run it through Missions?

If he has time, let him record a track." 

 

[BlitzPig_EL]

It was cooperative run in Multiplayer.

 

I'll try to replicate it again.

 

The south side hangers are when the mission home base was Odessa 2.

Edited October 8, 2025 by BlitzPig_EL

[MaxPower]

On 10/4/2025 at 7:42 PM, BlitzPig_EL said:

Seems odd that the collision would somehow wait till after I flew 50+ km and landed and shut off the engine before kicking in.

Collision is a system that is always active, not like the state of colliding with something.  For instance, if your plane is in contact with the ground, there is a system that's monitoring that every frame.  Usually, the geometry used to calculate that stuff is invisible and a simplified version of what you see.  So, given that it's invisible and not exactly the same as what's being rendered, glitchy collision can happen when everything seems fine visually. 

 

I only mentioned it out of interest's sake.  We don't have any real capability to debug that, I don't think... Unless you noticed weird debris or craters in the proximity of where you came to a stop and can replicate it.

 

Lastly, when you turn off your engine and the repair starts, that is the type of situation when you could expect a mode change.  It's during mode changes when problems like these are most likely to occur.  Again, pure speculation since I don't know how the engine works.