-Ice's Falcon BMS Helios Profile Updated!
-
apoll
I had a similar problem only to discover that I was using one key file for BMS and a different one for Helios. The solution was to relabel the key file so I would stop making that mistake.
-
There should be no need to re-label the .key file. However, if you have just downloaded the any of the files, it is a good idea to close everything down then start up the programs again. For example, you are using the old .key file and BMS and Helios are running. You overwrite the old .key file with the new .key file –-- but since BMS and Helios are running, they’ve loaded up the OLD .key file. So shut down BMS and Helios then start them up again and they should load the new .key file automatically!!
-
As the old saying goes, this is better than nothing.
-
New profile and images released for you guys to try out!
Basically, I’ve updated the charts to use the ones from 4.33. I’ve not added the Russian/China/N.Korea airbases as I don’t think there’s a need for them. The two S.Korean airstrips and Mandumi are not included as well for the same reason. If there is demand for it, I can probably add them in but it’ll require a bit of a re-do in terms of button placement.
I’m a bit more excited about the change I did to the MFDs though. I’ve always found the actual OSB touch areas to be too tiny and basically applied my HSD/CRS/Altimeter trick to enlarge the OSB touch areas. I’ve also changed the rocker switches so that they’re bigger and so hopefully, easier to use. Even though I’ve done this “trick” on my HSD/CRS/Altimeter, credits to Toto for helping my brain make the connection between them and my OSB dilemma. So try it out guys and I look forward to hearing what you have to say about the new MFD!
-
I’ve, yea, definitely loading your TARGET script file with the Target script editor BEFORE launching BMS.
Sobe, ok, that would make sense. It is like there ar two files running. I will go back and delete everything and start again. I may have got the files crossed over somehow. I will make a distinct name for Ice’s latest key file so there is no mistake linking either the latest Helios profile with the right key file, nor any mistake when I load up the key file in the BMS UI. Will see how that goes. That diagram: represents the WH button commands WITH Ice’s Helios profile loaded, right? Unshifted, right?
Thanks to you both. Look forward to testing out th latest Helios, Ice, particularly the larger MFD buttons.
Regards,
Apoll
-
apoll
Sort of. The standard TMS and DMS commands are not listed and they are the unshifted commands right out of the manual. The commands listed for the TMS, and DMS are the shifted new commands. the rest of the profile contains the unshifted commands in the box and the shifted commands either on top or below the box. The diagrams are based on the latest ice WH/Helios/target key commands.
-
Well, something weird going on. My trim button is FOV, not trim. I hit unshifted DMS up, and get a declutter. Right unshifted and I get SOI switched to right MFD and no amount of clicking down switches it back to the FCR on left MFD. Down puts the LMFD FCR into DTE. Shift with the pinkie lever does nothing as far as I can see. I have no idea what is happening. I have cleared everything out, re downloaded and followed instructions carefully. When you press right DMS unshifted, what do you get?
thanks.
apoll
-
Further to my last. It is clear that the profile loaded is generating the wrong commands as far as the WH is concerned. is the Target script the culprit? Something is not right, and it certainly bears no resemblance to the command map from you Sobe. Ice, is the Target profile script ok? Something has porked my WH loading the script, since I have the Helios set up correctly and loaded your keyfile in the UI correctly. Grateful thoughts.
apoll
-
First of all, DO NOT rename the .key file. If you do, you will have to go to the Helios profile editor and tell it what the new .key file is. Just make sure that the .key file you are using in BMS is the same file that is loaded in Helios. You DO NOT need two .key files.
Second, the TM script is okay. Try loading Morphine’s original script and see if that at least fixes your TRIM and DMS/CMS buttons? You should be able to go into Setup -> Controllers and use the DMS/CMS/TMS buttons and it will show as the appropriate input.
Third, apologies for the problems with the TRIM. I did not port over Morphine’s TRIM lines to the new .key file. I’ve uploaded a new .key file to fix this.
-
Ok Ice. I will try this out.mthanks. I must crack this, or there is not much point proceeding with BMS. I’ll be stuck with the soulless DCS a-10!
Apoll
-
Ok Ice. More testing. I have discovered that the WH stick, for example, was not generating the correct button pushes. For example, in the UI controller’s viewing pane, I watched the commands being generated as you suggested when I pushed the DMS up/down/left/right. They were NOT generating the correct commands as outlined in your key file; that is, the up DMs selects the DMs up command in the Stick section of your key file. instead, it was selecting a button 45 LMFD button for some reason. ALL my WH stick button pushes were generating LMFD button pushes. No wonder I was confused. I had to re-map your key file by allocating the correct command in your key file to the correct stick button; ie, the DMS Up command in your Stick bit of the key file mapped to the WH Stick DMS up button. When I did this, it worked correctly. But it looks like I will have to go through the entire WH stick and throttle button and make sure the correct button is mapped to the correct bit of your key file. That is what the problem is. You don’t mean for that to happen, right? It should work straight up with no necessity to remap? Right? If that is so, I wonder why the stick was being loaded with the incorrect button presses? Is that to do with the Target script being loaded? What could load the stick/throttle up incorrectly?
Views? Solutions?
apoll
-
First off I’m loving all the work,but here is my problem.
If i take everything you have provided it all works, but if i take the key file and use a keyfile editor to bind some joystick buttons the keyfile will not load up in Helios.
Helios will just crash upon loading that file up , or it will load for a few seconds allowing me to get to assign the key file but nothing shows up in the Falcon Callback area and then still doesnt work. -
I’m not exactly sure what’s going on with your setup, apoll. It definitely isn’t my stuff that’s doing that. Is there another profile for TM WH that you can use that works properly? Have you used Morphine’s original profile? Have you assigned controls via the Advanced tab in Setup -> Controllers?
For me, even WITHOUT loading up my Target profile and going to BMS -> Setup -> Controllers, TMS/DMS stuff still works.
Ok Ice. More testing. I have discovered that the WH stick, for example, was not generating the correct button pushes. For example, in the UI controller’s viewing pane, I watched the commands being generated as you suggested when I pushed the DMS up/down/left/right. They were NOT generating the correct commands as outlined in your key file; that is, the up DMs selects the DMs up command in the Stick section of your key file. instead, it was selecting a button 45 LMFD button for some reason. ALL my WH stick button pushes were generating LMFD button pushes. No wonder I was confused. I had to re-map your key file by allocating the correct command in your key file to the correct stick button; ie, the DMS Up command in your Stick bit of the key file mapped to the WH Stick DMS up button. When I did this, it worked correctly. But it looks like I will have to go through the entire WH stick and throttle button and make sure the correct button is mapped to the correct bit of your key file. That is what the problem is. You don’t mean for that to happen, right? It should work straight up with no necessity to remap? Right? If that is so, I wonder why the stick was being loaded with the incorrect button presses? Is that to do with the Target script being loaded? What could load the stick/throttle up incorrectly?
Views? Solutions?
apoll
-
What exactly are you trying to do? I edit my .key file all the time as I go through this process; I had to do it again just now for the TRIM stuff to work and Helios and BMS works fine.
You WILL need to restart BMS and especially Helios for it to recognize the new key mappings, but should not be crashing.
First off I’m loving all the work,but here is my problem.
If i take everything you have provided it all works, but if i take the key file and use a keyfile editor to bind some joystick buttons the keyfile will not load up in Helios.
Helios will just crash upon loading that file up , or it will load for a few seconds allowing me to get to assign the key file but nothing shows up in the Falcon Callback area and then still doesnt work. -
I’m merely adding in some joystick button (warthog) assignments (NO TARGET).
I’m using the keyfile editor program - i’ve even tried the new alpha program.
I added things like speed brakes and some radar range controls, nothing crazy to the throttle.
Once i add the changes via the editor everything does actually work in BMS - but if i need to make a change to the helios profile the keyfile causes helios to crash.
Everything has been restarted to rule that out. -
How are you adding these? As DirectX buttons? Why are you not using TARGET?
If you are adding them correctly, Helios should not crash. As it currently stands, there are a few commands mapped directly to DirectX via the .key file and Helios is fine with it, so the “theory” is proven to work.
-
simple answer to some - target sucks - IMHO , its just one more program that has to be launched and i’ve never got more functionality out of it that i was missing.
Having said that i did try using the most recent updated target file.
when i ran it i lost the use of some buttons on my throttle that i wanted to configure.What i am doing is simply opening op the key file in the 3rd party keyfile editor program.
From there i find the joystick button that i want to assign and then add it the assignment - such as air brakes to the proper hotas switch and save it.If i then load up the helios editor and try to open my profile with that same key file bound to it - it crashes.
having said that it all does work properly in game - but if i need to make a change the the helios profile suck as changing all switch assignments from ‘swipe’ to ‘touch’ i have to start all over again.
If you around 7:30 pm est tonight, i’d be happy to jump in some remote session and show you, if you have no other thoughts off the top of your head.feel free to email me directly if you’d like [email protected]
-
What exactly are you trying to do? I edit my .key file all the time as I go through this process; I had to do it again just now for the TRIM stuff to work and Helios and BMS works fine.
You WILL need to restart BMS and especially Helios for it to recognize the new key mappings, but should not be crashing.
Ice, can’t you just reload the key file and click Apply in the Controller UI to test? Versus not restart BMS again?
-
Ice, can’t you just reload the key file and click Apply in the Controller UI to test? Versus not restart BMS again?
You probably can with BMS, but I prefer a restart.
-
simple answer to some - target sucks - IMHO , its just one more program that has to be launched and i’ve never got more functionality out of it that i was missing.
Yeah, just say “it suxx” and people will totally get you… not. How does it suck? What functionality were you looking for that you did not get?
Personally, I start so many things anyway that “what’s one more?” I use MFDE, TrackIR, VAC, Helios, sometimes FRAPS… so one more doesn’t really take more than 30 seconds.
when i ran it i lost the use of some buttons on my throttle that i wanted to configure.
I’m not surprised, the profile probably overwrote them. Which ones? Why? Can’t really tell with the limited info you’ve given.
What i am doing is simply opening op the key file in the 3rd party keyfile editor program.
What 3rd party program?
From there i find the joystick button that i want to assign and then add it the assignment - such as air brakes to the proper hotas switch and save it.
So you trust this program to make changes for you, but it crashes Helios, then you ask me why it doesn’t work?
changing all switch assignments from ‘swipe’ to ‘touch’ i have to start all over again.
Change all switches to touch, do your changes, then never touch Helios again?
Sorry for the tone, nothing against you. Just Monday, that’s all.