Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

weaponselect turns off laser when cycling through fire modes #210

Closed
bux opened this issue Mar 21, 2015 · 3 comments
Closed

weaponselect turns off laser when cycling through fire modes #210

bux opened this issue Mar 21, 2015 · 3 comments
Assignees
Milestone

Comments

@bux
Copy link
Member

bux commented Mar 21, 2015

ACE_Dev: e7d7fa8

Mods:

  • @cba_a3_dev (RC6_v1.20.150317)
  • @ace_dev

Modules:

  • None

Steps to reproduce:

  • Start a night mission
  • Equip a MX Rifle with the "IR Laser Pointer" attachment and add some NVG to the unit
  • Turn on Night Vision and the Laser
  • Press the (default) 2 key to switch fire mode
  • Laser is now turned off

That's different to the default behavior of the F key. And it just doesn't make sense. 😄

@bux bux added the kind/bug label Mar 21, 2015
@bux bux added this to the 3.1.0 milestone Mar 21, 2015
@PabstMirror
Copy link
Contributor

I tried doing:

//Save the flashlight/IR settings:
_flashlightOn = _unit isFlashlightOn _weapon;
_irLaserOn = _unit isIRLaserOn _weapon;

do the "switchWeapon" action

//Reset the flashlight/IR:
if (_flashlightOn) then {
    _unit action ["GunLightOn", _unit];
};
if (_irLaserOn) then {
    _unit action ["IRLaserOn", _unit];
};

Unfortunaitly, the "IRLaserOn" action always resets firing mode to singleshot (at least for mx)
There is a bug report from a few weeks ago about this, that I think we'll need: http://feedback.arma3.com/view.php?id=22954

@commy2 commy2 modified the milestones: Backlog, 3.1.0 Mar 21, 2015
@commy2
Copy link
Contributor

commy2 commented Mar 21, 2015

Backlog, because not fixable atm.

@Mike-MF
Copy link
Member

Mike-MF commented Sep 11, 2023

Closing due to age, inactivity or already solved. May be re-opened if the issue is still present, even better just open a new up-to-date Issue.

@Mike-MF Mike-MF closed this as not planned Won't fix, can't repro, duplicate, stale Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants