Page MenuHomeFeedback Tracker

Mission parameter "disableChannels" removes ability to throw grenades
Need More Info, WishlistPublic


For some strange reason the mission parameter (set in description.ext within a mission folder) disableChannels stops players from using the "Throw" weapon.

Example config entry:

disableChannels[]={0,1,2,6}; {F24501} {F24502}


Legacy ID
Steps To Reproduce
  1. Start a new mission, place a player unit and save it.
  2. In the mission folder create text file description.ext
  3. In the text file add "disableChannels[]={0,1,2,6};" (without quotes).
  4. Play the mission and observe that you cannot use grenades of any sort.

Event Timeline

SilentSpike edited Additional Information. (Show Details)
SilentSpike set Category to Config.
SilentSpike set Reproducibility to Always.
SilentSpike set Severity to None.
SilentSpike set Resolution to Open.
SilentSpike set Legacy ID to 4222732225.May 7 2016, 7:09 PM
Bohemia added a subscriber: AD2001.Aug 4 2014, 2:54 PM
Iceman added a comment.Aug 4 2014, 4:29 PM

I could not reproduce the problem (with packed and unpacked mission file). Could you please upload a mission file here and also your newest rpt?
C:\Users\<Name>\AppData\Local\Arma 3\
Thank you very much.

Sure thing, should be up in 10 minutes or so

Scratch that. Can no longer reproduce the issue.

I could definitely reproduce earlier by removing and adding that config entry (on an entirely non-modded setup).

My .rpt from that earlier session is much longer so I've taken a look and tracked down the point where I ran into the issue (I can tell because I switched the unit I was using from I_G_Soldier_TL_F to B_G_Soldier_TL_F to see if it was something to do with that). The point where I encountered it was around line 1228.

Going to upload that full .rpt now, with some personal info stripped out.

Okay, so the file size of that one is too big to upload. I'll see if I can cut out everything that happened after I figured out what was causing the issue and moved on to making my mission again.

There we go, I cut out all the stuff that happened after I found the source of my issue. So it's still around about line 1228 that it occurred.

And there's the mission I was working on at the time. It is a WIP so it has changed a little since I ran into the issue.