-Ice's Falcon BMS Helios Profile Updated!
-
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? -
Ok…
-
yes, WH has worked properly before, both out of BMS and inside BMS. For example, when I loaded Morphines key file, with no Helios, worked well.
-
yes, I use track ir.
-
don’t know about write protecting the joystick filed et al. I certainly have not done it. I will give your suggestion a whirl.
-
ok, I have a WH attached, Saitek combat rudder pedals, track ir of course, a Razor Orbweaver finger pad connected. That’s it.
-
I have tested the Helios profile. As far as I can tell, all works as intended in the Helios profile.
-
in the 2d UI of BMS in the controllers bit, when I pressed the DMS up, it would say button 45 pressed and for an LMFD sob function. DMS down, and another button 42 pressed which was another LMFD sob button press. They were all like that; for the left MFD. I found those buttons in the key file and sure enough, they were for a whole bunch of commands that pressed various osbs on the LMFD. I had to remap the DMS up push to the correct command according to the key file.
Anything standing out? It is like the stick mad been loaded with these crazy commands, and not the correct ones.
Apoll
-
-
i guess i’m not completely against TARGET , i’ve just never needed it other than to turn of the WH throttle LED’s.
You might not need it now, but the flexibility of the program is good to have. Heck, you could probably throw one switch… ONE switch… and a properly scripted TARGET line would do your rampstart for you. But that would be cheating.
I’ll be honest after taking a look at the keyfile in notepad ++ , i have a bit to learn on manually editing this
Like I said, tell me of any changes you do. I may incorporate it or even if I don’t, it might spark an idea that leads to something more useful (see post #94). I’m curious though… why would you need to edit 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.
I’d have to suggest you google that or query your screen’s manufacturer. One of the reasons the switches are swipe-operated is so that an inadvertent touch does not throw a switch by accident.
Will flaps control be added back in?
Is the goal to build a fully functional TAGRET file?Yep. I’m thinking FLAPS could be mapped to the LG lever. Much easier to use and it means the pilot does not have to go heads down during takeoff. See post #71.
-
Anything standing out? It is like the stick mad been loaded with these crazy commands, and not the correct ones.
Sounds like you have the wrong .key file loaded in BMS.
-
Here’s what it looks like with no Target profile running. TMS Up is recognized and it works. Note the dropdown list.
Here it is again with my Target profile running. TMS Up is recognized and it works. Note the dropdown now says Thrustmaster Combined.
Still, it shouldn’t make a difference as you can see that TMS Up works with and without Target profile loaded.
Which leads me to believe that the problem is not with the stick but with the .key file. -
You probably can with BMS, but I prefer a restart.
No. That was good advice. Restart them all (BMS and Helios)…
-
So i spent an hour flying using the target profile.
some things i noticed…
the Radar range isnt working , but the HSD zoom in and out both work.
The other is the mouse nub on the throttle for the cursor slew.
when i’m not using target both axis’s center when it is not touched in the BMS controller settings.
When i run the target profile the the X axis is fine but the Y axis is all the way to the right , cause the cursor to constantly pull in that direction.I may have something set up wrong - in the mean time i set the POV next to the nub as my cursor slew.
thoughts?
and i’ve added TARGET to my start up script that automatically launches all need application.
-
So, i’ve been doing some helios editing today after reading a different post ICE had been commenting in.
I have removed the mfd frame and the OSB buttons but left the invisible buttons. This has made my MFD’s so much larger, now per the other post, i just touch the words instead of a button.WIN!!
-
yeah, the red china hat isn’t working for me either. I’ll look into that.
As for the mouse nub, it should be working as intended. Maybe you need to “zero” or “center” your device?
Nice call on the MFDs but since my profile aims to look like an F-16 pit, losing the MFD “look” kinda ruins it for me. If it was an F-22 sim, then probably yeah. Personal preference.
-
ok glad to hear its not just me with the china hat!
i even went and calibrated the mouse nub and i got the same problem, and like i said it works fine with out target - so in the mean time i just made coolie hat the slew for now.
I’m so used to not pressing the OSB buttons using the VRS F-18 exports that this is second nature -lol
-
Hi Ice,
Thank you so much for your new Helios (and add-on’s) profile. As soon as I have time to install and give it a test-fly, I’ll post my feedback here.
Cheers
-
Ice, you know how I had the problem of the OSB commands being mapped to my WH? And could not work out why and what the problem was? Well, just saw this in the main BMS general discussion thread:
https://www.benchmarksims.org/forum/showthread.php?23624-OBS-buttons-bound-to-Warthog-by-default
That’s it!! That’s exactly my issue. And it looks like there is a cure which I shall try asap and report back. Posting this to save anyone else heartache should they strike the same problem.
Apoll
-
Correction: in the Warthog bit of the joysticks/input forums.
Apoll
-
All fixed! In the end, this problem was to do with the device order Windows and the BMS UI had allocated to the WH and other devices I had on the system, most significantly, the Orbweaver finger pad I had connected. Both the system AND very significantly, the BMS controller UI had made the Orbweaver the number one device. Once I fixed that with a little app called JoyID, and unplugged it to another port, the BMS UI no longer saw it as the first device, and the button order then worked. From the forums, it is clear I am not the first to suffer from this; there are lots of discussions regarding the WH and the device ordering problem once you know what to look for. I won’t be the last to experience; for newbies, this will be an intractable problem, and really needs a sticky AND prominence on the various forums.mas it is, one has to dig around smf ferret out the issue. I suggest it could be a barrier to growing our BMS community.
Regards,
Apoll
-
Glad you sorted it out apoll. Did you have Cougar MFDs plugged in as well?
In the end, it was a hardware issue, eh?
-
Yes Ice. Hardware issue Nothing at all wrong with your excellent profile. But it’s a common hardware issue for sure; the forums are full of it for WH and Cougar owners. Thanks for your efforts; much appreciated. Now I can crack on and actually start learning this beast! Let me know if you want any further testing done in certain areas…happy to do so.
Apoll