[INVESTIGATING]AI Are Not Respecting The Aerodrome Coalition Change

[VAF [136] Striker]

We use a lot of missions that cap airbases but the AI are NOT respecting the coalition change. We did this test and once you capture a red airbase and turn it blue, the red aircraft will continue to spawn on the airfield. This problem was not happening a few patches back. I'm attaching the test mission file and ACMI.

----------------------------------

I added another test mission to demonstrate that this is not a third party script problem. I did another test mission with simple triggers and the problem still is happening.

Tacview-20200629-150502-DCS-VAF Patrol Base Capture Test Caucasus.zip

VAF Patrol Base Capture Test Caucasus.miz

Tacview-20200629-183619-DCS-VAF Patrol Late Activation Test Caucasus.zip

VAF Patrol Late Activation Test Caucasus.miz

Edited June 30, 2020 by 75th-VFS-Striker

[BIGNEWY]

Hi

 

do you have a track replay showing this happen?

 

The tacview and miz files help but we need to see it reproduced, if you do have a short server track replay that would be great.

 

we do have a similar issue reported, but it is also a difficult issue to reproduce.

 

thanks

[VAF [136] Striker]

We have about a dozen missions where it used to work correctly and now it doesn't so I'm really surprised that no one else has reported it. I'm attaching a track file that I just did this morning and it clearly shows that about 7 minutes into the mission that blue takes ownership of the airfield but red still is spawning in. We also have the same problem when we put blue clients on a red airfield so when we take the airfield we have available aircraft but we can jump into them before we take it. So it's failing to work correctly for both clients and AI.

 

Just to be clear, this has always worked in the past up till I think two patches ago on OB. I have not tested it in stable because I don't have that installed, but everyone in our group is reporting the same problem. Also, this is a global problem and not a map problem. We have the same type of scenarios on the PG map and the Caucasus and it's happening on either one. And the airfield runways in PG are repairing in 1 hour instead of 10 like in Caucasus. This happened about the same time.

VAF Patrol Late Activation Test Caucasus-20200701-100146.trk

[BIGNEWY]

Sorry I am not seeing a bug here.

 

If you have late activation units set to spawn at the airfield they will spawn regardless of who has the airdrome,

 

unless as a condition you have set coalition has airdrome and selected the airfield

[VAF [136] Striker]

Never used to work that way BN and it's causing all sorts of problems in our MP scenerios. We didn't use any of the "coalition has aerodrome" back a few years ago and the red would not spawn on a blue airfield or vice versa.

Edited July 2, 2020 by 75th-VFS-Striker

[Montrose]

Sorry I am not seeing a bug here.

 

If you have late activation units set to spawn at the airfield they will spawn regardless of who has the airdrome,

 

unless as a condition you have set coalition has airdrome and selected the airfield

this is a bug and I have tested 6 of my missions that used to work are now broken. I have reviewed to different scenarios that used to work that now don't. AI spawning into a base can now spawn in after the base coalition has changed. We now have enemy aircraft spawning on friendly airbases - this never used to happen. Late activation client slots can now be entered regardless of Coalition even when we use Coalition has Aerodrome. this never worked before.

 

Another example is patrols will continue to spawn even when their airbase is lost - this never ever worked this way before.

 

We run two servers and have built over 50 missions and this was never an issue until the last few patches. I wondered if this was introduced during the addition of Neutral Coalitions

[BillyCrusher]

It's impossible.

You set group in ME and this group has assigned country and coalition which written into miz file.

If airfield changes colour which country should bt assigned for the group? If you set Su-25T with delayed start and airfield became blue, which country should be Su-25T?

Coalition always set in mission file. It just can't be changed in sumulation.

[VAF [136] Striker]

OK Bignewy, I did another mission to show you the difference. I placed a group of late activation A-10C's on Sochi Airfield. I should NOT be able to get into this client aircraft because the condition for making them available is set by a trigger now. When blue owns the airfield they are activated. This is how we've been doing our missions in the past and it always worked that you could NOT get into a client aircraft until it was activated by your coalition owning the airfield. It looks like something happened with the back end code so that the airfield is showing as either red/blue/neutral on the map but it's state is somehow always being all three instead of just one of them. So when the mission started the A-10C's were already activated. I'm adding a new mission file and track file.

VAF Patrol Late Activation Test Caucasus-20200702-114911.trk

VAF Patrol Late Activation Test Caucasus v2.miz

Edited July 2, 2020 by 75th-VFS-Striker

[VAF [136] Striker]

It's impossible.

You set group in ME and this group has assigned country and coalition which written into miz file.

If airfield changes colour which country should bt assigned for the group? If you set Su-25T with delayed start and airfield became blue, which country should be Su-25T?

Coalition always set in mission file. It just can't be changed in sumulation.

That's not what we're saying. We're saying that we're putting another coalition on the other teams airfield, late activated client blue on red airfield, in the editor or client red on red airfield and all are late activation but will still spawn even after the airfield coalition has supposedly changed. Please look at the mission file. I've been building missions in DCS for almost ten years now. I know that they can't change sides after being placed in the editor.

Edited July 2, 2020 by 75th-VFS-Striker

[BillyCrusher]

Aha, I understand now, thanks. Will check.

[BIGNEWY]

We are looking into it, at the moment however on our builds we can not reproduce.

 

We are investigating

 

are you using scripts for this and has it changed any anyway?

 

thanks

Edited July 3, 2020 by BIGNEWY

[VAF [136] Striker]

Thanks for looking into it.

 

We've tested it both ways, with scripts and without with the exact same results. For the last 5 years we've been doing this you could not spawn enemy aircraft on field they did not belong to and now you can. We're also experiencing weird behavior with the MOOSE scripting because of this. I know it's not a DCS problem but I'm just letting you know. In our Operation Khachapuri the red spawn in all over the place now instead of on the airfield like they should. I'm just pointing this out because it started happening at the same time.