seowhq.net

Bobby landed...plane Stuka......status KIA

During the last mission, (SE-Crete-194105211300.mis) my teammate 72sq_4gatti, due to problems has not taken off, and has not even started the engine, but mission's statistics shows him as KIA, and his plane was lost.

72sq_SilVal wrote:During the last mission, (SE-Crete-194105211300.mis) my teammate 72sq_4gatti, due to problems has not taken off, and has not even started the engine, but mission's statistics shows him as KIA, and his plane was lost.

I can confirm! He was in my flight and he has disconnected few seconds after the mission start.

I am sure Shades will confirm this but I think that is one of the idiosyncrasies of SEOW.

If a landing event or baled out event is not recorded then the pilot is listed as KIA. The only way to avoid this is to take-off and land whereby pilot and a/c are safe or to bale out before taking off and also save the a/c and pilot.

Last week the EAF lost two pilots who had player ready screen bug before takeoff and could not take-off or bale out and are listed as KIA and we lost those a/c.

Are these sort of events being corrected and are aircraft being replaced?

If yes then I will check the allied side of these bugs to ensure a/c are returned if appropriate.

I am sure Shades will confirm this but I think that is one of the idiosyncrasies of SEOW.

Not really. It is a feature that is enabled/disabled by choice of campaign setting. If the "Enforce Pilot Landings" setting is ON, then any pilot that does not register a "Landed", "Bailed" or "Emergency Landed" event in the eventlog will be counted as KIA and airframe crashed.

If the setting is OFF, then no action will be taken for any pilot that does not land etc. So, you see, it is not an SEOW idiosyncracy, it is a simple campaign design choice. Campaign design choices are nothing to do with me.

Cheers,
4S

Please don't report this kind of stuff anymore, personal stats are not edited in this campaign, and any AC loss due to connection/client bugs is not compensated for.