SGT Coyle

Yeah, I'm thinking of two separate .tmc files, or not. Really stuck for how to go about it, but one feature I'd like to have is a command that switches between Pilot and RIO, and also switches stick/controller functionality.

Yeah, I'm thinking of two separate .tmc files, or not. Really stuck for how to go about it, but one feature I'd like to have is a command that switches between Pilot and RIO, and also switches stick/controller functionality.

Looking for some advice on a strategy, for an F14 profile. Looking for how to best implement controls for Pilot and RIO in one profile. I don't like using the UMD functionality built into TARGET, but I'm open to suggestions.

Can you post your code? .tmc and a .ttm if you use a macro file.

Right Console. Not the RWR panel. The ACNIP Panel. There's a double encoder there labeled GND and AUX. The outer knob is for the Betty and Growler. Turn them both all the way up. Were you getting lock on symbology in the HUD?

I guess there's one in every crowd. Like a dog that eats poop.

Do you use TARGET? If so, GUI or Script Editor? If script, then make a Macro file for the module or modules you own. Then It's a simple matter of jiving the macro file to the DCS settings, and vise versa. I've never had any luck trying to reload a saved input file to an updated Beta/Release. By the way. What Module did you loose the inputs for?

Completely understandable. No sonar.

LOL!

I don't Like it. It's not a fix. But good work around.

I got the same issue, but haven't had time to investigate. Look forward to enlightenment.

Yes! Bump!

Resilient!

Lots of dead links on OP. Hope all is well. Looking forward to getting back to mission editing, and learning Moose.

Run this https://www.digitalcombatsimulator.com/en/files/3302470/ on TARGET Script Editor, NOT the GUI. It will just give you axis control as a virtual controller. Try it as a trouble shooting step. See if you get your axis back. If not. You're no worse off. If you do get the axis back, stop TARGET and see if their still working. Good luck

You must be bored to troll this far back in time. LOL!

I would delete it out of the Apps folder in VoiceAttack directory. Then reinstall from fresh DL.

What did you do? Share the wealth.

Use the device analyzer under the menu bar of the Script Editor. In it, you'll see the raw DX axis, buttons, and hats input. You don't need to have a script running. If your axis is FUBAR you will see it in the output.

All presses for buttons are press and hold. Only a few are buttons on my script are "pulse". The button works fine. Tested with Windows in controller settings, also tested with Pointy's Joystick Test. Must be VA setting. And there it is. "TX6 release" setting. Box for "execute on button release", not checked. Sorry to bother. Love this ViacomPro.

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.