BMS Key File Help
-
@oldtommyboy
If you just need a static view for a few moments to get things squared away, you are better off using your hats to map 2d and 3d views. Its exactly the same pit, whereby 2d is pannable (snapview) with hat (which can also double -shifted- as trim) and 3d pannable with tir. No need to pause TIR at all. -
Thanks guys,I’m going to try something I thought about last night if this dont work,then I will resort to sst programing. Everything else good though. I wonder if other people have slight problems with rotaries and mouse wheel on throttle or if this is strickly a saitek problem also.
Killer- yep,i know about switching to 2d also,that was the only thing I hated doing in free falcon was switching back and forth between views.
Also while watching training vids,I wondered why he never pauses trackir when turning his head to look at his paperwork,now I know.but it does work fine with the keyboard.
I wonder if I delete reload ( the whole line ) and replace it with pause,if that simply will work,scince I’m messing around,guess I’ll find out.edit: nope didnt work,went looking through all old callbacks but couldnt find one for pausetrackir, oh well,back to flying. No big deal,tried for 4 days to get this,enough is enough unless some body could give me a callback to add to my keyfile cause nothing I did works.:uham:
-
Hmm tommyboy, you say that it works from the keyboard. Can’t you just program that key to the saitek ?
-
I was trying that with all the directx files,couldnt get it to work,if I was using sst I could but couldnt do it with the set up I want. I had it programed in ff5 for years but I do like the directx way better. I was trying to get it so it would show up in the game ui but couldnt get it to work,even creating a new key. No biggy. Thanks anyway.
-
I’ve tried the Kolbe file and cannot find out for the life of me how to cycle steerpoints :rolleyes: Any help from my fellow falconeers? I’m using the v14_full.key btw.
Happy Holidays,
Uwe
-
I’ve tried the Kolbe file and cannot find out for the life of me how to cycle steerpoints :rolleyes: Any help from my fellow falconeers? I’m using the v14_full.key btw.
Happy Holidays,
Uwe
Numpad + and Numpad -
SimICPPrevious -1 0 0X4A 0 0 0 1 “ICP: PREVIOUS - Push”
SimICPNext -1 0 0X4E 0 0 0 1 “ICP: NEXT - Push” -
Numpad + and Numpad -
Thanks Killer, I’d been checking the key file for “steerpoint” or “waypt”…
Uwe
-
Here’s one more question… how about ACMI? I’ve searched the keyfile for references, but haven’t found a way to turn ACMI recording on.
never mind, the “f” key works, just had to turn on the message in the cfg file … sorry.
Cheers, Uwe
-
Hi,
just changed the link in post #1. The old link was broken.
Thanks to Pilgrim for his advice.Regards
Kolbe
-
Here’s one more question… how about ACMI? I’ve searched the keyfile for references, but haven’t found a way to turn ACMI recording on.never mind, the “f” key works, just had to turn on the message in the cfg file … sorry. Cheers, Uwe
Kolbe,
Thanks in advance, but the link is down again.
Regards,
-
I’ve uploaded my version of the keyfile (about four weeks old or so) to my Dropbox folder:
http://dl.dropbox.com/u/1983539/BMS-keyfile.zip
Feel free to grab it from there.Cheers, Uwe
PS: Of course this is Kolbe’s Keyfile, the “my” was referring to “my downloaded copy”
-
-
Here’s one more question… how about ACMI? I’ve searched the keyfile for references, but haven’t found a way to turn ACMI recording on.
never mind, the “f” key works, just had to turn on the message in the cfg file … sorry.
Cheers, Uwe
Alternatively, disable the “message” in the cfg file and instead rely on the AVTR switch position and lamp.
Using the SimAVTRToggle toggle callback will not move the switch or turn on the lamp, however if you use any of the SimAVTRSwitch* callbacks you will effectively move the switch to its appropriate position and thereby illuminate the indication lamp, which will tell you at a glance whether you are recording, on auto or off.
#===============================================================================================
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “=========== AVTR PANEL ===========”
SimAVTRToggle -1 0 0X21 0 0 0 1 “AVTR: AVTR Switch - Toggle”
SimAVTRSwitch -1 0 0X21 4 0 0 1 “AVTR: AVTR Switch - Cycle”
SimAVTRSwitchUp -1 0 0XFFFFFFFF 0 0 0 1 “AVTR: AVTR Switch - Toggle Up”
SimAVTRSwitchDown -1 0 0XFFFFFFFF 0 0 0 1 “AVTR: AVTR Switch - Toggle Down”
SimAVTRSwitchOn -1 0 0XFFFFFFFF 0 0 0 1 “AVTR: AVTR Switch - ON”
SimAVTRSwitchAuto -1 0 0XFFFFFFFF 0 0 0 1 “AVTR: AVTR Switch - AUTO”
SimAVTRSwitchOff -1 0 0XFFFFFFFF 0 0 0 1 “AVTR: AVTR Switch - OFF”
#===============================================================================================One less message flashing on the screen.
-
thanx Kolbe for organising the callback forest for us.
while making my own i stumbled over this (BMS_Keystrokes_Ver_1_4_Full.key):
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======= FUEL QTY SEL PANEL =======”
SimExtFuelTrans -1 0 0XFFFFFFFF 0 0 0 1 “QTY: EXT FUEL TRANS Switch - Toggle”
SimFuelTransNorm -1 0 0XFFFFFFFF 0 0 0 1 “QTY: EXT FUEL TRANS Switch - NORM”
SimFuelTransWing -1 0 0XFFFFFFFF 0 0 0 1 “QTY: EXT FUEL TRANS Switch - WING”
SimIncFuelSwitch -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - Toggle Up”
SimDecFuelSwitch -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - Toggle Down”
SimFuelSwitchTest -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - TEST”
SimFuelSwitchNorm -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - NORM”
SimFuelSwitchResv -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - RSVR”
SimFuelSwitchWingInt -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - INT WING”
SimFuelSwitchWingExt -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - EXT WING”
SimFuelSwitchCenterExt -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - EXT CTR”(all disabled)
just to tell you.
many thanks again!
cheers -
Hi,
thanks for the info.
Seems to me I just forgot to set the keys for them. At least
QTY: EXT FUEL TRANS Switch - Toggle
QTY: FUEL QTY SEL Knob - Toggle Up
QTY: FUEL QTY SEL Knob - Toggle Downshould be assigned.
Will fix this in my next update.
Regards
Kolbe
thanx Kolbe for organising the callback forest for us.
while making my own i stumbled over this (BMS_Keystrokes_Ver_1_4_Full.key):
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -1 “======= FUEL QTY SEL PANEL =======”
SimExtFuelTrans -1 0 0XFFFFFFFF 0 0 0 1 “QTY: EXT FUEL TRANS Switch - Toggle”
SimFuelTransNorm -1 0 0XFFFFFFFF 0 0 0 1 “QTY: EXT FUEL TRANS Switch - NORM”
SimFuelTransWing -1 0 0XFFFFFFFF 0 0 0 1 “QTY: EXT FUEL TRANS Switch - WING”
SimIncFuelSwitch -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - Toggle Up”
SimDecFuelSwitch -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - Toggle Down”
SimFuelSwitchTest -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - TEST”
SimFuelSwitchNorm -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - NORM”
SimFuelSwitchResv -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - RSVR”
SimFuelSwitchWingInt -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - INT WING”
SimFuelSwitchWingExt -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - EXT WING”
SimFuelSwitchCenterExt -1 0 0XFFFFFFFF 0 0 0 1 “QTY: FUEL QTY SEL Knob - EXT CTR”(all disabled)
just to tell you.
many thanks again!
cheers -
Hi - I am very confused here. I downloaded Kolbes keyfile but it doesnt seem to do much for me.
What exactly is it supposed to do once I load it? And I apologize for the stupid question, but I have gone thru the manual, as well as tried various keyfiles and Foxy profiles, and cant get anything to work correctly.
First thing - I dont know how to program the Cougar.
But reading thru the BMS manual, it made it sound like programming the Cougar was a thing of the past….that BMS was designed to do complex things with the Cougar without having to use Foxy. But how do I do this???
I have tried Duncs profile - and to its credit, it works - the throttle cursor works and everything - but it causes BMS to crash every time I use it…either during a mission or when I end a mission.
I just want my Cougar to work…I dont need a super complex setup where there are double shifted functions. To start, I would like every button to work, and the throttle cursor. How to I accomplish this???
I posted a similar question on the General forum and even though I mentioned that duncs profile caused crashes, people told me to use duncs profile…and someone even suggested selling my Cougar.
Is there anyone here that can take pity on me and explain how to get this to work in laymans terms? This is about to turn into a tragedy - I drove 100 miles on the day F4 was released in 1988 to buy my copy…and although I have used it here and there since…I finally have a PC powerful enough to run it properly. But I am about to get rid of it and throw the cougar and my 2 throttles away out of frustration. I just dont know what to do.
So here are my questions:
In order to use the buttons and the throttle cursor on the Cougar…do I need to use Foxy? Or can I just use a keyfile?
I was under the impression that one of the included keyfiles allowed the Cougar to work without any more additional work…is that correct? If so, is it BMS.key? If so, what do I have to do to get it to work? Do I have to run any Thrustmaster software in addition to BMS?
How do I modify a keyfile? Do I load it in a text editor, and then paste values created via the keyfile generator Excel spreadsheet? Or do I assign keys from within Falcons controller section?
And is there anyone that could please gently walk me thru getting my cougar to work without having to use duncs profile?
Sorry for my frustration - I just cant get this to work and it is really frustrating me.
Mike
-
I use a personalized Kolbe keyfile but with an X-52, so I can help you, or better I try to help you, only for the keyfile part.
In the files you’ve downloaded there’s a guide made by Kolbe where you find a lot of informations about keyfiles. In simple terms a keyfile is the configuration of the controls that appear in the setup section of BMS. In Kolbe files there are several configurations: one completely blank, one for pitbuilders and one for normal users. These keyfile are programmed to use keyboard for controls and you have to use the programming software of your HOTAS to map all the commands you need. Maybe you can already find some profiles here in the forum. Keep in mind that BMS is already programmed for the long press functions, i.e. if you want to use TMS down for more than 1 second, you only have to do it, without program your HOTAS to activate another function after a press long more than 1 second.I hope I was enough clear and I apologise for my not so good English.;)
-
@Boeckler
Before we begin,
Have you correctly installed your Cougar?
What is your Operating System?
32bit or 64bit?
Do you use TrackIR?
Do you have any external rudder pedals?So here are my questions:
In order to use the buttons and the throttle cursor on the Cougar…do I need to use Foxy? Or can I just use a keyfile?
Your Cougar needs to be installed and recognised by your operating system.
You should have installed these files before even worrying about using anything Falcon related
Forgotten how to install a Cougar?
Here is a FAQ on what you should do
http://cougar.flyfoxy.com/faqinstall.phpYes you need to use Foxy, so go and download it from the link above and calibrate your Cougar and confirm all switches and axis respond.
Kolbes keyfile is an excellent resource
I was under the impression that one of the included keyfiles allowed the Cougar to work without any more additional work….is that correct?
Duncs (included) or Kolbes (adaptation) require only minimal coding from Foxy
If so, is it BMS.key?
Please use Kolbes
If so, what do I have to do to get it to work? Do I have to run any Thrustmaster software in addition to BMS?
Regardless of what you want to do with your Cougar, you should have installed and use the appropriate software. You will need to interact with Foxy and Cougar Control panel, which are all installed form the above links.
How do I modify a keyfile? Do I load it in a text editor, and then paste values created via the keyfile generator Excel spreadsheet? Or do I assign keys from within Falcons controller section?
Dont worry about modifying anything for now. You should confirm that you are capable of installing your HOTAS first before you embark on a career as a coder.
Just use Kolbes its practically perfect.
And is there anyone that could please gently walk me thru getting my cougar to work without having to use duncs profile?
I am trying to walk you gently through this and point you to the easiest way to get a Cougar working for Falcon. Duncs profile is easy to implement, I suspect installing your Cougar correctly first is whats holding you up.
There is nothing at all wrong, difficult or overly complex about Duncs profile, more likely you are not running the appropriate software to get your Cougar running properly.
Sorry for my frustration - I just cant get this to work and it is really frustrating me.
Mike
Now how about some answers to my questions before we proceed any further.
-
Thanks for both of your replies.
Killer - I am running Windows 7 64bit Home Premium. I have successfully installed “2007_HCO_VISTA_64_RC1.exe” - using “Vista Compatibility” mode. It installs the Cougar drivers as well as Foxy 4.4.02, CCP, and a few other things. As far as I can tell, the Cougar is correctly installed at this point. The reason why I say this is because a) the CCP is showing all buttons and axes as working and b) I am able to use duncs profile for a while….but it eventually crashes. I have posted a link to my crashlogs to the technical support forum.
As for your other questions - no, I am not using TrackIR or any rudder pedals.
I think I answered all of the questions that you needed answered.
Killer - thank you for taking the time to help me!
Mike
-
Thanks for both of your replies.
Killer - I am running Windows 7 64bit Home Premium. I have successfully installed “2007_HCO_VISTA_64_RC1.exe” - using “Vista Compatibility” mode. It installs the Cougar drivers as well as Foxy 4.4.02, CCP, and a few other things. As far as I can tell, the Cougar is correctly installed at this point. The reason why I say this is because a) the CCP is showing all buttons and axes as working and b) I am able to use duncs profile for a while….but it eventually crashes. I have posted a link to my crashlogs to the technical support forum.
As for your other questions - no, I am not using TrackIR or any rudder pedals.
I think I answered all of the questions that you needed answered.
Killer - thank you for taking the time to help me!
Mike
Hey Mike
Sorry I took so long to get back to you, been busy
Glad to know that you have got it installed OK, although I was hoping that the problem lay in the installation process. Anyhow, what I thought we might try is the simplest approach possible eliminating any chance of conflicts.
Create a new file in Foxy with just these two lines in it
DISABLE MOUSE
USE ALL_DIRECTX_BUTTONSand save it in your C:\Program Files\Foxy\Files\MikeDX folder (yes create a folder called MikeDX)
Compile it and Download it to your Cougar using either Foxy or CCP (which is standard procedure for any profile you are going to use)
Load up Kolbes keyfile (whichever one is appropriate for you)
Test the functionality of hats and rotaries in Falcon Setup Controllers, centre your stick and set your AB detents etc.
Take it for a spin using whatever missions previously gave you grief.
Dont worry for now if the keyfile buttons are not what you want, we can address that later, I just want to see if a simple dx approach causes you issues.