SGT Coyle

set off malware bytes and got quarantined.

Unplugged and reconnected Throttle. Got lights, shift, and toggle shift working. Uncommented RDRNRM/RDRDIS lines and got wierd behavior. Could only get RDRNRM to fire once. Had to restart profile and then again only once. RDRDIS did not work at all. Replaced with MapKeyRIOUMD(&Throttle,RDRNRM,...) and that line worked. Only once. Then removed IOUMD from line and works as advertised. Even put the line back to MapKey(&Throttle, RDRDIS,...). All works fine. I would say get rid of all the redundant IOUMD modifiers if their not needed in a particular line.

How do I switch an Axis (Friction Lever) from MapAxis to a KeyAxis and back? Looking to use the lever as flap axis and in shifted state use it as KeyAxis for operating the landing gear, hook, and kneel functions.

Weegie, Check weather your toggle shift is working. It will engage, but revert after a short time. And none of the LED commands are working.

Can't tell you how many times I've been certain its not the script, but if it's a connection issue, a continuity check with a multi-meter will tell the culprit. Post you script and get some second eyes on it before rolling out the soldering station.

dmonds, Can you post your script. I'm trying to work some thing similar out, but have hit a wall. A really ludicrously tall wall.

It seems the keyboard bindings are wrong and the Axis control is as well. On the keyboard we have four commands: Flaps_Down, Flaps_UP and Emergency_Flaps_Down, Emergency_Flaps_Up Each of these commands places the Flap handle in the emergency setting range respectively on the throttle quadrant. The Flap Axis range of motion will move the flap handle from one emergency setting to the other and all points in between. pg 29 Heatblur F-14A/B Tomcat Documentation, Release 1.0 The flap lever has a stepless range of motion between up and down and has two emergency positions, one emergency up and one emergency down. Both emergency positions have detents, the lever needs to be moved outboards to continue movement into these positions. Emergency up forces the flaps up, overriding the normal flap logic. Emergency down is non-functional. As I read that, I would expect the keybinds to move the flap handle to the limits of their up and down range as though using an axis, and for the Axis binding to move only to the limits of the up and down setting and not into the emergency stops.

Warranty action. Don't mess with replacing parts.

Are Flaps supposed to be Full Extend/Retract, or adjustable? I only get the Full Extend/Retract with the keyboard commands.

Just curious if this has progressed at all. I would be a +1 for it implementation. Maybe as part of the new carrier mod.

Nice Phrog My bad. It looked like a 46 on first glance. I'm looking to make my own throttle quadrant some day, but I'll probably use a 4 axis CNC Router. Good luck

For the Hornet: Controls Gear_Handle_UP, Launch_Bar_Control_Switch_EXTEND_RETRACT, Gear_Handle_DOWN, Arresting_Hook_Handle_Up, and Arresting_Hook_Handle_Down. Also set up Catapult_Hook_Up to be activated by the L/G Warning Silence Button when the Launch Bar is in the down position. .tmc code f/ F18: F18 function .tmh Mapping for Catapult_Hook_Up //Landing Gear Button MapKeyIO(&Throttle,LDGH, EXEC("Cat_Hookup();"), FCS_BIT_Switch);For the F5E-3: Controls Landing_Gear_Lever_LG_UP, Landing_Gear_Lever_LG_DOWN, and Drag_Chute_T_Handle_PULL_PUSH. .tmc code for F5E F5E Functions

You're not supposed to COMMENT IN THIS SECTION!!! Just re-report the bug. Send =Decoy= a PM about it.

Welcome to the jungle. Life will not be the same. I assume that the cable is "Hard Wired". That being the case, I would start by opening it up to see whats under the hood. That, I also assume, will destroy your warranty. If you go under the hood route, I would look at wiring a longer cable to controller and splicing it to the other, for starters. See if it works. Maybe look into a set of connectors that will allow you to do a more permanent job. I would also think about soldering skills. Most of these wire in the cables are very thin for wire nuts. But, actually I think you bought the wrong controller. The fact that you here tells me your ready to go a step further with a better setup. I don't know your financial situation, but maybe save up for it. This sort of thing can get expensive. Good luck. If you do go the under the hood route. Post photos. We might have use full suggestions.

