-Ice's Falcon BMS Helios Profile Updated!
-
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
-
Let me know if you want any further testing done in certain areas…happy to do so.
Just go ahead and play. If you find anything broken or if you think something should be changed, I’m open to suggestions!
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
Thanks, glad you found it useful!
-
the Radar range isnt working
pseudo-fix now is that I’ve mapped the range knob up/down directly as button presses. I’m not sure if that’s realistic though; Morphine did his as an axis instead of a switch/button. How does this work in the real jet? Does anyone know?
Also, is it supposed to be able to adjust the HSD range as well? Or just the radar range?
-
Ice, missile override button forward and back on the throttle just flashes the two modes up, but does not stick. Goes back to Nav mode immediately. Am I doing something wrong?
apoll
-
the Radar range isnt working , but the HSD zoom in and out both work.
Apparently, the china hat WAS working as intended. How exactly was it not working for you?
Check out this thread
-
Ice, missile override button forward and back on the throttle just flashes the two modes up, but does not stick. Goes back to Nav mode immediately. Am I doing something wrong?
Are you talking about the MRM/DF override switch? The one below the speedbrake? Should be working fine.
Check out your falcon bms.cfg file and see if g_bHotasDgftSelfCancel is set to 0.