Ice’s Falcon BMS Profile Updated for BMS 4.37
-
This post is deleted! -
Ice’s Falcon BMS Profile Updated to 4.36-05
Updated 13 December 2022:
The first post has been updated with the latest version.
Please note the requirement for BMS Falcon 4.36 U3 and Helios Version 1.6.5500.0 or later.
- Added all of the BMS Falcon 4.36 U3 updated charts for Japan, China and Russia.
- Added all available updated charts for the latest Balkans and Israel theatres. The Airports all have an Airport Chart but most of the DEPARTURE/TACAN/ILS charts are still missing.
- Removed the Nordic theatre charts since the latest charts are now in a format which is incompatible with the format used in this profile.
- The RPM Gauge now automatically sets the correct GE/PW version based on aircraft type.
- The Fuel Gauge now automatically sets the correct LH/RH needle fan based on aircraft type.
- The IFF/AUX COMM panels are now automatically selected based on aircraft type.
- The Air Brake Indicator on the Landing Gear Panel now shows the actual Air Brake position via a moving tape.
- Selecting the hidden button on the Landing Gear Panel Air Brake Indicator now toggles the Air Brake Open/Closed.
- The Caution Panel now displays for a few seconds for each new fault detected.
- The profile now checks for an incorrect Helios version and notifies the user accordingly.
- A notification from “DataAutoUpdate” that the Arial Narrow font is missing is included.
- This latest Helios version adds %BMSFalconPath% and %HeliosPath% environmental variables to the Process Control interface. All of the executable files in the C:\Bin folder have therefore been modified to access the required paths via command line parameters sent from the Process Control interface. None of the executables can now be run as a standalone application and the “PathNames.ini” file is redundant and has been removed.
- The standard profile can now use RTT MFDs for both the Centre Console and the Zoomed Console without the need for an additional profile. The full setup instructions to enable this are provided in the separate Setup Guide. If you aren’t experiencing lagging MFDs then it isn’t recommend changing to this since there wouldn’t be any advantage.
- Requires “g_bExportRTTTextures 1” to be set in the Falcon_BMS.cfg file found in \User\Config.
- Requires “set g_nKnobAccelerationDelta 0” to be added to the Falcon_BMS.cfg file found in \User\Config.
-
Hi @linknet
I just installed your new profile and the latest Helios, but I’m getting this screen when save the profile
any ideas?
-
Any Ideas? Yes, just follow the instructions on the screen. In particular the final instruction.
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
Any Ideas? Yes, just follow the instructions on the screen. In particular the final instruction.
well, I tried those before posting here.
I just kept trying, at least four times, until it finally worked. It did throw a couple of exceptions (log file attached).
One this I did change, on reflection, was I changed the profile editor to NOT run as admin - I had recently changed Helios control center to run NOT as admin/#. would the mismatch have made a difference
2022-12-17 13:47:00.9393|ERROR|GadrocsWorkshop.Helios.ProfileManager|Error saving profile|System.IO.IOException The process cannot access the file because it is being used by another process. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost) at GadrocsWorkshop.Helios.ProfileManager.SaveProfile(HeliosProfile profile) 2022-12-17 13:47:00.9713|ERROR|GadrocsWorkshop.Helios.Windows.ExceptionViewer|Unhandled exception occurred. Helios will exit.|System.Exception There was an error saving your profile. Please contact support. at GadrocsWorkshop.Helios.ProfileEditor.MainWindow.WriteProfile(HeliosProfile profile) at GadrocsWorkshop.Helios.ProfileEditor.MainWindow.SaveProfile() at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e) at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding) at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute) at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute) at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated) at System.Windows.Input.CommandManager.TransferEvent(IInputElement newSource, ExecutedRoutedEventArgs e) at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e) at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised) at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args) at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated) at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(ICommandSource commandSource, Boolean userInitiated) at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
-
Well, I tried those before posting here. Sorry but just had to check.
The error log shows a problem in saving the profile (file in use), maybe windows had blocked the file as coming from an unknown source. In which case the profile editor in non-admin mode would have problems saving it. Edit: Just tried that, it saved it without any problems.
Whether it is saved in admin or non-admin mode shouldn’t make the slightest difference.
-
In the new 4.36-05, “BMS - Ice’s Helios Profile” key file (unmodified), everything works great for me, EXCEPT the C&I knob will ONLY move from UFC to BackUp, but NOT from BackUp to UFC. The “in-game, on-screen” cockpit C&I knob works both ways, OK, but the “touchscreen” C&I knob only works one way, from UFC to BackUp. Then it gets stuck on BackUp and won’t change back.
I checked the settings in the Profile Editor and they seem right, but it still only works one way (UFC to BackUp).
Is this a Bindings problem on the Knob CNI layer?
Has anybody else experienced this? If not, any ideas what might be causing this?
Thanks! -
@Dan I’m answering this as I understand the problem to be that the touchscreen knob itself gets stuck and not that the touchscreen knob moves but then doesn’t move the in-game knob.
Those knobs on the IFF and AUX COMM panels haven’t been changed for a long time. I’ve just checked them both out and everything looks fine. The knobs are set to “Continuous” and “Touch on right to repeatedly increment or on left to repeatedly decrement” together with “Mouse Wheel” enabled.
So effectively that means that a touch (not a swipe) anywhere on the knob should flip the state back and forth, also with the mouse pointer over the knob the mouse wheel should flip it back and forth.
-
Thanks link.
I went through all the running processes to see if any were Helios related (including text editors etc.) but couldn’t see anything. As I said I opened and closed the profile a few times and eventually it started to work again- a big sigh of relief: it was probably one of those Windows things - turning it off and on again would probably have worked too
-
@linknet
It’s hard to describe accurately but the C&I from the touchscreen doesn’t operate the “in-game” UFC position, only the BackUp position. This leads me to believe it’s a problem or conflict in the key file but I have to check it out to see. All I have done to the base Ice’s profile is add my Cougar lines at the end. If I find anything unusual or any conflicts, I’ll let you know.
Thanks! -
@Dan Download and run this then just start the profile alone and toggle the C&I knob:
https://www.mediafire.com/file/ew1r8m4sawacwl5/EventTester.exe/file
You should get this result:
Close that and then just run BMS alone and try inputting Left-Ctrl-F5 and then Left-Alt-F5 from the keyboard and check that the in game C&I Knob flips back and forth.
-
@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