reported TSD showing Enemy FARPs Ignoring Map Options

[MartinCo]

Using attached miz: ah64-enemy-farp.miz

Map options enforced allies only

Occurs both in single player and multiplayer

Reproduction:

* Spawn in AH-64
* Navigate to TSD and observer a control measure slightly to the west
* Use the F10 menu to spawn a new farp (approx 1nm to the east)
* Note that this is not shown on the TSD
* Change Slot / Reslot on the AH64
* Note that we now have both hostile farps shown as control measures on the TSD

This causes a real issue on multiplayer servers that wish to have players stealthy offensive farps

DCS Version: 2.9.21.16362
Track file: ah64-hostile-farp.trk

 

Edited November 1 by MartinCo

[Floyd1212]

You are conflating a couple different issues together here.

13 minutes ago, MartinCo said:

Map options enforced allies only

This only pertains to units shown on the F10 map, not the map some aircraft have on their MFDs, like the Apache's TSD.

To force something like an enemy FARP to not be visible on the aircraft's MFDs, you need to check the option in the ME "Hidden On MFD"

When you spawn into the aircraft, all of the friendly and enemy units are added to the internal database of the aircraft and populated on the TSD (unless this box is checked for each group), up until the database is full.  When you spawn the second FARP using the script, the TSD is unaware this has happened and it does not show up.  Then when you reslot in a new airframe, all the units on the map are enumerated and the new FARP gets added to the database.

You will also notice that they are re-numbered so that the new FARP is C52 and the original one is now C53.  (Maybe it numbers them based on closest proximity to your aircraft?)  This will be different for you vs. a team member who spawned in before the new FARP was created.  Your C52 is not the same as their C52.  This is also true for SAMs and other enemy/friendly units that may have been killed since you slotted in the second time.

To get the new FARP to not be visible when it is spawned in, the script needs to set the attribute "HiddenOnMFD" to "true" when spawning the FARP.

[MartinCo]

Sorry! You're absolutely right for the miz embedded ME placed FARP

However adding hiddenOnMFD to the addStaticObject call to create the FARP does not work and it still shows up on the TSD in the apache that spawns after.

local farp = coalition.addStaticObject(country.id.RUSSIA, {
        ["category"] = "Heliports",
        ["shape_name"] = "FARP",
        ["type"] = "FARP",
        ["x"] = -83000,
        ["y"] = 852000,
        ["name"] = "Spawned FARP",
        ["heading"] = 0,
        ["dynamicSpawn"] = true,
        ["hiddenOnMFD"] = true,
})

farp:getWarehouse():setItem("UH-1H", 10)

trigger.action.outText("FARP Spawned", 10)

This is different to both my previous reports that have both either been acked, or fixed in the case of the ch47:
- NS430 - reported
- CH47 - reported + fixed 

Note if you jump into the CH47 - neither the ME, nor spawned hostile farp is shown in the nearest airports etc (only friendly ones if present)

null

So there is certainly some inconsistency here and maintain there is an issue to address

 

[MartinCo]

@Flappie would you be able reproduce / report this please ?

[Flappie]

Hi @MartinCo. I checked your track and saw what you saw. Then I checked "Hidden on MFD" in the Mission Editor FARP options, and the issue was gone.

 

ah64-hostile-farp_FIX.trk

[Vakarian]

@Flappie If I understood the report correctly, it seems like the issue is only with script spawned FARPs. When they are marked as hidden on MFD via mission editor, then it works as intended.

[Flappie]

The first FARP is part of the mission, and it was not "hidden on MFD".

The second FARP is a copy of the first FARP, spawned at another location.

Once I checked "hidden on MFD" for the first FARP, it no longer displayed on the MFD. Neither did the second FARP when I spawn it using the F10 radio item.

Feel free to try my track/mission and tell me if you keep seeing an issue.

[MartinCo]

What @Vakarian said

> The second FARP is a copy of the first FARP, spawned at another location.

It isn't a copy (not same unit id / group id etc) the 2nd farp will only show on your MFD after you restart the ah64

The reason it didn't show up in your track is that you have to respawn your apache after the farp is created for the TADS to show updated control measures

So easiest to use the miz as a local multiplayer server

* Spawn in taccom (just to save time)
* F10 spawn farp
* Spawn in AH64
* Observe spawned FARP as control measure
 

[Flappie]

I forgot to respawn, indeed. I'll try again.

[Flappie]

Bug reproduced and reported. 

[MartinCo]

Amazing, thank you so much @Flappie