Captured... at friendly airfield

[KillerCharlie]

I was halfway through a career as a 109 pilot. During one of the missions, I landed at a nearby friendly airfield where all the Ju-87s I was escorting landed. At the end of the mission I was CAPTURED. 

 

I didn't notice I was captured when I exited the mission, so now I can't replay it. How ridiculous - I was a few km away from my assigned airfield. How on earth do you get captured landing at a friendly field? I was nowhere near the frontlines either. Is there any way to edit the career and get him back?

 

Why even have pilots be permanently captured? You already have the option to replay the mission... unless you didn't notice you were captured (because you landed safely at an airfield 5km away).  

 

The graphics are great in version 3, but some of these things are really annoying. Disappearing enemy airplanes, 30 minute missions where not a single enemy shows up, and accelerated time that says "8x" when it's actually about 1.5. I'm taking a break from this game for a while to see if anything gets fixed. 

Edited April 9, 2018 by KillerCharlie

[Finkeren]

Clearly a bug and should be reported. 

 

On the other hand, it is not a consistent problem with the career mode. I have landed in the field or at friendly airfields quite close to the front multiple times in career missions and got back just fine.

 

Still, this sort of error is obviously annoying, game-breaking even - since it can easily cause you to lose an entire career, I would be pissed if it happened to a 30+ mission Iron man career of mine.

[Godspeed]

I have noticed several times that when i attack enemy ground targets with Bf-110 i get friendly fire.

When flight is over i check map i see only enemy trucks / guns destroyed.

Edited April 9, 2018 by Godspeed

[Lensman]

I think, to avoid this kind of situation, there should ALWAYS be a 'replay last mission' option on the career even if the system has to generate a new 'last mission'. Being locked out of a lengthy career with no options is unacceptable, more so if it's because of a defect like this.

[seafireliv]

