SGT Coyle

TX6 button press will not reliably start voice attack listening. I have TX1, TX2, TX3, TX5, and TX6 mapped button presses. I use TARGET to map them to buttons that produce a respective DX button. TX6, mapped DX6, when pushed and held, will most times produce a "listening resumed" immediately followed by "listening suspended". Repeated pushes may result in a desired "listening resumed", but the listening indicator on the right indicates listening is suspended. Listening is definitely suspend when this happens. Sometimes I can get a listening response with repeated button presses, but the listening state is toggled. Any thoughts?

Lookin sweet

Gotta say, after a long break from the Harrier, I was pleasantly surprised to see so much progress in the Module and the Training content. Learning a lot. Thanks

Matthl, If you don't want the "Thrustmaster Combined Device" you could use TARGET for just the Joystick. You'd get the rotation you want and keep the programming to a minimum. It would require an editing of the target.tmh, but it's not difficult at all.

So, I made a profile to control CDU, MFD's(Left, Right, Center), and UFC's across multiple modules (A10C, Av8B, F/A18C so far). It's mostly just for the alpha numeric input fields, and some limited knee board functionality. How should I setup the command to work with VIACOM? Is there any best practices for VIACOM? Thanks.

Anyone know the travel limits of the stick?

Look at this

Pg 21 of the TARGET Script editor. I use it to great effect to operate the Auto Pilot in the Harrier. //Autopilot Engage/Diengage********** MapKey(&Throttle, APENG, TEMPO( Altitude_Hold_On_Off_Toggle, Automatic_Flight_Control_On_Off_Toggle));//

I think they have added this with a bunch of other encoders and switches that sow being worked on, on the bug tracker. mcmike, welcome to the club.

Supper Frog!

Awesome, Thanks. Decided to give Voice Attack a try again, with VR, and saw your new version of VAICOM . DL'ed the pro version, with CHATTER and AIRIO, last night and wrestled with the PTT setup. Figured it out and immediately started thinking of what can I get out of this. A lot is the answer. I will be jumping into the manual full bore this weekend. Thanks for your efforts and good hunting.

Can this be used to get the JTAC/AWACS to repeat last message? Ok, that was a dumb question. What I think I meant was, can "Crystal Palace" (AOCS) repeat JTAC/AWACS call? Also, can "Crystal Palace", give me my own aircraft location in Lat/Long, and Magnetic Variation of the theater?

So what is the price? and how to order?

I was looking the other day. Virtually none. See what I did there.:smilewink: I took a look with lasso. I setup OD to open when I start Oculus Tray Tool, and close when OTT is closed. OTT stops the Oculus Service that's needed for Dash to run. Otherwise Dash runs as long as the HMD is pluged in.

Yeah! Baby, yeah!

Yes, +1 on both. It's the little things that improve quality of life.

Just did the Navigation mission. Excellent. The information was organized and presented well. I now have a great understanding of the system and how to use it.

IDK if it's bug or just not implemented, but when I rearm to all flares, no chaff, I still have 60 chaff / 120 Flares showing in the ECM page. What's actually got loaded I'm not sure. Anyone else have this?

Increase my enjoyment? Yes! Make me a better pilot? No, there's no hope for me.

.tmc files are made in TARGET Script Editor, not the GUI.

Any movement on this OP?

Paste this into a new .tmc and save as whatever.tmc, and compile and run it. That will kill the lights. include "target.tmh" //program startup int main() { if(Init(&EventHandle)) return 1; // declare the event handler, return on error //add initialization code here // Init Lights ActKey(PULSE+KEYON+LED(&Throttle, LED_INTENSITY,0)); //set Throttle backlight power to middle // set Throttle backlight power to low //ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1)); //set LED 1 OFF //ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF //ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT+LED3)); //set LED 3 OFF //ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF //ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT+LED5)); //set LED 5 OFF } //event handler int EventHandle(int type, alias o, int x) { DefaultMapping(&o, x); //add event handling code here }

Excellent! just the ticket. Thanks

Thanks, thought it would be like that. No worries, it seems to be working. RightStuff, you thinking of the "Device Analyzer"? I see all the buttons in the analyzer, just not in Win10 controller test app. When I was trying to assign buttons in game settings, none of the buttons worked. I figured out that I needed to use the drop down menu for joystick buttons.

When I run this should I see 120 DX buttons in the windows game controller testing window? I only see the 32 as normal.