Ice’s Falcon BMS Profile Updated for BMS 4.37
-
Thanks @linknet, worked like a charm, I did have to change what it is looking for in the first “x” characters of the theater name as it is actually called 1982 Battle for Suez, so changing the lookup to “1982” did the trick. Thanks for the insight on that one. I should have looked a little closer when I was doing it but ran out of time. What is the reason for limiting the length to check only the first few characters and not just return the full name and match the full name? Is that just to optimize the execution or is that to do with the theaters having different name lengths and there would be a problem to return 10 characters if only 5 exist?
My next question which is really just an inconvenience as the work around is to manually copy the DDS files for the kneeboards from the KTO directory to the Suez directory. The issue is WDP doesn’t recognize the FO theater and I can’t update WDP like I just did for the charts in Helios. Since WDP isn’t able to update the kneeboards in the correct directory which is “Add-On 1982 Battle for Suez\Terrdata\objects\KoreaObj” it only updates the DDS files in the standard KTO directory. Since Helios does pull the kneeboards from the Suez directory I am not able to get my own kneeboards unless I manually copy the DDS files from KTO to Suez. Is there a way to make Helios still update the kneeboards from the KTO directory even if it is running a non KTO theater? Doing this would just cause the in game kneeboards to display different images than the Helios kneeboards correct? Since I fly with pilot legs off them being different wouldn’t matter. How are the .jpg images in the “Documents\Helios\Images\FalconBMS Images\Kneeboards” updated from the Suez theater directory? Is that the AutoPadsUpdate.exe figuring out what the directory is for the Suez theater is or is it being done somewhere else?
Thanks
-
@zeek
You can just compare the full theatre name:elseif s == string.lower("1982 Battle for Suez") then theater = 6
But some of the theatre developers are in the habit of adding version numbers to the end of the theatre name so by using a subset of the theatre name the code doesn’t have to be changed each time a new theatre version is produced.
The AutoPadsUpdate.exe extracts the theatre name from the windows registry and combines that with the BMS Path provided as a parameter by Helios to obtain the relevant DDS files. So without a recompiled special version of AutoPadsUpdate.exe then a simple cmd file to copy across the DDS files would be the answer, which I’m sure you must have figured out already.
Alternatively I believe you can add theatres to WDP according to this discussion here:
https://forum.falcon-bms.com/topic/7/weapon-delivery-planner-released/2087
which I haven’t tried and can’t confirm whether it works or not. -
Hello guys,
Love the profile, many thanks to all the users involved in making it.I have a problem and I wish if you guys can help. @linknet @Wheelchock
When running the profile, at random time intervals, all lights and some instruments (for sure the altimeter) freeze. They come back after a random time interval or immediately after exiting falcon while the aircraft flies into the sunset.Have I setup something wrong? Is this a known issue? Thanks in advance!
-
@Raphael The most likely cause is having different refresh rates between monitors. I’ve experienced this before with a main monitor of 30hz refresh and a 60hz secondary monitor which is my touch screen.
-
Hi,
Can this profile read the current state/position of various buttons/knobs in teh cockpit?
Id yes how do you read it?
So far I could not find a way to do this to implement in my VoiceAttack plugin.Thanks
-
@janjan
BMS only exports a small subset of the knob and button positions and these are read by the Helios Falcon Interface plugin not by the profile itself. The Helios Falcon interface reads the BMS shared memory in order to extract the position values. -
@linknet
I use the shared memory but this has a very limited information regarding knobs and buttons position.
I want to know if you managed to find a way to read all other knobs/buttons position apart from the ones in the shared memory. -
@janjan
The profile uses the Flight Start Mode via Helios Shared Memory to set all of the controls that don’t have position information to the initial start position relevant to the flight mode, Ramp Start, Hot Start and Air Start. The profile then relies on the user adjusting the controls in the profile and not in BMS for them to remain in sync. There is no feedback for these so if adjusted in BMS then they lose sync. -
@linknet
Thanks, I was hoping someone found a way but no.
I do the same when I want to set a know - set it to a knows value and modify. -
Hi Linknet, I would like to report that besides RWR diamond float mode button and Radio Altimeter switch, the green oxygen regulator switch was also not in sync first time entering 3D.
-
@Todd1215 thanks for the suggestion but both my displays are set to 60hz. Any other suggestions?
-
@jacqueslees said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
Hi Linknet, I would like to report that besides RWR diamond float mode button and Radio Altimeter switch, the green oxygen regulator switch was also not in sync first time entering 3D.
Ok, thanks. I’ll check that out.
-
@Raphael when you have BMS in 3D bring up task manager and look at your GPU 3D utilization percentage. I was experiencing a delay in gauge movement when BMS was rendering at 4k and even with a 4070ti I found that BMS was pushing the GPU to 98% utilization. Helios needs a little headroom to operate in and a mean 2-3% wasn’t cutting it. Not until I had BMS render at 1440 did I get my smooth gauge movement back. So maybe look at that to see if it’ll help point out where the issue is.
-
-
Just curious if I’m the only one experiencing this, I occasionally get a popup alert when resetting the profile with an error message:
Line 12942 (File 'C:\Bin\AutoDataUpdate.exe)
Error: Unknown function nameI have the latest Helios version installed and everything seems to work fine in BMS and the touchscreen panel once the sim loads. Both types of kneeboards (BMS & WDP) seem to work fine. I can provide any additional information if needed.
-
@Slick8791-0 I’ve never experienced that before, can you determine whether the popup is generated by Helios or by AutoDataUpdate.exe, perhaps you could provide a screenshot?
However, whilst that shouldn’t happen, the question is why do you need to manually reset the profile. It shouldn’t be necessary and in fact can lead to the profile switches and knobs becoming unsynchronised with the controls in BMS. On starting a flight the controls are set for the corresponding flight start mode, Ramp Start, Hot Start or Air Start. Then on exiting the flight the profile is automatically reset. So there shouldn’t be any need to manually reset at any time.
-
@linknet I’ll try to grab a screenshot the next time it happens, but I did write down the exact text. I have my processes slimmed down so I was having problems grabbing the image.
I don’t typically do a profile reset so I may just be outside the normal (or way off on average) The Wife Unit isn’t due back home until tomorrow, so I should be able to test it again this evening and provide an update and any repro steps.
-
This post is deleted! -
@linknet Thanks, will do! I’ll try to provide an update this evening.
-
@linknet No issues at all today. Was able to load up and fly around. No errors when resetting either profile. I guess it was a one-time event but will let you know if it keeps happening. Thanks for the support!!!
-
Just installed Ice’s profile, It has come a really long way it is fantastic! I have spent many dozens of hours on my profile which is based on an early version on Ice’s profile and it doesn’t come close. Thank You!