Spotter doesn't spot if country is changed?

[LLv34_Temuri]

It looks like a spotter unit won't do the spotting ("radar") if the country of the unit is changed mid-mission. On each airfield, we have a spotting ndb unit (spotting distance set) for which we set the country depending on which side the airfield belongs to. In the mission editor, the unit is defined as neutral. Then at mission startup, we change the country after the mission is loaded. The result is an ndb unit that has the country set as it should be, but it doesn't spot, i.e. there's no "radar" visible in the map. Is this a bug or have we missed something?

[JimTM]

Check that your HUD is enabled (key for "Show/hide entire HUD") and that map markers are enabled (key for "Show/hide instrument panel, navigation and map markers").

 

Also, make sure that your plane is on the same side as the NDB,

Edited April 13, 2016 by JimTM

[LLv34_Temuri]

After some testing on my local computer, I came to the conclusion there's something wrong with the mission we have running on our server. Thank you for the input.

[LLv34_Temuri]

And after some further testing, the culprit turned out to be the Trigger:Spawner MCU. If the NDB is spawned, the spotting won't work. Here's what I have set up, the NDB starts as neutral, and the Behaviour MCU sets the country to German:
 

I login to the server, hop into a German plane, but the spotting doesn't work. If I remove the Spawner, the spotting works.