Ice’s Falcon BMS Profile Updated for BMS 4.37
-
@linknet Where does the generated files go?
-
@Atlas C:\Bin\KneePads
-
@linknet I’m sure you meant C:\Bin\KneeBoards, however, the left and right sheets are in one image? Is there one where the left is separate from the right? Either here or on AutoKneePads?
-
@Atlas
No, I meant exactly what I said, they’re in C:\Bin\KneePads - which is created after running the profile for the first time.Same in AutoKneePads except that they’re in AutoKneePads\KneePads, again created after first run.
-
@linknet I definitely don’t have KneePads. I just ran the profile again, “printed” out the briefing, but no folder.
-
Then the profile isn’t set up correctly, the first thing that C:\Bin\AutoDataUpdate.exe does is create that folder:
Global $sKneePadsSavedPath = @ScriptDir & "\KneePads\" If Not FileExists($sKneePadsSavedPath) Then DirCreate($sKneePadsSavedPath) EndIf
Therefore you need to investigate the reason for AutoDataUpdate.exe not running when the profile is started.
Check for Process Control enabled and a valid command to start C:\Bin\AutoDataUpdate.exe at profile start.
Check for blocked files, run the UnblockFiles.exe.
-
@linknet
I have a guest today and I was showcasing Falcon BMS with the Helios setup and this time the HUD floating inside DED and MFD issue is becoming unbearable. It happened so often that I cannot use the MFD at all. We tried TE1, TE2, LGB, everytime right after several minutes into the mission.
It’s completely unable to do the LGB TE because of this. We found out that if we do some actions like lowering the gear MFD reappeared, only to be covered by floating HUD 2 secs later.
Am I the only one to experience this at all? I just found out that 4.37 got an update I’ll report back after more testing. -
@jacqueslees said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet
I have a guest today and I was showcasing Falcon BMS with the Helios setup and this time the HUD floating inside DED and MFD issue is becoming unbearable. It happened so often that I cannot use the MFD at all. We tried TE1, TE2, LGB, everytime right after several minutes into the mission.
It’s completely unable to do the LGB TE because of this. We found out that if we do some actions like lowering the gear MFD reappeared, only to be covered by floating HUD 2 secs later.
Am I the only one to experience this at all? I just found out that 4.37 got an update I’ll report back after more testing.I replied to this issue 16 days ago when I explained that this was a Helios issue and nothing to do with the Ice Profile. I then also suggested reopening the following Helios issue - https://github.com/HeliosVirtualCockpit/Helios/issues/598.
That’s the correct place to report the issue and is the only place where you might get some answers. The MFD textures are generated within Helios not in the profile.
-
@Todd1215 said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@jacqueslees I have put together a fix for the scrambled Helios Falcon textures (MFDs,DED, RWR, etc )
Download the following zip file and unzip it to a folder. Copy the HeliosFalcon.dll file from the extracted zip file folder and place it in your Helios plugins directory. This directory is located under your Helios installation folder. Make sure you BACKUP your current HeliosFalcon.dll file before copying in the new DLL file.
This fix is compatible with Helios 1.6.5306 and newer.
This is just a quick fix and once the next release of Helios drops this DLL file will get replace with the latest version for the release.
Hi Todd, I need your help here again, could you reopen the issue report in Github? This is happening all the time now, I tested with 4.37 update 1, it becomes better, recovered itself from the scramble and didn’t happen after the first occurance.
I’ll do more tests now, and thanks Linknet, I just thought it might be universal now and curious why I’m the only one to report this behavior -
@jacqueslees You should be able to reopen the issue yourself, just restate the problems you’re having and select the ReOpen button. Particularly as more information might be required to determine the cause of the problem.
-
@jacqueslees please re-open the GitHub issue and provide a clean set of logs when the issue is occurring. The Helios logs can be found under Documents/Helios. In addition to that please provide what TE you are experiencing this issue in. Is it all of them, only some of them like the GitHub issue states. In order to get to the root cause we need details and lots of them. I personally have not seen this issue and I don’t think allot of others have either or else I’d see lots of reports of this problem which I do not see. My suspicion is that this is occurring only in Airstart TE’s, as Helios is already running prior you going into 3D in BMS. Once you go into 3D the Flying flag is set but possibly BMS hasn’t populated shared memory yet with the area for each window extraction which is why you see all of them in the MFD’s. I believe this issue is a one off problem having to do with your setup. If this is really bugging you just switch to using RTT instead of Helios Textures. It’s really easy with Linknets BMS profile and Helios. He has it documented in is profile zip file.
-
@Todd1215
I just created a Github account to try but I cannot reopen the issue, but I did left a remark. And thinking of what you mentioned if it was an one off issue then probably it was the way that I run Helios?
I always run TrackIR and Helios Control Panel first, then launch BMS, and after I click commit and BMS went to the actual in game resolution and loading, I click on the start button on the Helios Control Panel. This way when BMS finally loads up my touchscreen is also ready to fly. I can start the profile later, but not before, because the UI used to have a different resolution and it would not match the resolution I set in the profile. Could this be the reason for the problem?https://drive.google.com/file/d/1noUNVn6nAXVVHCERTw2hLd96CHGrHSGx/view?usp=sharing
This are the 2 Helios logs and 1 BMS log, where it crashed, all while we were doing the Laser Guided Bomb TE. Floating HUD while we are preparing the mission and unable to use the MFD on Helios. We lowered the gear and it could bring back the MFD for 2 seconds, then it went back to the floating HUD. We did it like 7 to 8 times and finally dicided to leave it and right after we hold down Pickle to be ready releasing the bomb BMS crashed.
-
@jacqueslees @Todd1215
I’ve reopened the https://github.com/HeliosVirtualCockpit/Helios/issues/598 issue on GitHub so that the discussion can be continued there which will make it easier to keep track of all the comments.
-
Ice’s Falcon BMS Profile Updated to 4.37-04
Updated 13 February 2023:
The first post has been updated with the latest version.
Please note the requirement for BMS Falcon 4.37 U1 and Helios Version 1.6.5900.1 or later.
Important: After installation run C:\Bin\UnblockFiles.exe to unblock all files.- Updated for BMS Falcon 4.37 U1 and compatible with Helios version 1.6.5900.1 or later. Note: Not compatible with earlier Helios versions.
- Requires “set g_bExportRTTTextures 1” to be added to the “Falcon BMS User.cfg” file found in \User\Config.
- Requires “set g_nKnobAccelerationDelta 0” to be added to the “Falcon BMS User.cfg” file found in \User\Config.
-
Hi, very good job at first -> @linknet. Could you please help me when i want split solo ECM panel to fit my 5 inch smart phone ? I tried to extract the code from config file and put it on solo profile but no luck. Thanks for any hint.
-
@Fox_518 Open the Combined Console panel then unlock and select the ECM panel. Then just copy and paste the ECM panel to a location that you have already selected. If this is to a completely new profile you need to install the Falcon Interface in that profile before copy and pasting else you will lose all of the bindings.
-
Any idea why I get this “warning”?
GadrocsWorkshop.Helios.HeliosProcessControl.ProcessControlInterface|Profile attempted to start a process ""C:\Bin\AutoDataUpdate.exe" "%BMSFalconPath%" "%HeliosPath%"" but this action is not permitted on this machine|
Doesn’t stop the profile loading.
-
@CriticalMass
Did you follow this in the Setup Guide?i
-
@linknet
Apparently not.I’ve recently got a new computer and I had copied the profile over - my assumption (I know) was that that was all that was needed.
I checked, and it wasn’t selected, but I can’t confirm fully as I don’t have access to my “pit” setup right now.
TANX!
-
Ice’s Falcon BMS Profile Updated to 4.37-05
Updated 05 March 2023:
The first post has been updated with the latest version.
Please note the requirement for BMS Falcon 4.37 U2 and Helios Version 1.6.5900.1 or later.
Important: After installation run C:\Bin\UnblockFiles.exe to unblock all files.- Updated for BMS Falcon 4.37 U2 and compatible with Helios version 1.6.5900.1 or later. Note: Not compatible with earlier Helios versions.
- Updated the key file to include the latest callback changes.
- Added all of the latest updated Korea charts.
- Updated the Comms Menu with the latest ATC changes.
- Requires “set g_bExportRTTTextures 1” to be added to the “Falcon BMS User.cfg” file found in \User\Config.
- Requires “set g_nKnobAccelerationDelta 0” to be added to the “Falcon BMS User.cfg” file found in \User\Config.