Here: https://forums.eagle.ru/showthread.php?t=171098

If your using the TARGET Script Editor, the following code section works perfectly for Flaps: //Flap MapKey(&Throttle,FLAPU, PULSE + FLAP_Switch_Up); MapKey(&Throttle,FLAPM, PULSE + FLAP_Switch_HALF); MapKey(&Throttle,FLAPD, PULSE + FLAP_Switch_FULL); If your having issues with setting up a script I've attached a script template I use as a first step when setting up controls for a new mod. All the physical buttons are listed in the form of a "MapKey" command. Every line is commented out and missing a "keyboard" command, but once you provide that "keyboard" command, all that's necessary is for you to uncomment the line. The axis are already set to work. I all so provided a Macro file that that has all the default Keyboard commands in game. So setting up a MapKey command is no harder than cut and paste the maco into you MapKey command. I can't disagree stronger, that the GUI is easier than the Script Editor. With a template .tmc and a macro built with https://www.digitalcombatsimulator.com/en/files/1730806/, you can be up and flying in an hour, and have a better understanding of how things are setup. I gotta go to work. If you have issues using TARGET, post here or PM me. Good luck hope to count you as a TARGET user.

The targetdx128.tmh that I use is his. Version 1.0. A classic.

e22et, So the definesdx128.tmh you sent me was named definesdx128.tmh.txt. That won't work. lose the .txt off the end. Your .tmc is incomplete. you don't have any axis assignments, but the profile launches. So you don't need to do anything to your game files. If you have, fix it. Attached is a new .tmc, a macrofile, and the "targetdx128.tmh" that I use. I only mapped the "Electric Power Switch" to the "APU START" switch on the WH. If you want to use the .tnc, you'll have to map the rest. One thing I noticed in your script is the lack of "PULSE" commands. You should use "PULSE+" for all toggle type switches on the WH. That way you can flip a switch to a position and it will pulse the command instead of holding it. Another thing. I haven't messed with the Flamming Cliff planes much. There may be an issue with TM Virtual Controller. In the setting panel both Throttle and Stick controllers are present as well as the Virtual controller. Maybe someone else can shed light on that. I hope this helps. Su33.zip

The .zip didn't include your definesdx128.tmh file.

They'll do that until you articulate the axis'. Even then you may have a degree of shakiness around the center. That's easily remedied with addition of a small dead zone.

Post your .tmc file.

I tend to follow the simulated HOTAS layout as close as possible for starters. I guess it follows, what controllers are you using? I'm using the TMWH with Left and Right MFDs, TPR rudders, and F18 attachment.

Me too. This is awesome!

What VR headset you got? What version of game, Release or OB ?

You can paste these into an TARGET Editor script //Trigger MapKey(&JoystickF18,TG1, ); MapKey(&JoystickF18,TG2, ); //Buttons MapKey(&JoystickF18, S1, ); //Recce Button MapKey(&JoystickF18, S2, ); MapKey(&JoystickF18,S3, ); MapKey(&JoystickF18,S4, ); //VR |:| Black Rocker and Push MapKey(&JoystickF18,H3U, ); MapKey(&JoystickF18,H3D, ); MapKey(&JoystickF18,H3P, ); //SSS :: Sensor Select Switch MapKey(&JoystickF18,H2U, ); MapKey(&JoystickF18,H2D, ); MapKey(&JoystickF18,H2R, ); MapKey(&JoystickF18,H2L, ); MapKey(&JoystickF18,H2P, ); //WSS = Weapon Select Switch MapKey(&JoystickF18,H4U, ); MapKey(&JoystickF18,H4D, ); MapKey(&JoystickF18,H4R, ); MapKey(&JoystickF18,H4L, ); MapKey(&JoystickF18,H4P, ); //Trim MapKeyIO(&JoystickF18,H1U, ); MapKeyIO(&JoystickF18,H1D, ); MapKeyIO(&JoystickF18,H1R, ); MapKeyIO(&JoystickF18,H1L, );