Helios 1.6.3605 Release - Supports RTT Configuration & launch control
-
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
-
IF you switch callsigns in BMS while Helios profile is running it will not pickup the change. You would need to stop and start the profile for Helios to reread the callsign out of the registry
-
It just checks this registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Benchmark Sims\Falcon BMS 4.35\PilotCallsign
IF you switch callsigns in BMS while Helios profile is running it will not pickup the change. You would need to stop and start the profile for Helios to reread the callsign out of the registry
Copy all. Thanks to you both. :thumb:
-
This post is deleted! -
This post is deleted! -
<blockquote>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?</blockquote><p><br />@pimpinwilly83 @Wheelchock <br /><br />Same problem and what i figured out is when Helios rewrites RTTclient.ini, two things were causing the error and not allowing RTTClient to run for me.<br />1. when it poputaled the new value for Line “DATA_OBS = 1”, it writes “DATA_Obs = 1” into the .ini file. when i corrected to “DATA_OBS = 1” (OBS all caps) the ini works fine.<br />2.when writing the RTTClient.ini file, it leave out “STRING_STR = 0” and “STRING_DRW = 0”, without these 2 values included in my ini file, RTT will not run.<br /><br />I dont know how to change the way Falcon interface creates the RTTClient.ini file, but it would be nice to have this option for me as i change aircraft and have to manually change the file for the different layout.<br /></p>
-
<p>I’m currently running Helios version 1.6.5101, with the Ice’s 4.35-11 profile.<br />Does this “new” Helios release (1.6.3605, with a <u>smaller </u>number), replace 1.6.5101?<br />My Profile Editor says 1.6.5101 the most current. Is this because there is a different Helios for RTT support?<br />I’m a little confused…<img src=“/plugins/nodebb-plugin-emoji/emoji/android/1f615.png?v=cn1jopfllvk” alt=“” class=“not-responsive emoji emoji-android emoji–confused” /> </p>
-
<p>Sorry!<br />I thought this was a new post. Pleased disregard!</p>
-
Bug with Helios 1.6.5306.4 in BMS 4.36.1:
As described here:
https://forum.falcon-bms.com/topic/23208/shared-memory-vs-sec-checkDuring ramp start I make the engine sec. check according to checklist. As soon as the nozzle closes every part of my display extraction (RWR, DED, PFD, MFDs) changes to HUD.
-