Cougar programming help please
-
Hi my brothers…
Looking to code the Cougar S3 button to be /o a DX button and when held /I to be shifted.
Anyone suggest the required code please?
-
Just check out Dunc_DX in your \Falcon BMS 4.33 U1\Docs\Key Files & Input\Device Setup Guides & Profiles\TM HOTAS Cougar folder.
Even if you don’t want to use Dunc_DX you can see how it’s set up to do what you want.
-
For 4.33.5 we should use dunc’s replacement files. Right?
Im fighting the same thing Mo. Like teamspeak and centering trackir etc.
Is the comms button assigned to the datalink commands? Or this has to be done also?
At the same time i also want to have and komurcu’s icp android app…
A living hell… [emoji38]Sent from my SAMSUNG-SM-T818A using Tapatalk
-
No I still some guidence on how to program the S3 button as follows:
momentary press acts as DX button
held acts as shiftI know it will involve a delay statement but my Cougar programming is very rusty.
Any code suggestions very much appreciated.
-
If I understand the Cougar manual, the following should do the job…
BTW S3 DX20 DLY (500) /P S3_LOCK /R S3_UNLOCK … or instead of the LOCK/UNLOCK, can I just say S3?
Where DX20 is an example of the DX button and the delay is half a second
-
Why do you want to complicate things? USE ALL_DIRECTX_BUTTONS is your friend.
Read pages 3-6 and 3-7 of Dunc’s Cougar DX Guide.pdf at the location I linked above and it should all make sense.
-
Well Darkman, you are correct in that that doc has very useful info. Cheers.
But here’s my question with use all DX Buttons: if the the S3 is so designated as DX3, how can it seen is shifted (/I)?
-
I ditched Foxy and TARGET etc. and just programmed my keyfile all DX. Much simpler and better than software.
All you need is:SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 1 “STICK: PINKY SWITCH (DX SHIFT)”
in unshifted layer:
Pinky/S3 (Win DX3 = BMS DX2)
SimHotasPinkyShift 2 -1 -2 0 0x0 -1
in shifted layer:
Pinky/S3 (Win DX3 = BMS DX2+256 = BMS DX25)
SimHotasPinkyShift 258 -1 -2 0 0x0 -1
Its just that simple and should work as you described that you wanted it to work. Even works with separate Cougar throttle TUSBA.
In Foxy, way back when, I just used.
BTN S2 SPC
-
Well Darkman, you are correct in that that doc has very useful info. Cheers.
But here’s my question with use all DX Buttons: if the the S3 is so designated as DX3, how can it seen is shifted (/I)?
I suggest you open the file and take a look; it’s commented in a very helpful way making it easy to understand and adapt. It opens in notepad/notepad++ too I think.
-
Is there a callback to drop stores (the emergency stores drop button on the left panel)?
Cant find such in the docs.
-
Remember that Dunc’s Cougar DX Guide that I referred you to, check out page 13
If you had just used that profile you would have been flying by now, but I’m sure you’re having fun relearning all the old Cougar stuff. Next thing you’ll be building a cockpit and then there will be no saving you :lol:
SimEmergencyJettison 274 -1 -2 0 0x0 0
-
Remember that Dunc’s Cougar DX Guide that I referred you to, check out page 13
SimEmergencyJettison 274 -1 -2 0 0x0 0Yep I read that and am now changing some of the DX Shifting maps…cheers brother for the answer!
-
Is there a callback for ICP Mark?
-
SimICPMark
SimEmergencyJettisonJust search full keyfile or Complete Callback List.
-
Is there a dx callback for TrackIRPause?
-
Not yet.
-
-
So heres a problem with DX mapping: I had a nice DX callback keyfile created.
I go into BMS and setup the Cougar MFDs with mapping, the file saves, afterwards it completely jumbled and wrecked the DX key file.
-
Always been like that. That’s why each keyfile starts with:
################################################################### ### 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! ### ###################################################################
-
You saved all your work on your nice keyfile though right? Because if you do anything to it in setup it erases all the wording in your DX file and can bugger it up. You should set up your MFD’s in the keyfile like everything else not in BMS UI setup. Don’t touch BMS UI setup for key mapping.