Helios 1.6.3605 Release - Supports RTT Configuration & launch control
-
Hello BMS users,
I am proud to announce that Helios 1.6.3605 is generally available for all users to upgrade to if you haven’t already. Helios 1.6.3605 brings some significant updates for Falcon BMS users in addition to some very much needed bug fixing and core upgrades. See the list of changes here. Please note the change log says 1.6.3604 which is just an earlier minor build of 1.6.3605. Nothing new between the two, just ironed out some issues.
Whats NEW !!
- Falcon BMS RTT is fully supported for configuration and control from within the Helios profile. I created a youtube video to explain how to enable , configure , and control RTT within a Helios profile.
- Added MapControl and MapViewer to provide moving maps, waypoints and pre-planned threats curtesy of (linknet). So no more having to add tons of map images and crazy configurations to your profiles. Just drop the Map Control on to a profile and bind a few inputs and done. Now you have a moving map. Demo Helios Profile provided here
- Exposed as a binding the Current Theater Name
How to get the new release.
- If you are currently running a Helios 1.6 release version just simply open up the Profile Editor and a version check should occur prompting you to download the latest version.
- Download the latest version from the GitHub page located here
LINKS
ChangeLog
Download
Demo Helios Profile for MapControlIf you have an issue or questions you can find me here on BMS forums or shoot me a message on discord here
Enjoy your new toys!
-
Awesome!!! This is going to help a lot!
:yo:
-
Very nice news. Thanks for the work on this.
-
Hi there. im trying to use Ice’s helios profile running on my networked laptop with touchscreen. but when i run the profile i get a msg saying that the RTTclient 64bit Error, configuration not complete. im using the newest helios that is meant to configure rtt for you. any ideas what i need to do?
-
After starting the profile via ControlCenter can you turn on the control center console and select the Share button at the bottom. Then click the copy to clipboard button and past the code here in this thread. I might need some more log files but this is a start.
-
Hi Wheelchock
I already checked your video about RTT ant it is working fine.
But I didn’t find any guide to how to use the MAP CONTROL function. I see several options on Input/Bidings (North up, Bullseye visible, Map Scale, etc…) But I don’t know how to make it work. I put the map control window on my screen but it only shows NO FLIGHT DATA in red even when in 3D.
Obviously I am missing something.Glad any help and thanks for the video.
cheers :yo:
-
Hi Wheelchock
I already checked your video about RTT ant it is working fine.
But I didn’t find any guide to how to use the MAP CONTROL function. I see several options on Input/Bindings (North up, Bullseye visible, Map Scale, etc…) But I don’t know how to make it work. I put the map control window on my screen but it only shows NO FLIGHT DATA in red even when in 3D.
Obviously I am missing something.Glad any help and thanks for the video.
cheers :yo:
It’s intended to be included in a profile with the Falcon Interface added, that’s where it will get it’s flight data from. Then you need to create buttons in the profile and assign them as below to access all of the options.
. -
It’s intended to be included in a profile with the Falcon Interface added, that’s where it will get it’s flight data from. Then you need to create buttons in the profile and assign them as below to access all of the options.
.Thanks. Got it.
I thought it would extract the position automatically into the map. My mistake.:yo:
-
Hi Wheelchock
I already checked your video about RTT ant it is working fine.
But I didn’t find any guide to how to use the MAP CONTROL function. I see several options on Input/Bidings (North up, Bullseye visible, Map Scale, etc…) But I don’t know how to make it work. I put the map control window on my screen but it only shows NO FLIGHT DATA in red even when in 3D.
Obviously I am missing something.Glad any help and thanks for the video.
cheers :yo:
yeah linknet is the author of those controls…so it sounds like he needs to create an instructional video on the subject…LOL
-
All right, thanks
What I didn’t figure out yet is how to make the MAP/aircraft position available in my profile. I am sure it is very easy and obvious but it evades me.
If you are willing to provide a simple step by step on how to make the map/position work it will be kindly appreciated.Anyway, thanks for your contribution for the community.
:yo:
-
All right, thanks
What I didn’t figure out yet is how to make the MAP/aircraft position available in my profile. I am sure it is very easy and obvious but it evades me.
If you are willing to provide a simple step by step on how to make the map/position work it will be kindly appreciated.Anyway, thanks for your contribution for the community.
:yo:
Here’s a demo profile which demonstrates the MapControl and the MapViewer in a simple profile, working through that in the profile editor should give you some guidance on the method of use.
https://www.mediafire.com/file/rixlnpbdnrdyo1k/MapControlViewerDemo.zip/file
You just need to add the MapControl or MapViewer to a profile which has the Falcon Interface added, the aircraft and position on the map will be automatically extracted from the Falcon Interface. You then need to set up inputs from buttons, switches or knobs of your choosing to enable the various options. The map will auto-select based on your current theatre.
The MapControl will always show NO FLIGHT DATA until you actually fly.
The MapViewer works by just tapping on the map to zoom in at that location and tapping again to return. If you draw the MapViewer control with a visible border then tapping on the border will hide the control. You also need to set up a separate button to show/hide the control.
-
-
Just watched a short video
on the implementation of RTT into a profile, very well done guys! Saves the steps of running\stopping RTT separately. I currently have the older CPD displaying on the right side of my triple screens and it works fine as long as I remember to Print the Briefing and Save the DTC but it sounds like you have improved that substantially also, so I would like to add that to my current profile if possible… Will it just pull the data from BMS without the Print/Save? -
Just watched a short video
on the implementation of RTT into a profile, very well done guys! Saves the steps of running\stopping RTT separately. I currently have the older CPD displaying on the right side of my triple screens and it works fine as long as I remember to Print the Briefing and Save the DTC but it sounds like you have improved that substantially also, so I would like to add that to my current profile if possible… Will it just pull the data from BMS without the Print/Save?The new MapControl pulls all of the data from shared memory without the need to Print the Briefing and Save the DTC. However the new version of the CPD still requires you to Print the Briefing and Save the DTC to update the Plan data. Although there is no longer any need to press the Helios reset.
-
The new MapControl pulls all of the data from shared memory without the need to Print the Briefing and Save the DTC. However the new version of the CPD still requires you to Print the Briefing and Save the DTC to update the Plan data. Although there is no longer any need to press the Helios reset.
W00T!! :headb:
-
Just downloaded the 4.35-9 profile and figured I would create a new profile based on it (just pulling some gauges onto my MFD screens and the CPD Map onto my main monitor) but I don’t see anything different as far as the CPD Map display or buttons, and i’m a bit confused about what, if anything I need to do to get the new map and associated controls onto my main screen. Gauges and the RTT MFDs on my lilliput’s, no issue…
-
I’m new to Helios, are on-screen controls (specifically MFDs’) available in this app? I have a touch screen Surface which I want to use as an MFD controller. I’m sorry if it’s been already said, but by a quick view there’s no mention of this feature.
-
Yes MFD are part of Helios. Basically any in/output from the cockpit is available
Gesendet von meinem SM-G930F mit Tapatalk
-
Forgive the question here, but I experienced an error with the Pilot’s Callsign not being set. I’ve been using the latest Helios version without issue with both Wheelchocks F-18 and Ice’s F-16 cockpit profiles. But now, as of last night, I get an error stating that “Pilot Callsign not set in BMS”. Of course I can by-pass it, but still it’s a bit annoying. The status report is below for Wheelchock & company to see if there’s anything wrong with my install.
{ "Product": "Helios", "Version": "1.6.3605.0", "Items": [ { "Report": [ { "TimeStamp": "09/18/2021 09:15:49.817 AM", "Status": "Loading Profile..." }, { "TimeStamp": "09/18/2021 09:15:50.390 AM", "Status": "Selected Falcon interface driver is 'BMS' version 'Falcon BMS 4.35'", "Flags": 2 }, { "TimeStamp": "09/18/2021 09:15:50.390 AM", "Status": "The key file configured in this profile is 'C:\\Program Files\\Games\\Falcon BMS 4.35\\User\\Config\\Jolly's Warthog Helios Profile.key'\n", "Flags": 2 }, { "TimeStamp": "09/18/2021 09:15:50.390 AM", "Severity": 2, "Status": "Pilot Callsign not set in BMS", "Recommendation": "Run Falcon and set your pilot callsign" }, { "TimeStamp": "09/18/2021 09:15:50.391 AM", "Severity": 2, "Status": "Failed preflight check.", "Recommendation": "Please resolve problems or disable preflight check in preferences." } ], "Name": "Control Center Console" } ] }
UPDATE: The issue seems to have fixed itself. But still would like to know how Helios identifies the particular Logbook in use. I use 2 seperate logbooks: 1 for flying an F-16 (TM Cougar) and 1 for flying the F-18 (TM Warthog)…so I’m a bit concerned if Helios identifies the wrong logbook.
Cheers
-
UPDATE: The issue seems to have fixed itself. But still would like to know how Helios identifies the particular Logbook in use. I use 2 seperate logbooks: 1 for flying an F-16 (TM Cougar) and 1 for flying the F-18 (TM Warthog)…so I’m a bit concerned if Helios identifies the wrong logbook.
Cheers
It just checks this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Benchmark Sims\Falcon BMS 4.35\PilotCallsign