Interesting. I wonder if airfields very close to the border can swap allegiances in real time before the map is updated? I`ve not had anything like that happen yet. However, normally the airfield I can land at always has flares firing, don`t know if it`s the same for Axis fighters.

 

There was the 2nd to last mission yesterday where I arrived late to the airfield where friendlies (not my squad) were landing. My squad had already landed and gone. There was no flare as usual. Since I was close to the border and remembering the forums and a guy talking about this issue,  I circled round and round, making sure this was my correct airfield, checked another nearby airfield and after about 10 minutes decided to land. I was accepted.

 

 

[Eicio]

It reminds me of a "bug" I had yesterday.

 

I was flying one of the two brand new G6 we received ans I took a bullet that made an oil leak to my engine.

 

I was able to land my plane nicely on my airfield in order to retrieve it, even if my engine had died the landing was perfect.

 

At the end it said that my 109 was "crashed" 

[Yogiflight]

1 hour ago, seafireliv said:

Interesting. I wonder if airfields very close to the border can swap allegiances in real time before the map is updated?

No there are no map updates like this. The frontlines only move, when a new phase of the game starts.

10 minutes ago, Eicio said:

I was flying one of the two brand new G6 we received ans I took a bullet that made an oil leak to my engine.

 

I was able to land my plane nicely on my airfield in order to retrieve it, even if my engine had died the landing was perfect.

 

At the end it said that my 109 was "crashed" 

This, plus the other way round, I am a bit dissapointed, that damaged aircrafts, like a smoking engine or a damaged water radiator or many holes in the aircraft, don't count as damaged. What does it need, that your aircraft counts as damaged?

[Eicio]

I see what you mean, it's a little "all or nothing" for now.

[Finkeren]

Dead engine = crashed. It's been that way since Rise of Flight.

 

The "damaged" aircraft only seem to appear in missions that you don't fly yourself, which is a bit disappointing but is likely just a feature that isn't fully implemented yet. It worked fine in the RoF career, so is clearly something they know how to do.

[=LD=Hethwill]

There's Emergency Landing result as well. So far only found it with a fuel situation, but was already on last approach to runway when it dried out 50m from the ground, so she rested gently.

 

The captured situation in the frontlines may be dynamic, like the AF is contested ? Last mission I had to bail and was very worried i would be captured but somehow managed to evade and was inside enemy lines with a river in between the frontlines. So not sure how it all works.

[56RAF_Roblex]

I would like to know why so many of my landings in career mode get recorded as 'forced landing' when I put it down perfectly at my home base.    I would understand if I landed heavily or was very badly damaged before landing but most of them are just normal landings.  Could it be because I had some unimportant bullet holes in my tail?  Is it because I ignored the control tower and landed without permission?   Is it because I usually taxi to the revetments before switching off and despawning (though I always get the 'Landed' message before leaving the runway)?

 

It does not affect anything but I would love to know what it thinks I am doing wrong.

[KillerCharlie]

Just to add to my original post: it was a good landing (no airplane damage, no hard landing). I got the successful landing notice when I landed in-game. The airfield was a long ways from the Frontline.

 

I'm also pretty sure I got the "successful landing" after I finished the mission - on the same screen that says I got captured.

 

I wonder if it's the particular map I'm on. I've been captured on several missions where I crash landed well within friendly territory. One time my engine died and I landed 100 feet short of the runway and was still captured! Clearly there's something wrong. 

 

I'm glad others agree that permanent capture is a bad idea. It's easy to miss the text that says you're captured and lose your career (especially in friendly territory). If you want permanent capture, isn't that what Ironman is for?

Edited April 9, 2018 by KillerCharlie

[QJ-Q_Anton]

2 hours ago, 56RAF_Roblex said:

I would like to know why so many of my landings in career mode get recorded as 'forced landing' when I put it down perfectly at my home base.    I would understand if I landed heavily or was very badly damaged before landing but most of them are just normal landings.  Could it be because I had some unimportant bullet holes in my tail?  Is it because I ignored the control tower and landed without permission?   Is it because I usually taxi to the revetments before switching off and despawning (though I always get the 'Landed' message before leaving the runway)?

 

It does not affect anything but I would love to know what it thinks I am doing wrong.

 

Could it be the wind direction? I'm glad someone else noticed this. It does not seem to be related to damage or taxiing, but landing without permission is something I had not considered. Reported here:

 

[sniperton]

As to 'forced landing', it may be related to you having landed not on the runway from where the flare signal fired off at airfields with multiple runways. Maybe also landing direction matters. It seems that the game penalizes not following the flight plan.

[56RAF_Roblex]

 

No the 'Forced Landing' has nothing to do with using the wrong runway.   There are always flares and usually one of my flight has already landed on that runway before me and others are trying to turn finals behind me and being told the runway is busy.   Sometimes I watch one of them land before I despawn but I am cautious about that because once only three of us made it back and all were happily in the circuit and undamaged and I taxied to one side to see the other two land and they collided instead.  It is safer to despawn as soon as possible and not give the AI a chance to do something stupid.

[LukeFF]

You guys have to post the mission files when these sorts of things occur if you want the developers to look into the problem.

[sniperton]

@Roblex: Then maybe just a game quirk, similar to when you get the message that the mission is complete and you can head home and the 'finish mission' label turns green, but if you land or exit before the squadron leader passes by waypoint #3 or gets close enough to the airfield, the mission will be counted as 'unsuccessful' and there's a chance that your squad member will be MIA.

 

@LukeFF: We're just trying to find out whether it's a bug or a feature.  But if you say it sounds like a bug, next time it occurs I'll post the files.

Edited April 10, 2018 by sniperton

[KillerCharlie]

Are the mission files the one in the Missions folder?

 

At any rate, I used the database editor to rescue my captured pilot. 

[LukeFF]

17 hours ago, KillerCharlie said:

Are the mission files the one in the Missions folder?

 

Yes, those are the ones.