Ice’s Falcon BMS Profile Updated for BMS 4.37
-
[FALCON_BMS_PATH]
Path= “C:\Falcon BMS 4.36”
[PILOT_CALLSIGN]
Callsign= “Viper” -
@daz The AutoIt error on trying to start BMS from the profile is due to a fault with the PathNames.ini file. Just replace it with the original file from the download. That should fix the array errors.
Now to determine why there are missing steerpoints I need a copy of the following file:
C:\Falcon BMS 4.36\User\Briefings\briefings.txt
It needs to be hosted somewhere so that I can download it, pasting it into this forum just seems to screw up the formatting. -
@linknet ok thanks, thats fixed that one so I can open BMS from the profile now.
I have uploaded my briefing.txt to https://www.mediafire.com/file/2to5ndxfahz0x2h/briefing.txt/file
Thanks
-
@daz said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
I have uploaded my briefing.txt to https://www.mediafire.com/file/2to5ndxfahz0x2h/briefing.txt/file
Strange, that works perfectly:
-
@daz Try deleting the Auto_Left.png and Auto_Right.png files in Documents\Helios\Images\FalconBMS Images 4.36\Kneeboards and see if they get recreated when you next run the profile. Auto_Right.png should contain the steerpoints.
-
@linknet Hi, when I run the profile, it always generates a blank Auto_Left and Auto_Right in
C:\Users\Admin\Documents\Helios\Images\FalconBMS Images 4.36\Kneeboards
I checked just to make sure and the briefing file is at:
C:\Falcon BMS 4.36\User\Briefings
Thanks
-
@daz Yet you say that the CPD steerpoints are all correct?
I’m not really sure what the problem is. Do you have the Arial Narrow fonts installed on your system? If not try installing them all from the Arial Narrow Fonts folder in the download.
If it looks like this then the Arial Narrow fonts are definitely missing:
-
@linknet Hi, Ha that was it, they are now installed and all is working great I will play some more tonight now.
This is really a nice solution. Thanks for your help.
I wish I had this when I was playing Falcon 4.0 20+ years ago. I guess it shows the power of open communities.
Thanks again.
-
@linknet Despite me spending hours trying to get Ice’s profile 4.36-04 and Helios 1.6.5.400.2 to work with my joystick profile, I am stumped despite installing and reinstalling. As soon as I enter BMS, none of joystick and throttle buttons are mapped properly. Same goes for the OSB and ICP buttons on my touchscreen.
Would anyone be willing to share a joystick profile that works? I run a TUSBA Cougar throttle, a Warthog joystick, TM MFDs.
Thanks!
-
@Mosquitoe Did you tell it to use your own .key file?
-
@Atlas Yes, in BMS, I pointed it to BMS - Ice’s Helios Profile.key which I have added my key bindings to
-
@Mosquitoe said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@linknet Despite me spending hours trying to get Ice’s profile 4.36-04 and Helios 1.6.5.400.2 to work with my joystick profile, I am stumped despite installing and reinstalling. As soon as I enter BMS, none of joystick and throttle buttons are mapped properly. Same goes for the OSB and ICP buttons on my touchscreen.
Would anyone be willing to share a joystick profile that works? I run a TUSBA Cougar throttle, a Warthog joystick, TM MFDs.
Thanks!
-
Are you using Alternative Launcher?
-
Does everything work without the joystick profile added to the keyfile?
-
Can you upload your key file complete with the added joystick profile to a suitable source and then provide a link to it.
-
-
-
No, I am using the BMS launcher.
-
Big No. With just the stock Ice keyfile without my bindings added, touchscreen presses on my MFDs and ICP just come out mapped to something completely different. Even the VHF rocker switch on my Cougar gets mapped to something on my Warthog throttle like TMS Down.
-
Link to my keystroke file - https://www.mediafire.com/file/aez9toehg251a1n/BMS_-_Ice%2527s_Helios_Profile.key/file
Thanks for your help with this.
-
-
@Mosquitoe
That key file is in a bit of a mess. The added HOTAS section already contained a full key file so everything was duplicated but not necessarily with the same callbacks.Download this: https://www.mediafire.com/file/c56wih1aceimi85/BMS+-+Ice’s+Helios+Profile+Key+Files.zip/file
First from that download use the standard BMS - Ice’s Helios Profile Key with NO added HOTAS and make sure that both the profile and BMS point to it.
Now just test the profile on the touchscreen, ignore the HOTAS, do all the buttons work? If they don’t work then you have some other problem.
If it does work then try the BMS - Ice’s Helios Profile Key with HOTAS which contains the HOTAS section I extracted from your original key file. Although I have no way of knowing if that HOTAS section works with your HOTAS. However it only contains DX callbacks which shouldn’t interfere with the keyboard callbacks in the standard profile key,
-
-
@linknet I tested the Keyfile without any bindings and I still had problems getting the touchscreen MFD and ICP buttons to work. Strange thing is all the cockpit switches, dials and buttons seem to work fine. It seems to be isolated to the ICP and MFD buttons.
When I did the test, I didn’t have my HOTAS plugged in.
Any thoughts?
-
@Mosquitoe said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@linknet I tested the Keyfile without any bindings and I still had problems getting the touchscreen MFD and ICP buttons to work. Strange thing is all the cockpit switches, dials and buttons seem to work fine. It seems to be isolated to the ICP and MFD buttons.
When I did the test, I didn’t have my HOTAS plugged in.
Any thoughts?
Yes, first let’s see if the profile’s MFD’s are generating the correct keystrokes. So download this EventTester utility and run that together with the profile, don’t start BMS and leave your HOTAS unplugged.
https://www.mediafire.com/file/ew1r8m4sawacwl5/EventTester.exe/file
Press the Left MFD OSB-1 Button and check that the output in the EventTester is as shown below. Left MFD OSB buttons 1 to 10 should give the same result with just the number cycling through 1234567890.
You can check all of the button outputs against the “BMS - Ice’s Helios Profile Keyboard Layout.pdf” found in the profile download under
Helios Full Profile Setup >> FalconBMS Keyfile >> BMS - Ice’s Helios Profile Keyboard Layout.pdf
-
@linknet I tested the LFD and they are definitely out of sync. OSB 1 on the left button generated a keystroke for OSB2. OSB 2 generated a keystroke for OS4 and the OSB 3, 4 and 5 didn’t generate anything at all.
Could this be a driver issue for my touchscreen monitor? My touchscreen monitor is an Asus VT229
-
@Mosquitoe If you have the same Windows Scaling factor (DPI) for both your main monitor and the touchscreen ,which is absolutely essential, then you could try to recalibrate the touchscreen. Failing that it could be a problem with the touchscreen.
-
@linknet both monitors are running at 1920 x 1080. I’ll try recalibrating but I don’t there is an issue with the touchscreen as it is not giving me any issues with MS Office docs.