Recent Posts

41

Feature Suggestions / Re: Joystick Axis Support

« Last post by SemlerPDX on March 28, 2025, 12:50:03 PM »

Have you looked into device state conditions?  There are also joystick axis tokens, too, including position, rotation, acceleration, angular acceleration, angular velocity, etc. - check the VA Help Manual starting around page 191.   Might be able to get rid of Joy2Key right away if you build a conditional command which can watch your joystick axes for non-zero values....

42

Issues / No Key Email Received

« Last post by scottb613 on March 28, 2025, 12:23:10 PM »

Hi Folks,

Just a heads up - I purchased my VA2 key this AM - via your website. I still haven't received an email with a key.

I did receive a receipt via PayPal.

I don't need it - as I retrieved my key via your automated system.

Just a heads up you might have an issue with your licensing system. I checked my spam folder too.

Regards,
Scott

43

Feature Suggestions / Joystick Axis Support

« Last post by scottb613 on March 28, 2025, 07:17:09 AM »

Hi Folks,

First off CONGTATS - on getting v2 out the door. Just purchased - looking forward to testing when I get my key.
    

After all these years - you are certainly entitled to another ten spot.

Feature Request - - - Joystick Axis Support - - - so I can remove Joy2Key from my control program ensemble.

Regards,
Scott

44

Profile and Command Discussions / Re: Wildcards revisited

« Last post by MalcomR on March 27, 2025, 03:00:40 PM »

Okay.  I see now.  Thank you.

45

Profile and Command Discussions / Re: Wildcards revisited

« Last post by Pfeil on March 27, 2025, 02:13:36 PM »

The "wildcard phrase", is literally anything that is predefined. Doesn't matter whether that phrase uses dynamic sections or anything else.

"Altitude" is the predefined part of the recognized input, thus that is returned by "{CMD_WILDCARDKEY}". "4000" occurs after the predefined phrase, and as such it is returned by "{CMD_AFTER}".

46

Profile and Command Discussions / Re: Wildcards revisited

« Last post by MalcomR on March 27, 2025, 02:06:56 PM »

I saw those but they give me the portions before and after the wildcard * while the wildcardkey gave me the word altitude which is before the wildcard value of 4000 instead of the expected 4000. This is when I say Altitude 4000.

I did some more testing and found that the 4000 is actually in {CMD_AFTER} which is supposed to be the text after the wildcard phrase.  Based on the documentation I would have expected  {CMD_BEFORE} to contain Altitude and {CMD_AFTER} nothing since there is nothing after the wildcard. {CMD_WILDCARDKEY} should have the  wildcard phrase, 4000 since that is where the wildcard goes..  But maybe I'm not understanding what the manual is saying.
 
Attached is the output when I dump the Before and After and the command I'm experimenting with.

Yes, I agree that a sanity check is needed!

47

Profile and Command Discussions / Re: Wildcards revisited

« Last post by Pfeil on March 27, 2025, 01:40:37 PM »

There are tokens for that: "{CMD_BEFORE}", "{CMD_AFTER}", and "{CMD_WILDCARDKEY}".

Regardless, you'd likely want to run the output through the "{TXTNUM:}" token anyway just to make sure it's only the number.

48

Profile and Command Discussions / Wildcards revisited

« Last post by MalcomR on March 26, 2025, 02:10:48 PM »

I posted originally in this thread https://forum.voiceattack.com/smf/index.php?topic=4569.msg20793#msg20793 and got some helpful responses.  However, I'm still having issues trying to make this work.

My example is [Set;] Altitude [to;*] or [Set;] Altitude [to;] * where I want to say anything for the altitude.  The first form works fine and this is what is shown in the log (I'm using the inline script referenced in https://forum.voiceattack.com/smf/index.php?topic=3658.0). I said Altitude 4000 and this is in the log (see attachment).

Th command sees the altitude in place of the wildcard.  How do I access that wildcard value in the command? None of the CMDSEGMENTS 0-3 are set (that is the Wildcard n log entries).  The wildcard before and after actions give me what is before the wildcard or after but not the wildcard itself.

I really don't want to generate a command using something like [1000..45000] as that would generate a lot of commands and VA complains.

I suppose I could use the {CMD} and parse it to get the number from it.

Thanks.

Thanks.

49

Announcements and What's New / VoiceAttack beta version v2.1.5.1 has been released (standalone and Steam)

« Last post by Gary on March 25, 2025, 10:13:05 PM »

Howdy, folks!

The full release of VoiceAttack v2 has made this a very busy week!  This version contains a few updates and changes that naturally follow a big release o_O  Also, there are a few new tokens that were added by request that might help with some of those big numbers in your space sims :)

Welcome to springtime!


The beta can be downloaded here:  https://www.voiceattack.com/currentbeta

The zipped version of the beta is available here:  https://www.voiceattack.com/betazipped

Information about the Steam beta version can be found here:  https://www.voiceattack.com/getsteambeta

The rollback for this version is the full version: https://voiceattack.com/currentinstaller


As always, the release notes can be found here:  https://www.voiceattack.com/changesbeta

50

General Discussion / Re: Multiple callsign simple smart solution

« Last post by Polaris on March 25, 2025, 04:15:34 PM »

SemlerPDX,
Much obliged !
Fixed and working.

Just my own subjective opinion regarding rigidity of callsigns:
I mostly fly online and use very specific calls formation.
Built in them, as in any aviation calls and no matter if civil or other…your specific and precise callsign.
It’s as basic as holding a stick or a throttle.
You just don’t fly online without using the exact callsign assigned to you (in flight you can use your number but that’s it)…just like in the real world.
In my opinion.

One thing I do wish…to be able to use wildcards with a much better reliability.
Windows speech engine struggles with my accent and unless I give it precise calls it’s a hit and miss.

Cheers