SGT Coyle

Try unzipping to "Vulcan Forge" folder and putting folder in campaigns. Like this: DCS>Missions>Campaigns>En>Vulcan_Forge>(campaign files here)

Link that bad boy, will ya?

So I made my 2 macro files, but I get a compile error when I try to use a marco in the function. Compile [b]Error[/b]:Define stack full in F14B_Unified_Cockpit.tmc at line 94It works fine if I put a direct key command in like: MapKey(&Joystick[color=#ffffff],[/color]S1, [b]"5"[/b]);But the second I use a macro I get the error. MapKey(&Joystick[color=#ffffff],[/color]S1, [b]Recenter_VR_Headset[/b]);Edit: Further testing revealed that errors are reported when I use both the pilot and RIO .ttm's. If I use one or the other , but not both, the .tmc works fine. Looks like I'm just gonna have to go through them line by line. Any thoughts on what I should be looking for? Got it working just fine. It's just a matter of making sure there are no duplicate Macro defines.

Thanks, I'll look at this tonight. Drakos, Working on my Macro .ttm's. Eliminated most of the duplicate commands. I intend to use 2 macro files. Pilot(default) and RIO. All the pilot and duplicated commands go in Pilot.ttm, and only RIO specific commands go in RIO.ttm. Once that's done I can build my Mapping. I play mostly in VR so the printf and LED commands, in the example you gave me, are pretty much useless. I'm going to make those audio files for the pilot and RIO switch. That example is most definitely appreciated. Thanks.

Can you give an example? I'm feeling particularly dense at this time.

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.