Ice’s Falcon BMS Profile Updated for BMS 4.37
-
OK, thanks for the information. Shame about the kneeboards, I think it must be something to do with your setup but I’m afraid I have no idea what.
no problem…I have edited your profile a little bit to use the images from ezboard tool as workaround…
-
Ice’s Falcon BMS Profile Updated to 4.35-10
Updated 30 Aug 2021:
The first post has been updated with the latest version.
Please note the requirement to copy the included HeliosFalcon.dll to the Helios\Plugins folder.
-
…are there any changes in the BMS keyfile since version 8?
-
…are there any changes in the BMS keyfile since version 8?
For the CPD Only Version - Yes, for the Full Version - No.
-
Hi, great work again, thanks.
Two questions though:
1. and most important: the startup mde is not recognized (and yes, I copied the Helios Falcon.dll to the correct folder). The profile always shows all knobs and switches in the taxiway/flight positions. Any suggestions? Is the a special orer in which to start the profile and the sim?
2. Do I really have to use the supplied key file or can I switch the profile to my usual key file? The reason I ask is because I have not marked my additional callbacks to “add it to BMS Full” key file. My own key file is based on the BMS Full file.Otherwise, keep up the good work. I could not fly without it.
Regards
Bikeman -
1. The default startup of the profile is Taxi, you can change it by selecting the System button and then click the Ramp button. That should set all switches, knobs, buttons in their ramp start position.
2. I recommend using the key file provided or else you’ll spend lots of time trying to get to profile to work right only to end up with a very very similar key file to what was given. -
Is there a way to resize\eliminate the grey background of the “Map Viewer” map so just the map itself (or with a small grey border) appears? I know I can resize the whole graphic and place it where I like, just don’t see a way to modify it…
-
The MapViewer control itself should just be showing the map and nothing else. If the map is inside a panel and the panel has a grey color set then you will see the grey color also. If this is the case go into the panel where the map viewer is within and uncheck background from the panel properties
-
That’s the problem: the Ramp/Hot/Air Start buttons on the System button are missing. The profile info above the hook switch says “HOT START v435-10”. Where do I find the buttons you mentioned?
-
Is there a way to resize\eliminate the grey background of the “Map Viewer” map so just the map itself (or with a small grey border) appears? I know I can resize the whole graphic and place it where I like, just don’t see a way to modify it…
The map is square so if the MapViewer is square you will not see any grey background but you will then have to setup a method to hide the control as you won’t be able to tap/click on the background to hide it since there won’t be one.
By adjusting the size of the MapViewer starting from square you can have as much or as little border as you want depending on how much out of square you make it.
Just make sure you’re changing the size of the actual MapViewer control and not the panel in the profile which contains it.
If you don’t like the grey background colour I chose I’m afraid you’re stuck with it since it’s coded into the dll.:)
-
Hi, great work again, thanks.
Two questions though:
1. and most important: the startup mde is not recognized (and yes, I copied the Helios Falcon.dll to the correct folder). The profile always shows all knobs and switches in the taxiway/flight positions. Any suggestions? Is the a special orer in which to start the profile and the sim?
2. Do I really have to use the supplied key file or can I switch the profile to my usual key file? The reason I ask is because I have not marked my additional callbacks to “add it to BMS Full” key file. My own key file is based on the BMS Full file.Otherwise, keep up the good work. I could not fly without it.
Regards
Bikeman1. The profile always initially starts in “Hot Start” mode since there is no way of knowing which mode you’re going to select in BMS, as soon as you enter 3D the mode should auto-select depending on the mode you selected before you selected “Fly”. Ramp > Ramp Start, Taxi/Runway > Hot start or any mission that starts airborne > Air Start.
2. You need to use the supplied key file, that should form the basis, you can add to it providing all the callbacks required by the profile are retained.
3. The Ramp Start, Hot Start and Air Start buttons are no longer necessary and have been removed.
-
Sorry, me again, still no joy with the startup. I am using your key file in the Helios profile and BMS.
I have checked the HeliosFalcon.dl (size 48’635’904 bytes), it was protected by Windows. I unblocked it.
First I start the Helios profiIe, then I start the KTO training mission GroundOPS, click in BMS on RAMP. In the 3d world the hot start profile shows.
Am I doing things in the right order or do you have other suggestions on what I am doing wrong? -
Sorry, me again, still no joy with the startup. I am using your key file in the Helios profile and BMS.
I have checked the HeliosFalcon.dl (size 48’635’904 bytes), it was protected by Windows. I unblocked it.
First I start the Helios profiIe, then I start the KTO training mission GroundOPS, click in BMS on RAMP. In the 3d world the hot start profile shows.
Am I doing things in the right order or do you have other suggestions on what I am doing wrong?That’s the correct file with that size, and there is no particular order for start up, in fact I used that mission to test Ramp and Hot Start then the Spice mission to test Air Start.
Have you got any previous HeliosFalcon.dll’s hanging around in the Plugins folder. If so, even if you renamed them, just remove them. The reason being that if you renamed the previous 4.35-9 HeliosFalcon.dll to say HeliosFalcon.XXXX.dll that would still be read since it’s filename extension is still .dll and interfering with things.
If that was the case and you did a reset monitors and saved the profile then the binding for “Flight Start Mode” would get removed by the Helios Editor. So it’s important to then restore a new copy of the profile from the download.
Adding the HeliosFalcon.dll is only a temporary measure in order to get the profile released before the next major release of Helios, probably 1.6.5xxx, when all of the updates should be included, therefore then there will be no need for a separate .dll.
-
Negative on an old .dll hanging around. The new HeliosFalcon.dll is the only kid in town
Could it be a language issue? A friend of mine with the german 47th DragonFighters has the exact same problem. What information on my language setup do you require?
I do hope we get this sorted since I am grounded without Helios. -
Hello,
For information, if you do not use the “ENG (United States) keyboard, you must check the box” Always use QWERTY Key Codes “. For this option to work You must have the” ENG (United States) keyboard installed on your PC.
Have you checked if BMS is not running as administrator?
Helios and BMS must have the same rights. -
The map is square so if the MapViewer is square you will not see any grey background but you will then have to setup a method to hide the control as you won’t be able to tap/click on the background to hide it since there won’t be one.
By adjusting the size of the MapViewer starting from square you can have as much or as little border as you want depending on how much out of square you make it.
Just make sure you’re changing the size of the actual MapViewer control and not the panel in the profile which contains it.
If you don’t like the grey background colour I chose I’m afraid you’re stuck with it since it’s coded into the dll.:)
Right now it auto-sized to the size of my left monitor (2560x1440), I will play around with it a bit, thank you linknet!
-
Negative on an old .dll hanging around. The new HeliosFalcon.dll is the only kid in town
Could it be a language issue? A friend of mine with the german 47th DragonFighters has the exact same problem. What information on my language setup do you require?
I do hope we get this sorted since I am grounded without Helios.Run this test profile for Ground OPS Ramp, Ground OPS Taxi and the Spice training mission. Perform a Reset between tests to clear the data.
Let me have the results for all three when you are in 3D then we might be able to determine the problem:
https://www.mediafire.com/file/apa382oqz6o33s6/Test+Flight+Mode.hpf/file
In Flight >>> 0 = In UI, 1 = In 3D
On Ground >>> 0 = Not On Ground, 1 = On Ground
RPM >>> 0 = Engine not Running, >0 Engine Running –---- this should determine if either Ramp or TAXI when On Ground
Flight Mode >>> 1 = Ramp Start, 2 = Hot Start, 3 = Air Start
I haven’t tested this so it may need a bit of tweaking to get it to work.
Then give this modified HeliosFalcon.dll a try:
https://www.mediafire.com/file/djiuwervtmauney/HeliosFalconTest.zip/file
I haven’t tested this either just working on a hunch as to the problem.
-
Got it sorted, made a new profile, works great! Ignore the missing map section on the right, i’m at Brnik (Balkans) and the map ends just north of there… just have to figure out what setting in config makes the mouse work normally when out of the cockpit… set g_bEnableExclusiveMouseCapture 0 should do it, but doesn’t. // Captures the mouse when in 3D so that you don’t click something on the desktop when running windowed mode
-
Got it sorted, made a new profile, works great! Ignore the missing map section on the right, i’m at Brnik (Balkans) and the map ends just north of there… just have to figure out what setting in config makes the mouse work normally when out of the cockpit… set g_bEnableExclusiveMouseCapture 0 should do it, but doesn’t. // Captures the mouse when in 3D so that you don’t click something on the desktop when running windowed mode
That looks pretty good. I’ll let someone else answer the mouse problem, I’m on holiday.
-
Got it sorted, made a new profile, works great! Ignore the missing map section on the right, i’m at Brnik (Balkans) and the map ends just north of there… just have to figure out what setting in config makes the mouse work normally when out of the cockpit… set g_bEnableExclusiveMouseCapture 0 should do it, but doesn’t. // Captures the mouse when in 3D so that you don’t click something on the desktop when running windowed mode
Sell them and buy an Odyssey G9