TMJ help please
-
What’s also odd if I load a straight dx profile the gun fires on 2nd detent fine…the problem for me is a straight dx ignores all of the amazing programmability of the Cougar
As said above, 2nd detent fires gun not first. And no, straight dx does Not render foxy programming useless. Do you need to worry about programming as much with dx? No, but it’s still there if you need it.
-
I think what I am going to do is abandon keystroke mapping and use the BMS DX and DX Shifting instead. Will advise results. Cheers.
This is what I do so I can tell you there is at least one way to make it work And yes, I use shift layers to map at least two things to practically every HOTAS switch throw. Kolbe’s excellent work on the keyfile editor Excel file is highly recommended by the way – makes doing all this a snap. About the only edge case where you really need to think hard and do a little manual editing is if you want to use the facility to have different callbacks invoked for press and release DX button transitions…but you probably don’t need that for HOTAS things (now an ICP with a (on)-off-on setup for the DRIFT/CO switch on the other hand… ;)).
-
I think what I am going to do is abandon keystroke mapping and use the BMS DX and DX Shifting instead. Will advise results. Cheers.
Now you are talking! I highly recommend a realistic DX stick and throttle (looks like that is what you were going for anyway) and use the shift layer for stuff that is sim related ie. visor, zoom view, eject etc or anything fancy/unrealistic you want. DX has all the realistic button press timings and functionality already programmed.
-
So now Im a little confused, I read the manual for this app but have a question…
If I make changes here to the callback assignments, how do I save it as a new keyfile?
-
Take a look at the “Output” tab – there are directions there. Short version is that I use one of the default key files as a starting base and then paste the lines from the output tab that I want making sure to remove all the DX binding lines that are in the default file (or paste over them to replace them in effect).
-
Output tab is blank. I imported the key file in the Import Tab but have no idea how to get that into the TM Cougar Tab to alter the callbacks etc and then send that info to the output tab.
Im a relatively smart fella but I find the editor confusing.
Im just gonna modify my keyfile in notepad++, at least I know what Im doing there.
-
You’re going to need to be a smart and careful fellow to do it by hand with no mistakes
So far as I know the only thing you need to do to go from blank output tab to populated content is pick the keyboard locale on the Keystrokes Editor tab.
See the note on the Read Me tab – although I grant you it doesn’t really say “do this or you won’t see anything in output”
Change the locale (Keystroke Editor tab) BEFORE you assign keys.
Big fan of notepad++ here too though…that’s what I use to open the raw .key files when I need to do that.
-
Why don’t you just write your own key file. Start with Duncs and change it to how you like it. If I can do it, it is extremely easy.
I just copy and paste all the callbacks at the top like this:###################################################################
IF YOU SAVE THE KEYFILE IN THE BMS SETUP UI, YOU WILL LOOSE
ALL COMMENTS AND THE ORDER OF THIS FILE! SO ALWAYS KEEP A
BACKUP OF THIS FILE FOR FUTURE REFERENCE!
###################################################################
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “BMS - Full”
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “1. UI & 3RD PARTY SOFTWARE”
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======== 1.01 UI FUNCTIONS ========”
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 “REM: Hardcoded (not changeable)”
SimDoNothing -1 0 0x3B 0 0 1 -0 “UI: IVC Broadcast (Global Comms to 2D & 3D)”
SimDoNothing -1 0 0x3C 0 0 1 -0 “UI: IVC Local (Comms only to 2D)”
SimDoNothing -1 0 0x1 0 0 0 -0 “UI: Exit Sim - Leave Menu - Abort”
SimDoNothing -1 0 0xB7 0 0 0 -0 “UI: Screenshot (See also section 6.06)”
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======== 1.02 3RD PARTY SOFTWARE ========”
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 “REM: This is just for reference. See manual.”
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 “REM: Assignments can’t be changed here.”
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -0 “REM: Set keys in 3rd Party Softw. not here!”
SimDoNothing -1 0 0x41 0 0 1 -0 “3RD: TrackIR Precision”
SimDoNothing -1 0 0x42 0 0 1 -0 “3RD: TrackIR Profile”
SimDoNothing -1 0 0x43 0 0 1 -0 “3RD: TrackIR Pause”
SimDoNothing -1 0 0x58 0 0 1 -0 “3RD: TrackIR Recenter (See also 6.06)”
SimDoNothing -1 0 0x46 0 0 1 -0 “3RD: Teamspeak PTT”
SimDoNothing -1 0 0x37 0 0 1 -0 “3RD: Teamspeak Broadcast”
SimDoNothing -1 0 0x37 1 0 1 -0 “3RD: Teamspeak Toggle Mike On/Off”
SimDoNothing -1 0 0x37 2 0 1 -0 “3RD: Teamspeak Toggle Speaker On/Off”
SimDoNothing -1 0 0X42 0 0 1 -0 “3RD: VAC PTT”
SimDoNothing -1 0 0x43 0 0 1 -0 “3RD: FRAPS Video Capture”
SimDoNothing -1 0 0x44 0 0 1 -0 “3RD: FRAPS Screen Capture”
SimDoNothing -1 0 0x57 0 0 1 -0 “3RD: FRAPS Benchmarking”
SimDoNothing -1 0 0x58 0 0 1 -0 “3RD: FRAPS Overlay”
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “2. LEFT CONSOLE”
#===================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======== 2.01 TEST PANEL ========”
SimOverHeat 312 0 0x3B 1 0 0 1 “TEST: FIRE & OHEAT DETECT Button - Hold”
SimOBOGSBit 115 0 0x3C 1 0 0 1 “TEST: OXY QTY Switch - Hold”
SimMalIndLights 312 0 0x3D 1 0 0 1 “TEST: MAL & IND LTS Button - Hold”
SimMalIndLightsOFF 313 0 0XFFFFFFFF 0 0 0 1 “TEST: MAL & IND LTS Button - Release”
SimProbeHeatMoveUp 115 0 0x3E 1 0 0 1 “TEST: PROBE HEAT Switch - Step Up”
SimProbeHeatMoveDown 115 0 0x3F 1 0 0 1 “TEST: PROBE HEAT Switch - Step Down”
SimProbeHeatOn 115 0 0XFFFFFFFF 0 0 0 1 “TEST: PROBE HEAT Switch - ON”
SimProbeHeatOff 115 0 0XFFFFFFFF 0 0 0 1 “TEST: PROBE HEAT Switch - OFF”
SimProbeHeatTest 115 0 0XFFFFFFFF 0 0 0 1 “TEST: PROBE HEAT Switch - TEST”
SimEpuGenTest 115 0 0x40 1 0 0 1 “TEST: EPU/GEN Switch - Hold”
SimFlcsPowerTest 310 0 0x41 1 0 0 1 “TEST: FLCS PWR TEST Switch - Hold”Then program the stick like this:
#################################################################
Full real TM HOTAS Couger DX button mapping,
this is the UNSHIFTED (without holding Pinky/S3) layer.
Notes:
Windows counts the buttons from DX 1 to 32,
BMS counts the buttons from DX 0 to 31.
For the DX to work properly, you HAVE to make sure that
the Falcon BMS config file includes the following setting:
set g_bHotasDgftSelfCancel 1
(this is set to 0 by default, so please change it)
#################################################################
The 1st number after the function name is the DX button number,
the rest of the line is always the same and irrelevant for us.
TG1 (Win DX1 = BMS DX0)
SimTriggerFirstDetent 0 -1 -2 0 0x0 0
Pickle/S2 (Win DX2 = BMS DX1)
SimPickle 1 -1 -2 0 0x0 0
Pinky/S3 (Win DX3 = BMS DX2)
SimHotasPinkyShift 2 -1 -2 0 0x0 -1
Paddle/S4 (…and so on…)
SimAPOverride 3 -1 -2 0 0x0 0
MslStep/S1
SimMissileStep 4 -1 -2 0 0x0 0
TG2
SimTriggerSecondDetent 5 -1 -2 0 0x0 0
TMS/H2
SimTMSUp 6 -1 -2 0 0x0 0
SimTMSRight 7 -1 -2 0 0x0 0
SimTMSDown 8 -1 -2 0 0x0 0
SimTMSLeft 9 -1 -2 0 0x0 0DMS/H3
SimDMSUp 10 -1 -2 0 0x0 0
SimDMSRight 11 -1 -2 0 0x0 0
SimDMSDown 12 -1 -2 0 0x0 0
SimDMSLeft 13 -1 -2 0 0x0 0CMS/H4
SimCMSUp 14 -1 -2 0 0x0 0
SimCMSRight 15 -1 -2 0 0x0 0
SimCMSDown 16 -1 -2 0 0x0 0
SimCMSLeft 17 -1 -2 0 0x0 0 -
Why don’t you just write your own key file. Start with Duncs and change it to how you like it.
Yeah thats what Im doing, adding Shifting ones too.
I would have preferred key stroke mapping in Foxy but I couldnt get the trigger detents to work.
-
Yeah thats what Im doing, adding Shifting ones too.
I would have preferred key stroke mapping in Foxy but I couldn’t get the trigger detents to work.
Oh I saw Keyfile editor. I thought you were using that. I found it easier just to type mine (over 240 buttons) manually line for line directly in the keyfile than monkey with Keyfile Editor.