-Ice's Falcon BMS Helios Profile Updated!
-
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.
-
ok here we go - and all good on the tone.
–-------------------------------------------------
when i ran your target script i know the flaps and the boat hat stopped working, probably some more, but those i recall directly.the third party program was literally called ‘Keyfile editor.exe’ - it seemed to do exactly what i wanted it to do with out the hassle of binding things in game.
This app may crash helios ,but all changes i have made work perfectly in game - the goal of using this was just to make life easier when binding. as you can scroll and scroll via the in game menu and still not find the cursor slew options.
and on the changing of swipe to touch, i’d be ok making the change once - but this cool guy named ICE keeps making these awesome updates forcing me to use this kick ass profile i’ve been hoping someone with a high level of brain power would make for a long time… HA
-
Yep, on the ver6 TARGET profile, I took out the FLAPS control. The BOAT switch should be MRM/DF override.
As for editing the .key file, I would recommend Notepad++ and editing by hand. I would also NOT recommend editing the .key file via the in-game UI. I do all my edits on Notepad++
The beauty with the new .key file is you should know EXACTLY where your callbacks should be. If you are referring to your cursor up/down/left/right, I know exactly, EXACTLY where they are because I know where that switch is located in the real aircraft and therefore I know exactly where it is located in the .key files. 2.19 is the Throttle Quadrant System and that’s where it should be.As for changing profiles, I’ll have a word with this cool guy and tell him to stop messing with your Helios profile
In all seriousness though… run my stuff AS IT SHOULD BE… run TARGET. Use my .key file. Run Helios. Then if you’re missing something, tell me and I’ll see what I can do. As far as I can tell, you not running TARGET is more of a preference thing rather than a concrete obstacle to the game. So give TARGET a try (I was in the same boat before), the built-in IDLE DETENT, the different shifted layers, the ability to specify what a long-press vs. short-press would do, it’s worth it. For example, the small gray pinky button on the stick… short press is TIR center, long press is AP disconnect — and this is in the UNSHIFTED layer.
Bottom line, it’s easier for me to fix and tweak things if we’re all on the same page.
-
Thanks Ice. Yea, I do not know what is happening. But yes…what I have is definitely not what you intend. The thing is I follow your instructions to the letter…no messing around with extraneous software…no mucking with key files ect. Just as you wrote. I also delete old versions before putting in new versions. I have set up the advanced controllers properly according to instructions. But no good: my stick buttons are generating LMFD commands. Wierd and, at the moment, inexplicable. Tell me one thing: what program/file in all this is responsible for uploading key commands to the WH buttons? Is it the key file? Or the Target script? You mentioned you changed the Trim button to work properly. How did you do that? Because before when I used it it was PoV. Now, after your change and without any input from me, it has changed to work trim. What did you do exactly to change that? Because that is probably what I need to do to the whole profile to correct it.
Thanks Ice. Much appreciated. I will persevere.
Apoll
-
apoll, I need you to answer the following:
1. Has your HOTAS every worked properly before? If yes, describe how you were using it at the time.
2. Do you use TrackIR?
3. Have you write-protected the joystick.cal and axismapping.dat files? It might be a good idea to un-tick read-only, go back into BMS and set everything up correctly, then have a few flights, and if things are working good, then write-protect the two files again.
4. What exactly do you have connected to your PC that you use for simming?
5. Try out the Helios profile. Are the switches working as intended? Do the corresponding switches in the game move as they should? Are the MFD OSBs working properly?
6. Go in the 2D UI of BMS, go to Setup -> Controllers. Press TMS up. What happens? There’s a small area that will tell you what command was recognized, what does it say?There’s something in your system that interferes with your HOTAS working correctly. I’m not exactly sure what it is.
what program/file in all this is responsible for uploading key commands to the WH buttons? Is it the key file? Or the Target script?
The program does not “upload” the key commands to the buttons. TARGET basically becomes some sort of “middle man” or “interpreter.” You press a button and TARGET deals with it as the profile (TARGET profile not Helios) dictates. As I said earlier, if you load up the TARGET profile and short-press the gray pinky button, TARGET sees the short press and sends out a “TrackIR center” command. Long-press that same button and target sends out a “AP disconnect” command. It’s still the same button though!
As for the .key file, it received TARGET’s commands and interprets it for BMS to act upon. That “AP disconnect” command that TARGET sent out, the .key file interprets that and makes the sim/aircraft act accordingly. Press the pickle button on the stick and TARGET sends out a DirectX input which the .key recognizes and interprets that as “pickle”
So you see, both TARGET and .key file work similarly.
You mentioned you changed the Trim button to work properly. How did you do that? Because before when I used it it was PoV. Now, after your change and without any input from me, it has changed to work trim. What did you do exactly to change that? Because that is probably what I need to do to the whole profile to correct it.
The TRIM functions on the .key file was based off the original Pitbuilder.key settings. I ported over Morphine’s settings and that made it work properly again. Your “input” was to download and place the correct .key file and that “fixed” the trim for you. However, we are now both using the same .key file and my TM WH works perfectly and yours doesn’t so it’s not the .key file that you need to be worried about.
-
Ice, thank you very much for trying to help. I shall reply shortly with detail on what you ask. I do want to crack this as your profile is superb and I must be able to use it in with the WH. Pls stand by.
Apoll
-
NP, take your time. As long as we sort it out before 4.34
-
i guess i’m not completely against TARGET , i’ve just never needed it other than to turn of the WH throttle LED’s.
I’ll be honest after taking a look at the keyfile in notepad ++ , i have a bit to learn on manually editing this
I have absolutely no problem editing all the switches to touch in helios per every profile update no matter how often they are released - its worth it.
Something happened to a setting of my touch screen that makes swiping almost impossible as it used to work fine, So touch has been my work around.
If you have any thoughts on how to fix this, i’d be willing to listen.Will flaps control be added back in?
Is the goal to build a fully functional TAGRET file?