[RESOLVED]Tanker Call Sign Bug

[evilnate]

Hi All,

 

In mission editor with version 2.5.6.45915 if you have more than one tanker with same call sign but different number designation, the unique numbers are not displayed in the F10 radio menus. All have 1-1 which makes it difficult to know which tanker your talking to.

 

To reproduce;

 

1. Make mission with two tankers on separate frequencies.

2. Set call signs (Arco 1-1, and Arco 2-1).

3. Launch game and see in F10 menu they are both Arco 1-1.

 

*** SOLVED see below ***

Edited May 28, 2020 by evilnate
conclusion

[Spiceman]

I had this same issue, and noticed that it happened when I joined as Game Master first, and then joined in an aircraft slot. If I joined an aircraft slot straightaway, it worked normally. Weird.

[evilnate]

I had this same issue, and noticed that it happened when I joined as Game Master first, and then joined in an aircraft slot. If I joined an aircraft slot straightaway, it worked normally. Weird.

 

I don't have a game master or any other combined arms slots in the mission. I wonder if this bug report is noticed by the people who can fix it?

 

A work around would be nice as well. :)

[GrizzlyVzla]

I have the same issue, i hope for a fix

[evilnate]

Is this the appropriate location to report DCS mission editor bugs? If yes, are the reports ever acknowledged by devs?

[evilnate]

The title of this thread hasn't received the magical [brackets]. Does this mean the problem many are having isn't a bug?

[Bearfoot]

Are you using MOOSE to spawn the tankers?

 

I had the same issue. Problem solved by using MOOSE to set the callsign number.

[evilnate]

Are you using MOOSE to spawn the tankers?

 

I had the same issue. Problem solved by using MOOSE to set the callsign number.

 

I think you nailed it, thanks!

 

I just tried assigning a callsign but get nil value errors. I'm not using the recovery tanker script for my tankers. Is there a way to assign callsigns to spawned tankers without using the recovery tanker moose script?

 

--Enable respawn of AAR
spawn_us_kc135_1 = SPAWN:New( "us_kc135_1" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(1,1)
spawn_us_kc135m_1 = SPAWN:New( "us_kc135m_1" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(2,1)
spawn_us_kc135_2 = SPAWN:New( "us_kc135_2" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(1,2)
spawn_us_kc135m_2 = SPAWN:New( "us_kc135m_2" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(2,2)
spawn_us_kc135_3 = SPAWN:New( "us_kc135_3" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(1,3)
spawn_us_kc135m_3 = SPAWN:New( "us_kc135m_3" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(2,3)
spawn_us_s3b_1 = SPAWN:New( "us_s3b_1" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(3,1)

[Bearfoot]

I usually set the callsign on the group (in ":OnSpawnGroup") using "::CommandSetCallsign( callsignNameIndex, callsignNumber, 0)".

 

In any case, if it can be set on the spawner, I suspect that your "SetCAllsign" should be "SetCallsign" (case matters!).

 

 

I think you nailed it, thanks!

 

I just tried assigning a callsign but get nil value errors. I'm not using the recovery tanker script for my tankers. Is there a way to assign callsigns to spawned tankers without using the recovery tanker moose script?

 

--Enable respawn of AAR
spawn_us_kc135_1 = SPAWN:New( "us_kc135_1" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(1,1)
spawn_us_kc135m_1 = SPAWN:New( "us_kc135m_1" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(2,1)
spawn_us_kc135_2 = SPAWN:New( "us_kc135_2" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(1,2)
spawn_us_kc135m_2 = SPAWN:New( "us_kc135m_2" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(2,2)
spawn_us_kc135_3 = SPAWN:New( "us_kc135_3" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(1,3)
spawn_us_kc135m_3 = SPAWN:New( "us_kc135m_3" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(2,3)
spawn_us_s3b_1 = SPAWN:New( "us_s3b_1" ):InitLimit( 1, 99 ):SpawnScheduled( 15, 1 ):SetCAllsign(3,1)

Edited May 27, 2020 by Bearfoot

[evilnate]

I usually set the callsign on the group (in ":OnSpawnGroup") using "::CommandSetCallsign( callsignNameIndex, callsignNumber, 0)".

 

Bingo! Thank you very much Bearfoot! The magical [NOT A BUG] can be added to the title!

 

Finished product

local us_kc135_1 = SPAWN
  :New( "us_kc135_1" )
  :InitLimit( 1, 99 )
  :SpawnScheduled( 15, 1 )
  :OnSpawnGroup(
    function( Texaco1 )
   Texaco1:CommandSetCallsign(1,1)
    end 
    )