help mapping keyboard to UFC and CDU

[cichlidfan]

How is a modifier not an option for your TIR keys? Mine are set to Backspace, Ctrl + Backspace and Shift + Backspace for most things and I have Alt + Space used in at least one profile as well.

[Fakum]

[ATTACH]57795[/ATTACH]

 

well,,, when I go to change the current assignment, it will only accept 1 key stroke,,, and I dont see anywhere in any menu to apply any modifier settings?

[pixelpilot]

Fakum, i know joystick buttons can be at a premium and they are all needed for flight/combat commands but is there not one spare you can map to TIR? I tend to centre my quite a lot so find it handy on my stick (i use same button in every game) that said i just checked and am able to map modifiers, shift cntrl and alt all worked, although that is in TIR 4 software.

[cichlidfan]

[ATTACH]57795[/ATTACH]

 

well,,, when I go to change the current assignment, it will only accept 1 key stroke,,, and I dont see anywhere in any menu to apply any modifier settings?

 

My screen looks just like that, I just hit two keys at the same time (i.e. LeftAlt and Spacebar) and it takes it. Although, if memory serves, TIR does not know the difference between the left and right keys, for Shift, Control and Alt.

[pixelpilot]

going back to what shagrat said. given that the CDU and UFC keys are mostly already mappend to lctrl+lwindows and lshift+lctrl respectively, if you have a programmable joystick that can be made to latch a button and return key presses you could have a data entry mode which is toggled on and off with a button on your joystick, this is definatly possible with the SSt software on the x52, you just have to be carefull thet no other control (slider set for bands and returning speedbrake key commands for example) is returning any keystroke because if you go into data enty mode and they are the cdu will fill up with undesired inputs. Sorry for the longwinded reply by the way may have just confused matters:)

[Fakum]

Thanks for the feedback,,, I did manage to get a modifier attached,, initially, I was trying LWin but that simply was not working,,, I did manage to get either a shift/alt or Ctrl,,, I just had to do it 1st instead of 2nd,, and as mentioned,,, it does not know the difference between left and right,,, so I dont know yet if that will be an issue in the Foxy syntax yet? Thanks for the guidance

[Fish]

.............I have a problem with my TrackIR v5. My hot keys for centering and pausing were "C" & "P",, I have no single keys available ....................

 

I presume that you have an analog throttle, so what about num- and num+ :smilewink:

[Paco]

I have my CDU letter and number keys mapped to the keyboard and x52. When I depress and hold my pinkie switch it acts as a modifier, that in combination with my keyboard allows me to type into my CDU. Works great.

[Fakum]

Thanks Fish,, yeah,, I think there are a few keys that can be freed up,,, as I do have an analog throttle,,,, I also noticed the "],[" keys seem to be unbound as well.

 

Thanks Paco,, I was attempting to be able to type without holding onto any buttons on the controls,, I have tried that but noticed I had a certain level of incompetence to which like I would fly the palne into the ground while looking at my keyboard,, hahaha,,,, anyway,, I have succeded and just have some tweeking to do,,,, thanks for the suggestion

[RedX]

One additional tip:

 

I've found it extremely convenient to map the UFC to a separate USB keypad. Cost about 30 euros.

[Fakum]

yeah, well,,, I have so many Cougar programming problems now, I will resrt back to my original profile so Im not struggling with the snap view loss I have not resolved and look for another alternative. this USB keypad you speak of, can you elaborate,, anybody? point me to a relative thread or something,,, thanks

[Fish]

yeah, well,,, I have so many Cougar programming problems now, I will resrt back to my original profile so Im not struggling with the snap view loss I have not resolved and look for another alternative. this USB keypad you speak of, can you elaborate,, anybody? point me to a relative thread or something,,, thanks

 

Here's the keyboard i use. Sits nicely in between stick and throttle

 

http://www.amazon.co.uk/Keysonic-Wireless-Keyboard-Integrated-Frequency/dp/B000L10Y5E/ref=sr_1_2?ie=UTF8&qid=1319664755&sr=8-2

 

When i'm finished flying (virtually!), i revert back to my G15

 

My rig is almost the same as yours, and I got a pretty solid profile for cougar/tir/Ch pedals. You can download it from the VAC thread. PM me if you need support for it, or help with cougar.

Edited October 26, 2011 by Fish

[Fakum]

Thanks Fish,,, Im trying to figure out the concept here? You have your every day keyboard plugged in while your flying, AND you have this one as a wireless running at the same time? You then can type in the letter "a" all by itself from the wireless keyboard and it is entered in the scratch pad?

Side note,,, yeah I could use help with the Cougar programming, I assume you havnt seen the thread that I posted this in,,, but heres my question regarding that,, if you have any incite on this, please respond at :

http://forums.eagle.ru/showthread.php?p=1314216#post1314216

Question =

Let me try to simplify my own question here, because im still working on resolving this.

In my Thrustmaster Cougar, Foxy programming, I have the following joystick file:

Rem H2

 

BTN H2U/I Cockpitpanelviewtoggle

/O/H HotasTMSUp

BTN H2D/I ViewDownslow

/O/H HotasTMSDown

BTN H2L/I ViewDownLeftslow

/O/H HotasTMSLeft

BTN H2R/I ViewDownRightslow

/O/H HotasTMSRight

I understand this completely, what I don’t understand is that when I do :

BTN H2U/I Cockpitpanelviewtoggle

 

With this action, I can now use snap views (which is great), the above stated “IN functions no longer function as stated e.g:

 

BTN H2R/I ViewDownRightslow

 

Is now a snap view function, and does not function as stated above.

 

The toggling of the :

 

BTN H2U/I Cockpitpanelviewtoggle

 

Somehow now utilizes this macro instead:

 

 

SnapView0 = USB(DE3 D62 U62 UE3)

SnapView1 = USB(DE3 D59 U59 UE3)

SnapView2 = USB(DE3 D5A U5A UE3)

SnapView3 = USB(DE3 D5B U5B UE3)

SnapView4 = USB(DE3 D5C U5C UE3)

SnapView5 = USB(DE3 D5D U5D UE3)

SnapView6 = USB(DE3 D5E U5E UE3)

SnapView7 = USB(DE3 D5F U5F UE3)

SnapView8 = USB(DE3 D60 U60 UE3)

SnapView9 = USB(DE3 D61 U61 UE3)

 

I don’t see how this macro is “turned on and off” if you will