Cougar profiles, non DX only
-
Nope u got it wrong. Landing issue was with no dx profile.
Sent from my SAMSUNG-SM-T818A using Tapatalk
Exactly. Shift b for brake would be a continuous command, so if you wanted to press G to raise the gear for a go around, you’d run into problems. DX removes all of this worry as it’s direct button mapping; no middle man of a joystick pretending to be a keyboard. Dunc’s profile in the docs folder will be what you need, and you can very easily add keystrokes on top of it for non BMS functions such as TIR etc.
-
How about when you have shift modifiers etc. on way the speedbrake switch. That shift key means that you cannot send out any other keystrokes whilst you’re actuating the speedbrake without undesired actions; simultaneous keystrokes are going to be constantly stepping on each other. Simply not a problem with dx mappings.
Blue Wolf explains it better, but if using keystrokes on your cougar is not a problem, then you’re not pressing enough keys at once.
+1
I had undesired command issues until I wrote my own DX file. Now its perfection.
-
Any chance you could post your tmj please
-
Any chance you could post your tmj please
If you are asking me. I don’t use Foxy. Pure DX key file only.
-
Exactly. Shift b for brake would be a continuous command, so if you wanted to press G to raise the gear for a go around, you’d run into problems. DX removes all of this worry as it’s direct button mapping; no middle man of a joystick pretending to be a keyboard. Dunc’s profile in the docs folder will be what you need, and you can very easily add keystrokes on top of it for non BMS functions such as TIR etc.
Yeap I’m on it this period of time.
I try to understand if I must use
Dunc_DX
or
Dunc_DX_ReplacementAs I understand it I must use Dunc_DX_Replacement cause it implements the latest keycommands.
Now I just added the commands for ICP only for Komurcu’s android app but missing many for the rest buttons and switches he has in the app.
Also try to re figure out how to map my current teamspeak and trackir commands.
but as I see it for trackir I might go back to default as it must have them already?
Tried Kolbe’s excel and got lost. This excel is wonderful but needs too much time to be sure what u r doing exactly and if it’s correct. 3 times starting from scratch reinventing the wheel all of them. -
Mower, Did you ever get a profile for your cougar? I just got a brand new Cougar ( my second one I had to buy). I want to try using one without using DX. could you send me one. If you did find one I’d like to try it. Send it to my inbox.
That would be truly appreciated. Thanks, Rhino
-
Same question please: anyone have a Cougar profile for 4.34 please?
-
If you must use a profile, use Dunc’s in the BMS inputs folder. IMHO his is the best realistic profile. I used it and modified it until I switched to DX, but I’m never going back. Don’t even have Foxy installed anymore. DX covers my Cougar stick and TUSBA with full shifted layer for both as well as my MFD’s, my switches and MFP’s all in one file.
-
Can I use shifted commands with S3 with a DX profile?
-
Can I use shifted commands with S3 with a DX profile?
Yessir.
#####################################################################
This is the SHIFTED (with holding Pinky/S3) layer.
Pressing PINKY/S3 + some button will result in a DX
number which is “original DX button number + 256”.
So e.g. the Uncage button - which is Win DX24 / BMS DX23
by default - will become BMS DX23+256 = DX279 here.
Shifted buttons that should do THE SAME as the unshifted ones
do NOT need to be mapped at all.
Shifted buttons that should do NOTHING at all (hence only work
as unshifted buttons) need to be mapped to “SimDoNothing”.
NOTE: for the DX shifting to work properly, you HAVE to make sure
that the Falcon BMS config file includes the following setting:
set g_nHotasPinkyShiftMagnitude 256
(this should be there by default, please just crosscheck)
#####################################################################
TG1 (Win DX1 = BMS DX0+256 = BMS DX256)
SimDoNothing 256 -1 -2 0 0x0 0
Pickle/S2 (Win DX2 = BMS DX1+256 = BMS DX257)
AFResetTrim 257 -1 -2 0 0x0 0
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX25)
SimHotasPinkyShift 258 -1 -2 0 0x0 -1
Paddle/S4 (…and so on…)
SimEject 259 -1 -2 0 0x0 0
MslStep/S1
SimDoNothing 260 -1 -2 0 0x0 0
TG2
SimDoNothing 261 -1 -2 0 0x0 0
TMS/H2
OTWSelect3DCockpitMode 262 -1 -2 0 0x0 0
OTWSelectF3PadlockModeAA 263 -1 -2 0 0x0 0
OTWStepNextPadlock 264 -1 -2 0 0x0 0
OTWSelectF3PadlockModeAG 265 -1 -2 0 0x0 0DMS/H3
FOVToggle 266 -1 -2 0 0x0 0
SimVisorToggle 267 -1 -2 0 0x0 0
ToggleNVGMode 268 -1 -2 0 0x0 0
RecenterTrackIR 269 -1 -2 0 0x0 0CMS/H4
SimEWSPGMInc 270 -1 -2 0 0x0 0
SimEWSProgInc 271 -1 -2 0 0x0 0
SimEWSPGMDec 272 -1 -2 0 0x0 0
SimEWSProgDec 273 -1 -2 0 0x0 0The TRIM hat/H1 has its own syntax.
(Please just believe me that this section is ok, a full explaination
is available in the “DX Shifting” docu).
We map TRIM for the SHIFTED layer here. There is no need to map
the UNSHIFTED stuff (POV change), because BMS will automatically
use POV for ALL unmapped/unused layers by default.
AFElevatorTrimUp 0 -1 -3 0 0x0 0
SimDoNothing 0 -1 -3 1 0x0 0
AFAileronTrimRight 0 -1 -3 2 0x0 0
SimDoNothing 0 -1 -3 3 0x0 0
AFElevatorTrimDown 0 -1 -3 4 0x0 0
SimDoNothing 0 -1 -3 5 0x0 0
AFAileronTrimLeft 0 -1 -3 6 0x0 0
SimDoNothing 0 -1 -3 7 0x0 0
OTWViewUp 2 -1 -3 0 0x0 0
SimDoNothing 2 -1 -3 1 0x0 0
OTWViewRight 2 -1 -3 2 0x0 0
SimDoNothing 2 -1 -3 3 0x0 0
OTWViewDown 2 -1 -3 4 0x0 0
SimDoNothing 2 -1 -3 5 0x0 0
OTWViewLeft 2 -1 -3 6 0x0 0
SimDoNothing 2 -1 -3 7 0x0 0###Note: I have POV on shifted layer and Trim on unshifted layer here