Combine "BMS Full.key" with older Helios profile
-
Hi everyone,
I had been running Falcon 4.32 with Rogues Helios profile and corresponding key file and recently updated to 4.33. I noticed that the key file ‘BMS Full’ within 4.33 is really well catagorised and has quite a few enticing extras. With a little digging in my docs folder I realised Kolbe is the guy responsible for what must have been hours of work - well done!
The ‘Rogue.key’ file that I am currently using works flawlessly and Rogue is to be commended for the many hours of work that must also have gone into this profile. With some more digging I worked out I could add content to the key file and soon had cut and pasted a number of extra lines of code from the updated BMS Full.key into Rogues to get access to some of the newer features. For example, today I added the ‘Track IR re-center’ line so that I can now bind this function to my Hotas.
However, I wonder how I would go about combining the BMS Full.key file with Rogue’s Helios profile? This way I could have access to a better catagorised key map whilst continuing to use this great profile. Not too sure but at a guess, does this mean I would have to:
1. edit Rogue’s profile in helios
2 import the BMS Full.key
3 remap every single flight control to the new key file?If so I feel like I have a lot of learning to do…
If anyone knows of a simpler way and doesn’t mind sharing it I’d love to know about it.
Thanks in advance. -
I would recommend using the BMS Full.key and then just copy-pasting Rogue’s stuff into it, not the other way around. Easiest I could think of is to copy-paste both .key files into Excel. I would put the new .key lines on the left and Rogue’s on the right, and then sort out Rogue’s so that the same callbacks are on the same lines, then just go down the lines one-at-a-time. Tedious work, but you’ll only have to do it once.
Then copy-paste the new .key lines onto Notepad++ and name it as your own .key file.
-
Great advice Ice, I will get straight onto it.
-
Hey Ice, just a quick update to let you know your trick worked a treat. However I am somewhat cross-eyed after a full day of mind numbing work… So far everything seem to be working as planned but haven’t had a chance to test everything yet. Thanks again for the help!
-
You are most welcome!
Like I said, it’s tedious. If you have a little background on Excel, you can separate the callbacks into the appropriate sections and let Excel “combine” the proper things for you automatically, but unless you want to LEARN Excel as well, just do it manually and get it over with and get to flying
-
Unfortunately I only did the excel basics back in highschool so even though I knew it was possible, after 20 years it was seriously easier to manually change literally hundreds of callbacks than learn yet another program…
After a bit of testing it all seems to have worked apart from the sound id’s. A lot of Rogues callbacks used the older 4 digit codes or a ‘-1’ to inhibit sound, and so I changed these to the particular callback’s respective 3 digit code (from the newer key file). However when I went in game anything I ‘clicked’ on the Helios touchscreen did not make a sound (even thought the command is executed in the 3D cockpit). If i click a switch on the 3D cockpit with the mouse, I hear the appropriate sound FX so I know its not a cockpit volume thing. Anyways I got frustrated and went searching to see if anyone had made any updated Helios profiles that took advantage of 4.33’s new keyfile. And guess where that led me??
Ha! so now I am runnng Ice’s helios profile!
Man, I really put the cart before the horse on this one. Whilst I really like Rogues profile it was great to see some really helpful extras in your profile like airfields information and side panels in the vertical. I installed Weepop’s variation also and looks like he’s done some great work also. The only thing I’m still having trouble with is the sound fx when I click something in Helios? In both your profile and Weepop’s I hear nothing. Any ideas? -
If you are using my profile and my .key file, you should hear the sounds. Not sure on Weepop’s.
They changed the sound IDs on 4.33, standardized it. It was a mess in 4.32. Really, what you should’ve done is just change the keystroke section of the callbacks and touched nothing else. Try my profile “as intended” and see if you have sound.
-
Sorry should have explained myself better. When I went looking for a new Helios profile I ditched my old .key file
So now I am running your Helios profile with your .key file or weepops profile with his .key file.
Unfortunately neither play sound? Not sure where to look on this one.
-
Have you got my latest profile and key file, see downloads, because it should have sound now.
weepop
-
Hi weepop,
Yes I downloaded your latest profile and key through your mediafile site but still to no avail. I looked at both yours and Ice’s .key file and can see the 3 number codes on each call back but for some reason my computer doesn’t like it? I am running version 4.33 not the later 4.33.1 if that makes any difference? Also I have Windows 7 professional 64 bit but for some reason can only play 4.33 in 32 bit mode. Would this have anything to do with it?
Sound issues aside for me, you’ve done a great job with the profile! I really like the extra airport material
-
Hi Wilkotaz
Glad you like my profile, do the extra buttons for NAV GPS etc work for you? and all the extra pages in airport or weapons etc?
I also have win 7 pro 64 and I run in 32 bit because of problem with free track in 64 bit, so that`s not your problem.
Do all other in game sounds work ?
-
I have not played much of 4.33.1 so my profile is mainly 4.33.0, and IIRC, the sounds were working. The 3-number codes are new for 4.33, as you know 4.32 used the old 4-digit codes. Not sure if 32/64 bit makes a difference. What are your in-game sound settings? Maybe you muted it there. Also verify on the Helios profile that you are pointing to the correct .key file.
Quick test –- start up a TE, maybe the Day Landing one, then fiddle with the ICP buttons and other switches. There should be sound and the buttons should work (ie, flicking a switch in Helios should also activate the switch in the cockpit). I just wonder whether you’re actually “tied” into the correct .key file.
-
Hi Wilkotaz
Glad you like my profile, do the extra buttons for NAV GPS etc work for you? and all the extra pages in airport or weapons etc?
I also have win 7 pro 64 and I run in 32 bit because of problem with free track in 64 bit, so that`s not your problem.
Do all other in game sounds work ?
Yep. All buttons, switches etc that are pushed on my touchscreen elicit the correct response in the 3D cockpit (albeit with no sound). All of your charts and weapons pages function correctly also, even the new GPS buttons etc within your charts that automatically input co-ords work (great addition for noobs like me who are still learning). I am using Weepop-Ice.hpf and have tied it to weepop BMS4.key within Helios. When I am in the game UI I select your weepop BMS4.key from the controller settings page before launch. Whilst I don’t getting any ‘clicking’ sound effects from my touchscreen inputs, if I use the mouse to hover over the same switches in the 3d cockpit I receive the sound when I push down on it. Kinda weird hey? Am I perhaps missing any other files?
-
Quick update Ice and Weepop. I tried a fresh install of BMS and Helios on my sisters computer following the same technique as before and to my excitement it all worked. I figured from this outcome that I had some confliction issues (elsewhere/unrelated to Falcon or any of its associated programs) on my PC. As it has been a long time since it has had a fresh install I backed everything up and wiped it clean. Upon reinstalling windows 7, BMS and Helios, I am proud to say everything is now functioning as intended with full sound effects!!
Unfortunately I never diagnosed the real problem, but since I have not heard of anyone else suffering from this, hopefully the problem is long gone.
Of course once you overcome one challenge in BMS cockpit configuration, another one is ready to leap right at you. I hadn’t noticed before in my control settings that the trim hat does not function (was too busy working on sfx issues…).
I realise this is to do with your your .key files not working with my HOTAS setup. I use a TM Warthog stick and TM Cougar throttle via realsimulators TUSBA TQS R2 adaptor and previously in 4.32 I never needed TARGET or anything else to allow it to work in Falcon, it was just detected and made available in Windows 7 Games Controllers in W7 Control Panel. This is true for my 4.33 installation also.
My question therefore is, what is the best way for me to get full functionality of my HOTAS with both of your profiles? I understand Ice that you had conflicts with Track IR and so " ported over Morphine’s lines" into your BMS - FPM by Ice.key file to fix the problem. However I am using this key file with your helios profile and still experiencing the same problem. I figure it is because when you wrote your profile it was obviously to work with your HOTAS setup but I am not sure how the coding works to accept joysticks etc.
I wonder specifically, how do I go about editing either “BMS - FPM -Ice.key” or “weepop BMS4.key” to get full functionality of the your profiles AND my HOTAS setup?
I feel like I owe you guys some beers for your time
-
Glad to know it’s working. One of Weepop’s issues was that he needed to “fix” the charts page but nobody else had reported that problem. Weird indeed.
As for my profile, as you know, I adopted it from Morphine’s. This means you’ll have to start up TARGET Script Editor, load up the .tmc file, run it, and then start up everything else. The .tmc file combines both controllers (TM WH stick and throttle) into one virtual controller. I’m not sure how exactly that will affect your TUSBA throttle setup though.
-
This post is deleted! -
Unfortunately my TARGET GUI did not detect my TUSBA Cougar throttle, and with a little looking online it appears it is not compatible with TARGET or other software such as Foxy.
I realised that the Warthog Trim Hat WAS functioning in your ‘BMS - FPM by Ice.key’ but NOT in Weepop’s ‘weepop BMS4.key’. I figured therefore that you had some code in your file Ice, that would allow me to get the Trim Hat working in Weepop’s and so edited both key files in order to compare them. I noticed at the bottom of each of the files there is different code to the majority of callbacks which I am guessing is the DX callbacks for individual joystick/input device buttons.
When I physically push directions on my Hat in your profile I get the following responses written in the UI
Input POV1: Left
STICK: TRIM Left - Roll leftInput POV1: Right
STICK: TRIM Right - Roll RightInput Pov1: UP
STICK: Trim Nose DownInput Pov1: Down
STICK: Trim Nose UpIn the UI list of controls I also see that STICK: Trim Up,Down,Left and Right are bound to keyboard keys +,-,Num. and Num0
So it seems the exact same function in BMS can be bound to 2 different input devices (i.e. one on a joystick and one on a keyboard for example)?
With this information I went looking within the BMS - FPM by Ice.key for the Trim Up,Down,Left and Right callbacks at the bottom of the key file in what I am assuming to be DX joystick callbacks. I found these codes for left and right for example.
AFAileronTrimLeft 0 -1 -3 5 0x0 0
AFAileronTrimLeft 0 -1 -3 6 0x0 0
AFAileronTrimLeft 0 -1 -3 7 0x0 0AFAileronTrimRight 0 -1 -3 1 0x0 0
AFAileronTrimRight 0 -1 -3 2 0x0 0
AFAileronTrimRight 0 -1 -3 3 0x0 0Although even further confused that there were three separate codes for each direction, I selected the number code 0 -1 -3 5 0x0 0 associated with AFAileronTrimLeft and using the ‘Find’ function in notepad, searched for this code in weepop BMS4.key hoping to find a match. However notepad could not find one.
Am I on the right track here? I figure if I can locate the joystick hat callbacks within BMS - FPM by Ice.key, I can copy and past them in weepop’s key and have full functionality of the hat?
I should also mention that when I load weepop’s key file in the UI I get 'No function Assigned" displayed whenever I physically push a direction on the hat (due to their assigned callbacks having the -1 0 0XFFFFFFFF 0 0 0 0 function in the code), however within the game these directions move the cockpit FOV (sort of like looking with the mouse if you don’t have Track IR).
-
Wilkotaz
I do not use any DX settings as I prefer my CH program.
I do not use the POV hat for trim only for view, because I like to be able to turn off my free track under certain circumstances
and fall back to the POV hat. This is why I run in 32 bit (post 11) as it does not happen in 64 bit.I have programmed keys on my G19 keyboard for trim which I find acceptable.
I am seriously considering changing to BMS full key as you state in first post so would be very interested in what you come up with.
weepop
-
As you have found, there are two ways to trim – via keyboard and via the hat switch. The keyboard controls is mapped via “keyboard” while the hat is mapped via directx, if that makes any sense.
-
Ice - Yes I now understand there is both a keyboard mapping and a DX mapping within the keyfile. However I can’t seem to determine which part of your keyfile is assigning the Hat controls on my Warthog stick. I figure if I can find this DX code within your key file I can copy and paste it into weepops. Is there any way I can find out what my DX mappings are when I press them, perhaps via other software? I really want to copy the correct code from your key file to weepop’s.
Weepop - Sorry Weepop, it was my understanding you are using the BMS full key? Just configured for you joystick setup. I’m not on my sim computer at the moment so can’t look at your keyfile to confirm. My goal is to get the BMS Full key functioning with both your helios profile and Ice’s, and have my HOTAS setup able to utilise all buttons. Do you have any suggestions on where I should be reading in order to achieve this? I am guessing that your CH program must be written into your keyfile somewhere because when I push my POV Hat I move my view around the cockpit. I have no experience at programming whatsoever but can see a link here, just not sure how to go about it. And if I get it sorted you will be the first to know!
