BMS Key File Help
-
Hi Leech,
that’s strange.
I’ve just checked it twice now and I can’t find a reason, why it should’nt work this way.
What happens, if you use CTL+Z+R (And with ALT+C : F)?
Which HOTAS do you use?
Does anyone else have this problem?
EDIT:
After reading your post again…
I got you wrong…F…k,
next beer is on me???
-
Dear Killer. You have not Read The FM? It is mentiond twice (in my documentation), that the keylayout has changed and “is not comparable to other versions before.” :uham:
-
:uham:
-
Sorry for the confusion Kolbe. You file clearly says ctl c f for fps. That totally works. But i’m just too used to ctl z r, that in my head the fps display is still ctl z r… So, there is no problem but my head
-
Hi, I got the same issue as LeechNL, spend quite a bit of time, but can’t get a trim response from the hat 1 of my cougar. all the other commands, DX and shifted DX work fine.
Here all the related commands from the modified dunc’s keyfile. Maybe there’s something wrong here.
Red - ensures the unshifted edge buttons on the hat do nothing,
Blue - ensures all the shifted buttons on the hat do nothing
Green - maps the elevator and aileron trim buttons.
Black - trim related command lines for completeness.[b][color]SimDoNothing 0 -1 -3 1 0x0 0 SimDoNothing 0 -1 -3 3 0x0 0 SimDoNothing 0 -1 -3 5 0x0 0 SimDoNothing 0 -1 -3 7 0x0 0 [/color] [/b] [b][color]SimDoNothing 2 -1 -3 0 0x0 0 SimDoNothing 2 -1 -3 1 0x0 0 SimDoNothing 2 -1 -3 2 0x0 0 SimDoNothing 2 -1 -3 3 0x0 0 SimDoNothing 2 -1 -3 4 0x0 0 SimDoNothing 2 -1 -3 5 0x0 0 SimDoNothing 2 -1 -3 6 0x0 0 SimDoNothing 2 -1 -3 7 0x0 0 [/color] [/b] AFAileronTrimLeft -1 0 0X27 0 0 0 AFAileronTrimRight -1 0 0X2B 0 0 0 AFElevatorTrimUp -1 0 0XC 0 0 0 AFElevatorTrimDown -1 0 0XD 0 0 0 AFResetTrim -1 0 0XC8 1 0 0 SimTrimAPDisc -1 0 0X5 2 0 0 SimTrimAPDISC -1 0 0XFFFFFFFF 0 0 0 SimTrimAPNORM -1 0 0XFFFFFFFF 0 0 0 SimTrimNoseUp -1 0 0XC7 5 0 0 SimTrimNoseDown -1 0 0XCF 5 0 0 SimTrimYawLeft -1 0 0XD2 5 0 0 SimTrimYawRight -1 0 0XC9 5 0 0 SimTrimRollLeft -1 0 0XD3 5 0 0 SimTrimRollRight -1 0 0XD1 5 0 0 AFResetTrim 257 -1 -2 0 0x0 0 [b][color]AFElevatorTrimUp 0 -1 -3 0 0x0 0 AFAileronTrimRight 0 -1 -3 2 0x0 0 AFElevatorTrimDown 0 -1 -3 4 0x0 0 AFAileronTrimLeft 0 -1 -3 6 0x0 0 [/color][/b]
Any help / advice welcome.
Cheers.
Fish -
I’m still no expert, but could it be because you have the same function mapped twice?
AFAileronTrimLeft -1 0 0X27 0 0 0
AFAileronTrimRight -1 0 0X2B 0 0 0
AFElevatorTrimUp -1 0 0XC 0 0 0
AFElevatorTrimDown -1 0 0XD 0 0 0and
AFElevatorTrimUp 0 -1 -3 0 0x0 0
AFAileronTrimRight 0 -1 -3 2 0x0 0
AFElevatorTrimDown 0 -1 -3 4 0x0 0
AFAileronTrimLeft 0 -1 -3 6 0x0 0What happens is you remove the first part?
AFAileronTrimLeft -1 0 0X27 0 0 0
AFAileronTrimRight -1 0 0X2B 0 0 0
AFElevatorTrimUp -1 0 0XC 0 0 0
AFElevatorTrimDown -1 0 0XD 0 0 0 -
……could it be because you have the same function mapped twice?..
I believe extra lines for the trim above are for keyboard mapping, and came as default in dunc’s keyfile. It’s not a problem to have both a POV (or a DX) statement using the same callback as a keyboard (one only allowed) command.
Got my problem sorted. POV HAT was not enabled in foxy.
In Foxy i had disabled HAT1 as POV, to allow for mapping of DX buttons, but the mappings for the POV below are a special type of DX mappings, and require POV enabled on Hat1!!. So i just included a line in the tmj file
[color]'USE HAT1 as POV'[/color].
Now i think I know enough to implement Kolbe’s new keyfile.
-
Great work Kolbe, very nicely laid out keyfile
Quick typo for you, key “1” has “LMFD OSB 02” rather than “LMFD OSB 01” listed in the pdf.
Also, assuming Dunc doesn’t mind, it’d be great if you could include tmm/tmj files along with a version of his cougar setup instructions and joystick mapping doc. I know it’s straight forward to setup Dunc’s then your keyfile, just thinking about future users, even more so if this setup ships with the next BMS update (which I hope it does)
-
……Then feel free to download it and give it a try…I would be happy about some feedbacks, whether they are good or bad.
Kolbe
Hi Kolbe,
Thanks for all your effort. Just configured your file for DX callbacks, based on dunc’s profile, and it is very sweet indeed. I started off with the blank file, and just configured the ICP stuff for my P8000 + a few others. I don’t need many since its all clickable now!! Got everything for my stick as DX, except the TG1, which i left as DUNC has it for snapping between padlock and 3D.I noted something which might be just me or my install. When i compile the key file in BMS (load then save from the controller UI), i get all the SimDoNothing callbacks changed to SimRadarNextTarget. I tried it with the original file from your pack, and I got the same result. Not sure of the cause, but i expect the effect would only be felt if any of the SimDoNothing strings were assigned keys. Wanted to assign a key to one of my shifted DX keys for my TS PTT.
Cheers
Fish -
Hi,
Got my problem sorted. POV HAT was not enabled in foxy.
Would be nice to know, how you disabled POV in Foxy as there are several ways to do it (which means: Force the H1 hat not to act as default POV)
Usually it should not be necessary to add the code line USE HAT1 as POV.Great work Kolbe, very nicely laid out keyfile
Quick typo for you, key “1” has “LMFD OSB 02” rather than “LMFD OSB 01” listed in the pdf.
Also, assuming Dunc doesn’t mind, it’d be great if you could include tmm/tmj files along with a version of his cougar setup instructions and joystick mapping doc. I know it’s straight forward to setup Dunc’s then your keyfile, just thinking about future users, even more so if this setup ships with the next BMS update (which I hope it does)
Thank you.
I will change LMFD OSB 01 in my next update.Regarding to the instructions:
I will do so. I have excluded all Cougar relevant info into a separate pdf. Besides that I have a main manual (introduction to my key files, general DX stuff…), one pdf for the TM Cougar MFDs and now I’m working on instructions and necessary files for the Warthog. Not easy, 'cause I don’t have one(Btw: ZELEGEND, if you read this. Sorry! I was busy in rl. I will provide testing stuff soon, I hope… )
When i compile the key file in BMS (load then save from the controller UI), i get all the SimDoNothing callbacks changed to SimRadarNextTarget. I tried it with the original file from your pack, and I got the same result. Not sure of the cause, but i expect the effect would only be felt if any of the SimDoNothing strings were assigned keys. Wanted to assign a key to one of my shifted DX keys for my TS PTT.
Lol,
I have never expected, that someone would try to set keys for SimDoNothing
You are right, if you set keys (manually by editing the key file in an editor) you will have this result after next save in UI. In UI you are not allowed to change these SimDoNothings. Not without any reason. But thank you for this advice. I just checked my manual and expressed not clearly enough not to do this. So I will add this info in my update.
Maybe it was not clever to include those code lines into the key file.IMHO, there are only some possible solutions:
-
Edit the dunc.tmm/tmj
You can implement code to use TS with a button without loosing DX functionality.
If you need help, PM me. -
Use keyboard only
Boooring… We can do better -
Use the COM1 / COM2 callbacks
Just set the same keys in TS for broadcast and PTT (optional) as for COM1 / COM2.
You will either use TS or IVC, but most likely not both at the same time. When in “IVC mode” just mute your mike in TS (and optionally speakers as well). -
Use a not working callback with DX
For example:
The callback KneeboardTogglePage is not implemented right now. (There are several other callbacks which are not implemented atm) So if you assign a key, nothing will happen in game.
This callback can be assiged as a DX command in the key file. Problem is, that they are not safe for future use, 'cause we will (hopefully) have a working kneeboard in future releases or mods.
But I am wondering, if the callback SimRadarNextTarget is really bad at all?
Who cares if you have dozens of those callbacks in your key file without assigned keys?
If you have enabled realistic avionics in setup, this callback should do nothing, btw. (not tested)IMHO, this is worth to set it on the dev’s to do list:
- implement “fake” callbacks to use as DX commands for TS in the key file (or callbacks like recenter TRACKIR, which work)
or - teach the damn UI
nottochangethebloodycallbackswhenkeysareassignedtosimdonothing
Hope, I could help.
Regards
Kolbe
-
-
Yep,me too,just trying to use pause trackir instead of reload trackir,that and the damn rotaries and wheel pain in ass on the x-52,trying to set up,antenna elevation,radar range,radar gain and manual zoom in tgp mode on the two rotaries and wheel,frustrating.
-
……Would be nice to know, how you disabled POV in Foxy… Usually it should not be necessary to add the code line USE HAT1 as POV…….
Having it as a command in the profile i expect ensures its always that way, no matter how its set for other profiles, or by default.
……lol…I have never expected, that someone would try to set keys for SimDoNothing
Ha, thought i had a clever way to map a key to dx button to avoid a keyboard or tmj macro, but logically i now see it could not work. See my comment below
Hope, I could help.Regards Kolbe
Indeed you have. Lots of ideas there.
The callback KneeboardTogglePage is not implemented right now. (There are several other callbacks which are not implemented atm) So if you assign a key, nothing will happen in game. This callback can be assiged as a DX command in the key file.
Hmm. That would be nice, but don’t make sense to me. Here’s my understanding. The callback just causes bms to run some code, or internal command (like calling a function in code). The DX map just allows a button on the stick to activate that command, without going through any keyboard keystrokes, or cougar macros (which just mimics the keystorkes anyhow). So assigning a ‘key’ (or combo) to the callback, just provides ‘another way’, to call that bms command. ??
The TrackIR ‘recenter’ callback is an interesting one, cause it directly causes BMS to interface with TrackIR probably through some kind of API call, and causes a direct command to be implemented on Track IR, without any keyboard intervention. I expect BMS would need to interface with TS3 is a similar manner, or through some kind of ‘plugin’ into TS, to provide the DX functionality.
-
-
Thank you Kolbe!;)
BMS is my first Falcon sim and when I start to use it I found it very difficult to set the controls on my preferences: I could not understand what the functions in the list means because the descriptions are everything but clear.
But with your files and guide now I can make my own profile.
Thank you so much!
-
Ok,really stupid question here kolbe,how do I setup pausetrackir instead of reloadtrackir,thats all Iwant to do,everything else I can deal with but dang if I can change it,even when changing it manually,it screws things up,my fault,but I want pausetrackir,dont ask why. I cant even fiqure out the editor cause I dont have the program to use it-xls
-
how do I setup pausetrackir instead of reloadtrackir, I cant even fiqure out the editor cause I dont have the program to use it……
First IMO, there’s no stupid questions. I’m sure Kolbe will have a better answer for you, but in the meantime this might help.
1. BMS has callbacks for both Reload TrackIR (ReloadTrackIr), and Recenter TrackIR (RecenterTrackIR). From the official keyfiles, there’s no callback for Pause TrackIR at present. (maybe there’s a plan to do it in the future)
2. Where there is a callback you can use Direct X button, if your controller supports it, or map some keystroke/s to the callback, from in the game, then program them on your controller. These keys would be quite independent from those setup in your TIR software.
3. Where there’s no callback ( as in this case) BMS is irrelevant in how you set up to use it.
4. Two options, Keyboard, or program what ever controller you have (not clear from you post what controller you use).
5. You can edit the key strokes mapped to a callback in the game setup/controllers, menu, by clicking on the command, then apply the keys, then save the file.
6. You mention an editor above, you can edit the keyfile directly with a text editor, and while there are many free ones, notepad, in windows is perfectly adequate. There’s also an xls file floating around which helps you compile the lines to add to the keyfile, but like u said, you need excel to run it.
7. Pausing TIR IMHO is a bit hit and miss in the current BMS, as it does not always end up at the paused view, so not very useful.
Hope this helps some.
Fish -
Thanks fish,I have been using the keyboard but still would like it mapped on my x52,I use it (pausetrackir) during ingress and when doing other things.Did just download foxy,will start playing with that.I’ll fiqure something out,come hell or high water,I am a bit of a perfectionist. And scince I just lost my 2nd day in caimpaign on account of me fricking around,guess I’ll just mess around for another couple days or weeks.
-
@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 ?