Page MenuHomeFeedback Tracker

Dev Branch RPG/Launchers in FFV - 'Switch to Secondary Weapon' keybind doesn't work
New, WishlistPublic


Within the stood-up/turned-out FFV positions in the Offroad truck that allow firing of Secondary weapons (RPG, Titan, PCML etc.) it is not possible to use the 'Switch to Secondary Weapon' keybind from the controls, to switch from your primary weapon (rifle etc.) to the afore mentioned secondary weapons.

The older 'Switch gun / launcher' keybind can be used to shoulder the launcher, or by selecting it through the action menu.

The 'Switch to Primary Weapon' and 'Switch to Handgun' keybinds work fine in all FFV seats alongside with the older 'Switch gun / handgun', as does switching to and from binoculars etc. It is only the controls for the launcher slot that are not consistent with how they work when on foot.


Legacy ID
Steps To Reproduce
  1. Board the Offroad in one of the front FFV positions while playing as the 'Rifleman AT' unit
  2. Turn out so that the unit is in the standing FFV position that faces forward
  3. Press the 'Switch to Primary Weapon' and 'Switch to Handgun' keys alternately to see that you can switch between these two weapon slots without issues (might need to check your keybindings)
  4. Press your 'Switch to Secondary Weapon' while holding either your primary weapon or handgun and see that you do not switch to the AT launcher the unit carries on his back.
  5. Use the 'Switch gun / launcher' keybind instead, and see that the unit does now shoulder his launcher.

Additional step:

Dismount from the Offroad and try alternating the 'Switch to Secondary Weapon' and 'Switch to Primary Weapon' keys to show that it does work normally, and the controls are only inconsistent in the FFV seat.

Event Timeline

da12thMonkey set Category to Controls.
da12thMonkey set Reproducibility to Always.
da12thMonkey set Severity to None.
da12thMonkey set Resolution to Open.
da12thMonkey set Legacy ID to 2963469583.May 8 2016, 1:04 PM
da12thMonkey added a subscriber: da12thMonkey.

This issue made its way in to the 1.54 stable patch so have updated the relevant version fields in the ticket