Author Topic: Pre-Release Direct X keypress option missing?  (Read 3550 times)

HighwaymanEd

  • Newbie
  • *
  • Posts: 16
Pre-Release Direct X keypress option missing?
« on: October 17, 2016, 12:34:15 AM »
Hey Gary.

After publishing up that DCS UH-1H profile, I found that the option of setting standard or Direct X mode key presses is missing in 1.5.12.24. Is this deliberate?

« Last Edit: October 17, 2016, 12:38:05 AM by HighwaymanEd »

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4782
  • RTFM
Re: Pre-Release Direct X keypress option missing?
« Reply #1 on: October 17, 2016, 03:00:31 AM »
Yes.

Quote from: http://www.voiceattack.com/betachanges
v1.5.12.7

   - Design changes
   
     -  Standard and DirectX mode have been removed.  There is no longer
        a need to choose a mode.  This was found on the key press, key recorder
        and quick input screens.  You will need to use the key press screen's
        'key chooser' feature to select any keys that are not available to you
        by simply typing them on your keyboard (such as, 'numpad enter' for games
        and some media keys).

Are you having issues with an application not responding to keypresses?

HighwaymanEd

  • Newbie
  • *
  • Posts: 16
Re: Pre-Release Direct X keypress option missing?
« Reply #2 on: October 17, 2016, 03:50:12 AM »
Yes and no. :)

I've built out a profile which I started in version .17 and finished in .24 and it works find for me, however I've exported this profile which I intend to sell for a couple of Dollars and the feedback from a couple of users has been that for the latest standard release version of VoiceAttack it doesn't work for them unless they change the mode to DirectX for the key press.

I'll assume that when the release version gets its next upgrade they will have feature parity and it will no longer be an issue.

Thanks for the reply!

Pfeil

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4782
  • RTFM
Re: Pre-Release Direct X keypress option missing?
« Reply #3 on: October 17, 2016, 10:44:56 AM »
I'll assume that when the release version gets its next upgrade they will have feature parity and it will no longer be an issue.

It will. Gary's aiming for the beginning of November for the next stable release.