RADIO ITEM ADD FOR GROUP adds items to wrong group

[Yurgon]

Building a quick ACM and BVR test mission, and my radio items keep showing up in the wrong group (mission attached; only tested in SP so far).

 

I've encountered the problem in DCS 2.5.4.29079 OpenBeta.

 

Basic setup:

- Groups:
 - Hornet ACM (Client)
 - Hornet BVR (Client)
 - MiG-23 ACM (AI)
 - MiG-23 BVR (AI)
- Triggers:
 - Once
 - Condition: TIME MORE (2)
 - Actions:
   - RADIO ITEM ADD FOR GROUP (Group Hornet ACM, "Activate MiG-23 ACM", Flag 101)
   - RADIO ITEM ADD FOR GROUP (Group Hornet BVR, "Activate MiG-23 BVR", Flag 201)
 - Once
   - Condition: FLAG IS TRUE (101)
   - Actions: GROUP ACTIVATE (MiG-23 ACM)
 - Once
   - Condition: FLAG IS TRUE (201)
   - Actions: GROUP ACTIVATE (MiG-23 BVR)

 

But whenever I spawn in the Hornet ACM, I've only got the F10 Radio item "Activate MiG-23 BVR".

 

It's only when I spawn in the Hornet BVR first, and then re-slot to Hornet ACM that the proper radio item shows up.

 

In any case, the flags do correspond to the radio items, so the problem is that the radio items get added to the wrong group; it's not that the wrong flags would get set.

 

Anyone know what am I doing wrong?

 

Possibly related threads:

RADIO ITEM ADD FOR GROUP (Bug)

RADIO ITEM ADD.......

 

On a side note, I'm sure I'll be able to find workarounds or use MiST or MOOSE to get the job done, so please keep this on topic (I'll certainly holler in the proper thread if I can't get it done ;) ).

Yurgon_radio_item_add_for_group_test_2.5.4OB.miz

[A101Wayz]

I think there is a bug in DCS with the radio menu system... If you join spectators first, and then jump into an aircraft, all should be well.

[Sickdog]

I’ll chime in that I had strange behavior as well when choosing a slot for the first time but then it’s fine after that. But something to check which I was able to track down: make sure you don’t have both a script running that adds radio menu items AND also adding radio menu items via the mission editor. I found when I removed the mission editor created radio menu items and only had my script added items, it behaved properly with the first time I occupied a slot at the beginning of a mission. Perhaps a bug? I dunno.

[A101Wayz]

I’ll chime in that I had strange behavior as well when choosing a slot for the first time but then it’s fine after that. But something to check which I was able to track down: make sure you don’t have both a script running that adds radio menu items AND also adding radio menu items via the mission editor. I found when I removed the mission editor created radio menu items and only had my script added items, it behaved properly with the first time I occupied a slot at the beginning of a mission. Perhaps a bug? I dunno.

Never thought of that... Good catch!

[Yurgon]

If you join spectators first, and then jump into an aircraft, all should be well.

 

Sounds plausible!

 

As I said, when I join the second slot (BVR) first, and then join the first slot (ACM), the radio items seem okay. It's quite possible that re-slotting (from which ever slot) solves the problem. Got to test that, thanks for the input! :thumbup:

 

I’ll chime in that I had strange behavior as well when choosing a slot for the first time but then it’s fine after that.

 

Thanks, that seems to point very strongly at a problem simply with the initialization.

 

But something to check which I was able to track down: make sure you don’t have both a script running that adds radio menu items AND also adding radio menu items via the mission editor.

 

Good advice, thanks!

 

In my case, I did not use any scripts at all in order to keep it as simple as possible. But maybe this could help narrow it down. :thumbup: