frustrated disabled alpha tester

Hi guys, I've got a problem with the menu scrolls with VA and I don't know if it's a bug or stupidity on my part.

The menus work fine with VA except in the station when I'm about to land. I've got a voice command that turns on the ship lights and deploys the landing gear, which happens no problem. However, once activated, the horizontal thrusters stop working. This makes lining up a little more tricky.

Should I send a ticket or am I doing something wrong? :S

Does this only happen on landing or in open space as well?
Do the other thrusters work?

My first thought is that you might not actually be resetting the focus to the HUD, even though you are looking at it. The script I use to lower landing gear that I posted earlier (hmm, note to self: add turning on the lights ;) ) does not have this problem. If you are exiting the VoiceAttack sequence with a "2" keypress to revert to the HUD, try using a "3" to close the side panel instead. It will also return you to the HUD.

Lowering the landing gear and turning on lights manually does not SNAFU the thrusters normally, so I don't see why a VoiceAttack sequence should do so.

If you can post your VA command string I'll try to replicate it.

If this is a genuine glitch then submitting a ticket might not achieve much, as VA is a third party app - however if the ramifications were more widespread then FD would certainly want to know about it.
 
Last edited:
Thank you Hellhawk, below is the string.

Press 3 key and hold for 0.1 seconds and release
Pause 0.3 seconds
Press Q key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press S key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press S key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press S key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press Space key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press S key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press Space key and hold for 0.1 seconds and release
Pause 0.1 seconds
Press E key and hold for 0.1 seconds and release
Say, 'Landing assembly'

It's only the horizontal thrusters that don't work. Everything else is fine. If I give the command again (retract) and then manually lower the gear, there is no problem.
I'm using trackIR and have to look at the panel in order to have the spoken command run. I simply look forward again when the command has run.

It works fine in open space.
 
I'm still at work but I'll be home in about an hour - I'll try replicating this then and let you know how I get on (assuming I can get a landing pad that isn't constantly revoked by that fickle traffic controller :) ).

Weird that it works fine in open space.

TrackIR can add a layer of glitchyness to this whole process.
 
Last edited:
Thank you Hellhawk, below is the string.

It's only the horizontal thrusters that don't work. Everything else is fine. If I give the command again (retract) and then manually lower the gear, there is no problem.
I'm using trackIR and have to look at the panel in order to have the spoken command run. I simply look forward again when the command has run.

It works fine in open space.

OK, I replicated your VA string and encountered the same problem, except in my case all thrusters were affected - actually I suspect all keybinds were affected, but I didn't try every possibility.

You should be able to fix this by doing one of 2 things.

Either:

* Remove the first 2 lines (ie "3" to open the panel, and "Pause")

or

* Add an extra "Press 3 and wait for 0.1 seconds" as the second last line.

I think the problem is with using TrackIR and VA together to control the side panels. Normally, without TrackIR, a command of "3" is needed to change the POV to the panel (either manually or using VA), and again later to change back to the HUD. However TrackIR removes the need for this as it invokes the side panels automatically when you look within a certain range of the cockpit overlay, and dismisses it again when you look away. Effectively, TRACKIR integration is issuing a "3" keypress whenever it passes the boundary of the sidepanel.

The problem is that if you have a "3" in the script for VA when using TrackIR it is redundant, but still seems to have some sort of weird residual effect. It sort of "half locks" the panel POV as far as keybindings are concerned. The reason you could use the thrusters after issuing the command a second time to retract the landing gear was simply that the side panel interface had registered a second "3" command and closed its focus for command entry.

So, either removing the initial "3" command, or else inserting a second one at the end, should fix the problem - it worked for me and I was able to land successfully 3 times in succession and use the lateral thrusters with no problem.

NOTE: I'd recommend leaving the initial "3" command and adding a second one at the end. This is completely redundant, but it means if you are not using TrackIR at any time your VoiceAttack command will still work properly.

I hope that is of some help.
 
Last edited:
Sincere thanks Hellhawk! I'll give it a go as soon as possible.
I can't rep you due to the spread factor but have some virtual rep instead. :)


Edit: IT WORKS! No problems at all. I deleted the 3command and just look to the right now instead.
 
Last edited:
Anyone proficient with the VoiceAttack software can help me? As a disabled user, and a lazy b*stard, I have found it helps me immensely. But I cannot, for the life of me, get it to simulate Alt+TAB/Task switching.

I bought this piece of software, because quite frankly, its awesome.

Any help would be appreciated.
 
Anyone proficient with the VoiceAttack software can help me? As a disabled user, and a lazy b*stard, I have found it helps me immensely. But I cannot, for the life of me, get it to simulate Alt+TAB/Task switching.

I bought this piece of software, because quite frankly, its awesome.

Any help would be appreciated.

You need a combination of two VoiceAttack commands.

1) Make a new command
2) Call it "Task" (or whatever else you like)
3) Click the Key Press button to open the Add a Keypress window
4) Click the "Press Key" button and hit TAB
5) Click the "Left Alt" button
6) Select the radio button "Press Key(s)"
7) Select the radio button "Standard"

This completes the command to open the task select bar. It should just contain the single command "Press down Left Alt + Tab keys"

When you issue the command "Task" the task switching bar will appear briefly and then switch to the current foreground application. Say "Task" again and the next application in sequence will appear. Repeat the command to step through the open applications.

However - you must have a second VoiceAttack command to stop the first one, otherwise the "Task" command will keep the ALT & TAB keys pressed down and not hand you over to the foreground application.

1) Make a new command exactly the same way as above but call it "Select"
2) Instead of selecting the radio button "Press key(s)", select the button "Release key(s)".

When you issue this command it terminates the original "Task" command and leaves you with the selected foreground application open.

There are other ways to do it, but this is the simplest one I can think of. It would actually be neater to implement 3 commands - one to hold down the ALT key until a release command is issued, one to hit the TAB key to step through the task list, and a third to select the required task and release the ALT key. Repeating the ALT + TAB command when it is already running in order to step as I've detailed above is either kludgy or elegant, depending on how you look at it :p.

Hope that helps
 
Last edited:
I didn't see it mentioned but I am tired. I use VAC from DW. It controls my panels, and the largest command is when getting ready for landing. I tell it "prepare for landing" and it opens my Systems Panel, then goes back a panel and down to engage my landing gear, closes the panel, and opens the target panel and moves to contact with the one command.
 
I've just tried this - I get inconsistent results. Tried with a command that repeats an E keypress 4 times when I'm focused on that right panel.

Sometimes it goes all the way across others it only jumps one or two panels.

Try going back a panel rather than going forward 4.
 
Back
Top Bottom