-
Notifications
You must be signed in to change notification settings - Fork 39
Falcon Interface
The Falcon Interface provides a way of defining what key information is needed by Helios in order for the profile to interface with Falcon BMS successfully. There are many users that have multiple versions of Falcon BMS loaded at any one time so Helios needs to know the version of BMS you're using with the current profile. The version field helps Helios find the directory for key files and some other files as well.
The version combo box will always sort the installed Falcon BMS versions from highest numbers to lowest numbers. So 4.35 should come before 4.34 and so on. These values comes from the Windows registry.
Displays the currently selected pilot callsign in Falcon BMS. This value is taken from the Windows registry based upon what Falcon Version is selected in the Falcon Interface.
The key file text box allows you to select the key file that will be used with the current profile. The file selection button is to the right of the text box and when selected will take you to the user config directory of the currently selected Falcon BMS version.
This feature if checked will find the Falcon BMS window that is running and will force it into focus before sending a callback/keystoke to it. This ensures that if you've ALT-TAB'd out of the window for whatever reason that it is back in focus so any keystones that the profile sends isn't missed.
Force Falcon pilot callsign to use the key file defined within the current running Helios profile. This helps to ensure that Falcon BMS loads the same key file that the Helios profile has configured within the Falcon Interface.
Informs Helios that it should generate RTT Client configurations for the loaded profile.
Enables networking feature and connect to a remote RTT server.
The preferred renderer that will be used by RTT Client.
Use a simple grid pattern for the RWR RTT viewport.
How often should the client poll the RTT area to check for changes? The higher the value, the more GPU/CPU load you generate. Note that this value does NOT affect the smoothness of the display animations. The display can not draw more frames than BMS is currently exporting to RTT (which by default is BMS FPS / 2). This setting is only available when Networked is disabled
This is a Helios global setting that must be checked the first time the profile user wants to use a profile that has RTT Enabled defined within it.
Start the RTT Client automatically when the Helios profile starts.
Stop the RTT Client automatically when the Helios profile stops.
The IP Address of the remote RTT server.
The remote port of the RTT server.
If Networking has been selected you can choose to have the RTT Client mirror the shared memory areas of BMS, F4, OSB, and iVibe.
Once the key file is loaded into the interface the Falcon Interface will determine if there are any callbacks that are used in the profile that are not present in the key file. This will ensure you are aware of any bindings that may not work when selected. Any missing callbacks will be noted on the Interface Status page
Download latest Helios from this repo