SGT Coyle

Put this little didy in your TARGET Script and you too can have a gear handle on the little grey lever. KeyAxis(&Throttle, THR_FC, [color=#ffffff]0[/color], AXMAP2( LIST(0,30,70,100), Gear_up, 0, Gear_Down)); But, asking Heatblur to go to the trouble to assign an axis to a binary switch, that is not something I can get behind.

What's stopping you? It's either up or down. If it's not down then up. If it's not up it's down. There is no halfway. That would be like being a little bit pregnant.

Awesome! Just tried it and wow.

Excelent, thank you. How about an F18 Grip version?

Are there instructions on how to use this?

I have no idea. I would think that most if not all folks in here are using the Script Editor, not the GUI. But, you might have a corrupted install. Maybe uninstall/reinstall GUI and try again.

Did you use Windows to calibrate? If not DON'T. Never heard of it solving problems. Probably remove devices (Throttle and Stick) and reinstall from scratch. Remember to reboot after software/driver install. Good luck.

YFKM!! That's awesome! LMAO! I'm trying that right now!

ataribaby, Didn't mean to imply any malfeasance. Just letting you know. I really didn't have any concerns, but can't be to careful. Thanks for the effort. I look forward to trying this.

slickdevel, In that thread I failed to mention that you can map any controller button to a ui layer binding. You don't need to use TARGET.

Probably not. I'd think they'd make an announcement if it were. Probably just busy with real world stuff.

dmonds, Great find. I've used KeyAxis for this sort of thing, but forgot about IOUMD feature it offers. Thanks for that. My question was more fore a way to have a traditional axis behavior assigned to say Flaps axis, and via flags or function call, change that traditional axis to the KeyAxis functionality. This is an example (non functional) of a .tmc that Drakos helped me out with for the F14. There are probably many things wrong with it at this stage, but I thought it might illustrate the problem. There are 2 modes of the script: Mode1 = Pilot settings Mode 2= RIO settings Modes are switched via the Left Throttle Button. In the Pilot settings I want to have the landing gear, hook and kneel operations on the Friction Lever as KeyAxis, and also the Flap axis that is not available via keyboard binding (there is Flap_UP and Flap_Down, but those aren't working as axis control, just full up and full down). So my desire is to move from KeyAxis to MapAxis control on the fly. ...And of course I'd like to do the same sort of thing for the RIO settings. I hope that makes sense. Any help or insights would be appreciated.

What about "UI Layer" in game control settings? There are bindings for scroll up and down.

Give it time...

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