Redfor spawns to capture airfield even if Mi-26 does not land there

[Terlisimo]

Just saw this happen:

1. Mi-26 goes to Nalchik
2. Nalchik defense damages it, but does NOT destroy it
3. Mi-26 turns back to Beslan
4. Redfor spawns at Nalchik at the moment the damaged Mi-26 lands back at Beslan

I assume there is a trigger "when Mi-26 lands, spawn red units", but does not check where the helo has landed.

[Terlisimo]

I think this is the issue with all airfields, and explains why red forces occasionally spawn at well-defended airfields.

[Acidic]

IIRC there was a check for one of these units' distance from their target airfield to determine whether they're allowed to spawn.

I'll check to make sure that's still functional.

[Terlisimo]

I see the code that handles landing distance, and it passes my in-head parser.

Still, I'm 100% positive I saw what I described above. Even have Tacview to support that claim.

I will try and reproduce the bug. Maybe something returns null, or MIST started returning that value in kilometers haha.

[Terlisimo]

I just reproduced this by accident, but it's definitely an issue.

Happened with Russian An-26, inbound to Sochi, but diverted since blufor took Sochi while An-26 was in the air. It landed at Sukhumi and said "landed 288 meters from target, spawning Russian forces".

Gonna look further into this, but it looks like there's a problem in the transportLand() function, or the data it uses.

Further insight, function calculates distance between event.initiator:getPosition().p and event.place:getPosition().p , that sounds wrong... I mean, event.initiator is always going to be at the place it's landing at, will it not?

[Jeremy Smitherman]

Yeah I think Acidic and I just ID'ed what's going on here, should be fixed soon

[LazyBoot]

Here's a tacview showing the issue
https://1drv.ms/u/s!AuKUcZ9GznIdt_t9OcFKh1BuOARHcQ