Page MenuHomeFeedback Tracker

Radio Support description.ext "cost variable" bug after 1.2
Closed, ResolvedPublic


After the patch I noticed the radio supports stopped working in my custom missions, I troubleshooted the problem and found out that if I put
cost_variable = ""; to anything other than blank (infinite) I cannot choose payload on any support that has any cost. I have the cost variable at 150 and most supports cost around 10. I can call in supports that have their costs set to 0 but no others.


Operating System
Windows 10 x64
Steps To Reproduce

Make a custom mission, copy the info from to your description.ext and then put anything other than a blank space in cost_variable = ""; . When trying to use the radio support it is not possible to select any payload for that support unless it's cost is 0.

Additional Information

Worked fine before the patch!

Event Timeline

Ftmch created this task.Jul 16 2022, 9:30 AM
Ftmch edited Steps To Reproduce. (Show Details)Jul 16 2022, 9:34 AM
Ftmch edited Steps To Reproduce. (Show Details)Jul 16 2022, 11:50 AM
veteran29 changed the task status from New to Need More Info.Jul 16 2022, 6:47 PM
veteran29 added a subscriber: veteran29.

Unable to reproduce the issue, make sure your variable contains number not some other type.

  1. Used example config from wiki
  2. Added score variable to config
  3. Called "Rambler" callsign with cluster munitions
  4. Score was properly deducted and plane was called

See example mission:

Ftmch added a comment.Jul 16 2022, 8:29 PM

Setting the cost_variable to "arty_score" and then adding "arty_score = 150;" to the init.sqf worked, before I was able to do it by just setting "arty_score" to "150" in the description.ext but I suppose that isn't possible anymore? Or else I was dreaming before..

Ftmch added a comment.EditedJul 16 2022, 8:44 PM

To be more specific I uploaded my description.ext that worked before the patch (unless I'm crazy) but stopped working after the patch. Switching out "150" to "arty_score" and adding "arty_score = 150;" to the init.sqf worked like I said so I'm gonna go with that from now on.
edit: did a double check and I'm 99% sure that using a number as arty_score in description.ext worked before the patch (or at least a couple of months ago)

veteran29 closed this task as Resolved.Jul 17 2022, 4:55 AM
veteran29 claimed this task.

It probably worked but not exactly as intended as you weren't able to adjust the score that way. It was always intended to be NAME of VARIABLE that holds the score. Not the score value, as per comment in config/wiki documentation.

Ftmch added a comment.Jul 17 2022, 8:35 AM

Understood! Will adjust my missions accordingly, thank you!