Ships that are "Late Activation" are still in object export (and moving).

[Acidictadpole]

I had added a late activation ship to my mission and even before its activated it is still appearing in Tacview as a ship with no group name.

 

 

I tested it in a contained environment and it appears that the ships are appearing in object exports, though not on the F10 map.

 

 

Attached is a small mission that you can use to see the issue. While it doesn't appear on F10 map, connecting with Tacview, or using something to investigate `Export.LoGetWorldObjects()` will show _two_ ships called "052C" (and a player f-16). The mission is set up to have two "052C" groups, where one is Late Activation, and the other is not.

 

 

For my own investigation, I included the following hook and watched the logs:

 

 

callbacks = {}
loaded = false
count = 0
callbacks.onMissionLoadEnd = function()
   loaded = true
end
callbacks.onSimulationFrame = function()
   count = count + 1
   if not loaded or count < 100 then return end
   count = 0
   local obj = Export.LoGetWorldObjects()
   for k,v in pairs(obj) do
       net.log("[+] Acidic Iterating...")
       net.log("[+] Acidic -- Object id: "..k.." -- name: ["..v.Name.."]")
   end
end
net.log("[+] Acidic Loaded export tester")
DCS.setUserCallbacks(callbacks)

Logs for the above produce this in the dcs.log:

 

 

[font=Consolas]2020-03-22 18:13:00.298 INFO    LuaNET: [+] Acidic Iterating...
2020-03-22 18:13:00.298 INFO    LuaNET: [+] Acidic -- Object id: 16777984 -- name: [F-16C_50]
2020-03-22 18:13:00.298 INFO    LuaNET: [+] Acidic Iterating...
2020-03-22 18:13:00.298 INFO    LuaNET: [+] Acidic -- Object id: 16777472 -- name: [052C]
2020-03-22 18:13:00.298 INFO    LuaNET: [+] Acidic Iterating...
2020-03-22 18:13:00.298 INFO    LuaNET: [+] Acidic -- Object id: 16777728 -- name: [052C][/font]

shiptest.miz