VR trigger prevents secondary/tertiary interactions on G1000 + temp. fix (Reverb G2)

Are you using Developer Mode or made changes in it?
NO

Have you disabled/removed all your mods and addons?
YES

Brief description of the issue:

A. Tested parameters

  1. Device: Reverb G2 hand controllers (left & right)
  2. Mode: VR
  3. Aircraft: SR22, C172
  4. Instrument: G1000 (NAV, COM, FMS, RANGE rotary/buttons)
  5. Sim: PC, SU10, no mods

B. Issue:
With the VR hand controllers, when the TRIGGER BUTTON is used on one of the G1000 rotaries/buttons (see above at 4.) then the SECONDARY or TERTIARY BUTTON do not work (have no effect) on ANY of the rotary/buttons.
This condition persists until the VR hand controller is reactivated by activity (after first being hidden by inactivity), now the secondary or tertiary button will work, unless/until the trigger is used again.

C. Cause:
With the VR hand controllers, when the TRIGGER BUTTON is ASSIGNED to function:
“VR - COCKPIT INTERACTION - RIGHT” or “VR - COCKPIT INTERACTION - LEFT”

D Result:
Trigger button usage PREVENTS any FOLLOWING secondary or tertiary button usage.

E. Temporary fix:
With the VR hand controllers, when the TRIGGER BUTTON is ASSIGNED to function:
“COCKPIT INTERACTION - PRIMARY”
When trigger is assigned and used as primary button, the issue does not appear and the controller is usable without loss of function, i.e. the function and operation is now more comparable to the default mouse buttons.

F. Test notes:

  1. The VR hand controller or the trigger button itself do not appear the problem here, it appears to be the functions “VR - COCKPIT INTERACTION - LEFT” and “VR…RIGHT” for any button it has been assigned to, when interacting with the G1000 rotaries/buttons (the topic title is a bit misleading in this regard, but for lack of good wording…)
  2. These functions appear to be the default assignment for VR hand controllers, which may be problematic for unaware users and the perceived default VR quality.
  3. This issue is not tested on other aircraft than described above at 3., but assumed is that it is reproducable for all G1000 cockpits.
  4. This issue is not tested on other combinations of instrument rotaries/buttons other than the G1000.

Provide Screenshot(s)/video(s) of the issue encountered:
Description suffices.

Detailed steps to reproduce the issue encountered:
Description suffices.

PC specs and/or peripheral set up if relevant:
Reverb G2 V1

Build Version # when you first started experiencing this issue:
Tested in SU10, but may not be the result of SU10 i.e. issue may be present since first VR implementation.


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

THANK YOU for posting this work-around. I had mapped a button to the Secondary interaction, but that didn’t work consistently. Re-mapping the triggers to Primary rather than the VR specific Right or Left interaction solves that issue. It must be a problem with the VR Right & Left actions disabling the Secondary function. I had previously read other people observe that mouse clicking onto the game again lets it work again, but your solution is better.

1 Like