Ice’s Falcon BMS Profile Updated for BMS 4.37
-
@linknet
Here’s what I’m getting in the Event Tester, using the touch screen.
As you can see, the F5 keypress after LALT is not happening, even though the key file shows it should be working.
CTL-F5 works fine, but ALT-F5 does not, in BMS or on the touchscreen.
When I use the mousewheel in BMS alone, the knob changes perfectly.
I ran a Notepad++ search for any duplicate commands (125 0 0x3F 4 0 0 1) in the keyfile, but found none). I also tried other keyfiles in BMS that toggle the C&I knob (CTL+SHFT+F1) and they work OK.ALERT! Another Helios update just came out! v. 1.6.55.01. Did they find a problem? Should I update again?
-
PROBLEM SOLVED! It turns out that I had “Nvidia Geforce Experience” in-game overlay turned ON, which caused it to “take over” the ALT-F5 command and cause me this grief.
If anybody with an Nvidia card has a keyboard command issue, you might want to verify that any in-game overlay is OFF! -
Greetings all -
Regarding the Alternate Launcher, is there anything specific about that app which specifically requires the BMS-Auto keyfile?? Reason I ask is I have changed my Helios panel’s keyfile to “BMS-Auto”, just as it states in the instructions (even placed a copy in the Bin folder), but when I’m in the 'pit nothing on the Helios panel works. Just wondering where I went wrong…
Thanks,
Jolly -
@JollyFE
I don’t use AL and therefore have no experience with it but I’ve been assured that the instructions from Post 2 and also in the Setup Guide actually do work.
Essentially the “BMS - Auto.key” has to be a renamed copy of the “BMS - Ice’s Helios Profile.key” and then you point both BMS and the Profile towards it.If using Alternative Launcher and/or needing to change keyfile bindings:
- Copy the “BMS - Ice’s Helios Profile.key” from the Setup “Helios Full Profile Setup\FalconBMS Keyfile” folder to the “Falcon BMS\User\Config” folder.
- Add your HOTAS bindings to the end of this keyfile and rename it to “BMS - Full.Key” after renaming the existing “BMS - Full.Key” to “BMS - Full - Backup.Key” or something similar, or to “BMS - Auto.key” if you are using Alternative Launcher 2.0.
- Now point both the Helios profile and BMS to either the “BMS - Full.Key” or the “BMS - Auto.key” as appropriate in the “Falcon BMS\User\Config” folder.
-
@linknet Thanks for the reply. I will tool around with it more and see where I went wrong.
Cheers
-
https://forum.falcon-bms.com/post/359604
Just an FYI with 4.37. I have been testing it for the past week and I am having issues with Helios with my…“modified version” of Ice’s profile. Essentially I can receive all the extracted data, but no call backs work. None of the buttons or switches! I’ve used both the original BMS launcher & the Alternate Launcher that is now included with 4.37.
It is very frustrating to say the least! So be prepared for no Touchscreen inputs and be patient! AND Please post here, anything you all have done to get your Helios profile to work with 4.37!
(NOTE: I have not attempted to use 4.36-05 yet. I believe my modified version is from 4.36-01).
Cheers,
Jolly -
@JollyFE - I was able to get my modified 4.36-01 version of Ice’s profile working. Don’t tell the Devs but as a temporary workaround I did a compare of my 4.36 Keyfile to the 4.37 Keyfile and added the new callbacks in the 4.37 Keyfile to the 4.36 Keyfile and then loaded that up in 4.37. just did a quick test and Helios is working as it should be. Since I use alternate launcher it is the auto keyfile. I can send you a copy if you want to hack it that way until new proper keyfile is released by Ice for 4.37 and Helios.
-
@zeek I appreciate the offer Zeek, but it may just be my “Frankenstein Version” of Ice’s Profile. Since no other Beta Testers use Helios I couldn’t duplicate it elsewhere, but glad it’s not as big an issue as earlier perceived.
EDIT: So a bit more info, if anyone else has experienced something similar, when touching anywhere on the touchscreen it translates to the cursor on the main screen (in cockpit). My Keyfile works fine as I can actuate all the buttons & switches with the keyboard, plus the Mouse Button is disabled. Not sure what I did, or what was changed with adding VR support, but whatever I’ve tried has been for not!
UPDATE: So I’ve had some luck with trouble shooting, in the form of uninstalling and reinstalling 4.37! Not 100% sure why, but I do believe it has something to do with the Alt Launcher and the Auto Keyfile that it generates. Why the Alternate Launcher instructions, noted above, did not work for me is still a mystery, but keep this in mind if you encounter issues with your Helios profile not working in the cockpit.
Cheers,
Jolly -
@linknet - You are probably working on an update already and all this will be for not, but I am curious in learning how Helios does what it does, so I am trying to add the USAF – ECM POD Control Panel to the profile I am running.
When trying to add animation to the Program in Standby, Program is Active, Program is Transmitting, and Fault indicators I don’t see an input interface from falcon for those. How does Helios know what input interfaces exist in Falcon? Does that come from the version of the Helios application, and newer versions of Helios add additional input interfaces from BMS as they become available and we have to wait on a new version of Helios to get this working, or does Helios pull those from BMS automatically, or are they manually configured somewhere? Currently under the Input/Interfaces/Falcon/ECM interfaces I only see power indicator changed and fail indicator changed as the available ECM input interfaces. Am I looking in the wrong location to animate those ECM program indicators or do we just need to wait on an updated version of the Helios application that will add those input interfaces?
Thanks
-
@zeek You’re looking in the correct place. Helios extracts the data from shared memory but this isn’t automatic. The new data in shared memory has to be added as bindings to the Falcon Interface code base. So a new version of Helios is needed before you see any of this data.
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
The new data in shared memory has to be added as bindings to the Falcon Interface code base.
Thanks, will keep an eye out for an update, until then will just have to struggle with trying to click it with the mouse in the pit.
-
Mr. Ice - This is FREAKING AWESOME !!! Words can not fully communicate how much I love this…totally solves all the “issues” I had with Falcon BMS and makes flying a zillion times more intuitive and fantastic. Much closer to flying the actual jet. If you are ever in Missouri USA I’ll buy you a steak dinner ! THANK YOU !
F-Bear
-
-
@FBear My rhetorical question for you is, Why didn’t you know about this before?!?! This has been around for years!!
-
@linknet I am having the problem again with the kneeboards updating. It looks like it is that same problem as last time where the KneeBoardsUpdate.exe is hardcoded to the 4.36 directory. Is it easy to provide a quick update to that exe? If not as a workaround I can just run an older version of WDP that is pointed to 4.36 to update the kneeboards so Helios can pull it from the 4.36 directory.
-
@zeek said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@linknet I am having the problem again with the kneeboards updating. It looks like it is that same problem as last time where the KneeBoardsUpdate.exe is hardcoded to the 4.36 directory. Is it easy to provide a quick update to that exe? If not as a workaround I can just run an older version of WDP that is pointed to 4.36 to update the kneeboards so Helios can pull it from the 4.36 directory.
In the latest 4.36-05 version of the profile the kneeboard updater path isn’t hard coded, the profile passes the most recent BMS path as a parameter to the updater. I’ve just tested the 4.36-05 version of the profile with BMS Falcon 4.37 and the kneeboard update is working fine. If you’re running this latest version of the profile and it still isn’t working just let me know.
-
-
@linknet - thanks, I see it now in the revision history. Guess I should have updated. Will do it with the 4.36 directory for now until the next version is released and then update.
-
@linknet - just getting back into BMS with the 4.37 release after some time away, updated my simple profile to point to 4.37, adjusted monitors, and all is error free. Issue is the MFDs do not display on my 2 Lilliput monitors. The other gauges I have on there are fine (Fuel Flow, RPM, Fuel, Compass, VVI) but no MFDs. For a quick fix I figured set them as hidden, then enable RTT, and RTT auto start/stop. Went into RTTClient.ini, set the positions where I wanted the MFDs, all good. Start my profile, I see RTT start but no video. I go and look at the RTTClient.ini and now it shows as "Created by Helios, both MFDs are set to “0”, and no coordinates, with a note not to edit it…
I can, once I disable RTT in the Helios profile, simply run RRClient64.exe using my original (I saved it) RTTClient.ini and it works perfectly, would rather have Helios run the show. What did I miss/mess up?
-
@Icer I’m sure you must have set this but just asking to make sure:
Add “set g_bExportRTTTextures 1” to the “Falcon BMS User.cfg” file
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@Icer I’m sure you must have set this but just asking to make sure:
Add “set g_bExportRTTTextures 1” to the “Falcon BMS User.cfg” file
Yes, and again RTT running on it’s own using my edited RTTClient.ini displays the MFDs fine, it’s just that if I set the profile to use it, it will start/stop RTT as expected, but it does not display anything and the RTTClient.ini Helios creates does not have the MFDs enabled…