I'm trying to get a number of macros set up on Voice Attack to be used with key presses. For example, pressing a key would type out "Do you need assistance?" and press enter.
This is done by setting up the "Recorder" when editing the command, including a set value of 0.01 pause for typing in each word, and just typing it out.
The method works great, except when I'm using FaceTrackNoIR and an IR clip setup. With head tracking activated using this function skews my "center" off to the side in a way that cannot be fixed. Using the recenter button does nothing, the new center is fixed. Using the text macro again only makes it worse.
I can't seem to find any settings in FaceTrackNoIR that might be causing this, and there is nothing in Voice Attack that could be. Since it only occurs when head tracking is active, I assume it must be a problem with FaceTrackNoIR.
The Voice Attack macro commands consist only of a sequence of letter and pause commands in sequential order. Nothing more.
Any suggestions on what might be causing this drift? Or any suggestions on an alternate way to set up macro text input that might bypass the problem altogether?
This is done by setting up the "Recorder" when editing the command, including a set value of 0.01 pause for typing in each word, and just typing it out.
The method works great, except when I'm using FaceTrackNoIR and an IR clip setup. With head tracking activated using this function skews my "center" off to the side in a way that cannot be fixed. Using the recenter button does nothing, the new center is fixed. Using the text macro again only makes it worse.
I can't seem to find any settings in FaceTrackNoIR that might be causing this, and there is nothing in Voice Attack that could be. Since it only occurs when head tracking is active, I assume it must be a problem with FaceTrackNoIR.
The Voice Attack macro commands consist only of a sequence of letter and pause commands in sequential order. Nothing more.
Any suggestions on what might be causing this drift? Or any suggestions on an alternate way to set up macro text input that might bypass the problem altogether?
