Jump to content

Recommended Posts

Posted (edited)

I've been going through the MAD AH-64 Campaign using a Pimax Crystal. Before the August 14 update (2.9.7.59074), I was able to use the Crystal's controller for the EUFD and keypad button presses. Those no longer work (button presses on the MFDs still work fine with the Pimax controller).

I can still adjust the brightness knobs. I can also affect the up/down EUFD switches on the left of the EUFD, just not the buttons on the right side of the EUFD. My fall back is to reach for the mouse for those key presses.

[Update] After more testing, it seems the controller inputs used to "press" buttons in the Apache are different than what they had been prior to the patch mentioned and I believe the previous one. In the Apache, I'm able to use the Pimax controller to "press" with 1) the trigger, 2) pressing forward on the stick and/or 3) pulling back on the stick.

For example:

  • The master arm/ground override buttons, I push forward on the Pimax controller stick.
  • For the MFD buttons, I can use the Pimax controller trigger
  • The left side toggle up/down buttons on the EUFD, I can use the controller trigger
  • The right side EUFD buttons and left keypad, I have to pull backwards on the controller stick (I used to be able to use just the Pimax trigger for these)

Very inconsistent implementation of the controller inputs. I've noticed a couple oddities like this in the F-4 as well (push forward on the Pimax controller stick to reset the master caution whereas the other buttons I can use the trigger.

Edited by instigatorxb
Posted an update after more fiddling
  • instigatorxb changed the title to VR controller button presses inconsistent on AH-64D EUFD and left keypad
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...