For some reason, I've made changes to my .key file shortly after uploading v.16 on March 2017. Change were done to the MAN RANGE and MFD GAIN callbacks and then to the Coolie Switch and Radio Switch swaps.
BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory. This v1.7 of my .key file.
The links to the original profile post also updated to v1.7.
Saturday, 21 October 2017
Sunday, 17 September 2017
v4.21S Release
Hello again fellow simmers!
With the release of YAME64 v.1.2.1, new features are available and for this, I've created a new version for my single-screen Helios profile.
Thanks to user feedback from Sharpe, I've implemented the approach plates to all South Korean (and Japanese) airbases.
Changes to this version include:
Here are the files for the new profile:
One-screen setup:
YAME textures:
With the release of YAME64 v.1.2.1, new features are available and for this, I've created a new version for my single-screen Helios profile.
Thanks to user feedback from Sharpe, I've implemented the approach plates to all South Korean (and Japanese) airbases.
Changes to this version include:
- New button images for the System Panel to make them easier to identify
- CPD button syncs CPD display on/off
- OSB implementation on CPD
- Fixed/altered YAME textures
Here are the files for the new profile:
One-screen setup:
- -Ice's BMS 4.33 v4.21S.hpf -- place this on your /Documents/Helios/Profiles directory
- Ice1ScreenSetup v121 -- place this on your /YAME64/layouts directory
- -Ice's Falcon BMS ver.3S -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.3S directory
YAME textures:
- YAME.7z -- Extract and copy/overwrite the CustomTextures folder into the \YAME64\gauges\CustomTextures folder, copy/overwrite the gear.png file into the \YAME64\gauges folder, and copy/overwrite the Korea KTO.png into the \YAME64\gauges\cp60\maps folder
Friday, 25 August 2017
2nd Test Instrument Approach Implementation
Part 2... Applied to departure and approach plates for Kunsan and Pusan only.
Please post on the BMS thread for any issues or any more suggestions. Thanks!
-Ice's BMS 4.33 v4.16dS.hpf -- place this on your /Documents/Helios/Profiles directory
Please post on the BMS thread for any issues or any more suggestions. Thanks!
-Ice's BMS 4.33 v4.16dS.hpf -- place this on your /Documents/Helios/Profiles directory
Sunday, 20 August 2017
Testing Instrument Approach Implementation
Here is a proof-of-concept to implement a suggestion from Sharpe. This should allow users to have the approach or departure plates displayed as they fly the instruments into or out of an airbase. So far, I've only implemented this to work on Kunsan and only to show the approach plates for Runway 18 and Runway 36.
A quick rundown of how to use it --- open up the CHARTS panel by tapping on the RWR, select KUNSAN, then select either RUNWAY 18 or RUNWAY 36. Tap on the approach plate to hide the center panel and the right panel. Tap on the approach plate again to un-hide the panels or tap on the RWR to un-hide the panels.
Please post on the BMS thread for any issues or any more suggestions. Thanks!
A quick rundown of how to use it --- open up the CHARTS panel by tapping on the RWR, select KUNSAN, then select either RUNWAY 18 or RUNWAY 36. Tap on the approach plate to hide the center panel and the right panel. Tap on the approach plate again to un-hide the panels or tap on the RWR to un-hide the panels.
Please post on the BMS thread for any issues or any more suggestions. Thanks!
- -Ice's BMS 4.33 v4.16cS.hpf -- place this on your /Documents/Helios/Profiles directory
Monday, 17 April 2017
New TARGET profile + layout
Due to the number of requests for this, I have made a "layout" of what is mapped where on the TARGET profile. I've also cleaned up the profile to make it easier to read. Please note that the TMS and DMS shifted layers are from Morphine's original work; I've not changed it as I've never used it as a shifted layer and so never bothered with it. I've also removed all the mappings for the switches on the throttle base except for the FLAPS switch which controls the LG lever in case I need to operate the LG lever without having to look down in the cockpit.
One big change here is that I've re-mapped the MIC switch to control radar elevation and range knob use. Comms control has been transferred to the COOLIE HAT which is where the comms switch is on the actual F-16 throttle. The CHINA HAT now controls zoom/FoV levels.
Please feel free to adjust the profile to your preferences and if you have a good idea of mapping a particular callback or function anywhere on the profile, please share your idea and I'll be glad to add it into the default profile. I'm currently thinking of mapping the screenshot button somewhere so that it'll be easy to take pictures without taking my hands off the controls.
Credit goes to Scotters for bringing Rybo's profile to my attention and also credit to Rybo for the inspiration for the change.
Link on first post updated.
One big change here is that I've re-mapped the MIC switch to control radar elevation and range knob use. Comms control has been transferred to the COOLIE HAT which is where the comms switch is on the actual F-16 throttle. The CHINA HAT now controls zoom/FoV levels.
Please feel free to adjust the profile to your preferences and if you have a good idea of mapping a particular callback or function anywhere on the profile, please share your idea and I'll be glad to add it into the default profile. I'm currently thinking of mapping the screenshot button somewhere so that it'll be easy to take pictures without taking my hands off the controls.
Credit goes to Scotters for bringing Rybo's profile to my attention and also credit to Rybo for the inspiration for the change.
Link on first post updated.
- Ice's BMS WH Profile ver7.1.tmc -- open and run with TARGET Script Editor. This is also from Morphine's profile with a few edits (updated 17-04-2017)
- Ice's BMS WH Profile ver7.1.pdf -- PDF version showing current control mapping
- Ice's BMS WH Profile ver7.1.fcf -- open with TARGET GUI to edit control mapping printout
- BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory. This v1.7 of my .key file.
Monday, 20 March 2017
Two-screen setup updated
Noted a small bug in this version, namely that the CPD sync button (small gray button) was not mapped to anything. Fixed. Link on first post updated.
- -Ice's BMS 4.33 v4.17 -- place this on your /Documents/Helios/Profiles directory
Friday, 17 March 2017
Profile not working?
Here are a few things to check if there are any issues with getting my profile to work properly:
1. Make sure the .key file is loaded in BMS. To do this, start up BMS, go to SETUP -> CONTROLLERS and click LOAD, select my .key file, and click on LOAD again. Current Keyfile should say BMS - FPM by -Ice and the very first line should show v1.6. Click APPLY a few times, then OK.
2. Make sure the .key file is loaded in Helios. To do this, start up Helios Profile Editor, load the profile, select the PROFILE EXPLORER tab and scroll down until you can see FALCON. Double-click on FALCON and a new tab should appear called FALCON. Make sure the Key File points to the proper location of the .key file.
3. RWR not showing up properly? The YAME .xml file isn't pointing to the proper location. Open the .xml file via Notepad++ and line 306 (line 340 on the two-screen .xml file) shows the info for the RWR settings. Line 313 (line 347 on the two-screen .xml file) tells YAME where to look for the RWR image. Change this line as appropriate.
More to be added as issues get identified....
1. Make sure the .key file is loaded in BMS. To do this, start up BMS, go to SETUP -> CONTROLLERS and click LOAD, select my .key file, and click on LOAD again. Current Keyfile should say BMS - FPM by -Ice and the very first line should show v1.6. Click APPLY a few times, then OK.
2. Make sure the .key file is loaded in Helios. To do this, start up Helios Profile Editor, load the profile, select the PROFILE EXPLORER tab and scroll down until you can see FALCON. Double-click on FALCON and a new tab should appear called FALCON. Make sure the Key File points to the proper location of the .key file.
3. RWR not showing up properly? The YAME .xml file isn't pointing to the proper location. Open the .xml file via Notepad++ and line 306 (line 340 on the two-screen .xml file) shows the info for the RWR settings. Line 313 (line 347 on the two-screen .xml file) tells YAME where to look for the RWR image. Change this line as appropriate.
<RWR zindex="4">This should be how the RWR should be set up in YAME:
<width>234</width>
<height>236</height>
<posx>452</posx>
<posy>24</posy>
<visible>true</visible>
<window>RIGHT SCREEN</window>
<image>Y:\YAME64\gauges\rwr.png</image>
<shader>shaders/blend.frag</shader>
</RWR>
More to be added as issues get identified....
Tuesday, 14 March 2017
Fixing the Charts
For some reason, a really common bug within Helios is that the CHART panels disappear after using the Reset Monitors function of Helios. To fix this, simply copy over the relevant lines from the default .hpf file onto your new .hpf file.
For the two-screen setup, the line starts from 14,969 to 16,478. For the one-screen setup, the line starts from 15,471 to 16,980.
Here's line 15,596 to 15,600 from the one-screen setup .hpf file:
As shown, my main screen is [1] and my secondary screen is [2]. Sometimes, Helios may detect the main screen as [2] and the secondary screen as [1]... or if you have more than 2 monitors, the one showing the profile may be identified as [X]. Whatever the case may be, simply change the monitor number in the .hpf file to reflect what your secondary screen number is.
So instead of having:
<Trigger Source="Visual;Monitor 2.Panel FRONT CONSOLE.Panel CHARTS.Button KUNSAN;Helios.Base.PushButton;Button KUNSAN" Name="pushed" />
and Helios has detected your main screen as [2] and your secondary screen as [1], you'll need to change the lines so that it will read:
<Trigger Source="Visual;Monitor 1.Panel FRONT CONSOLE.Panel CHARTS.Button KUNSAN;Helios.Base.PushButton;Button KUNSAN" Name="pushed" />
This is easily done in Notepad++ by using the Replace function. There should be a total of 3,370 occurrences when searching the whole profile or 604 occurrences when just editing the lines cited above.
The whole procedure should be as follows:
1. Open up the profile in the Helios Profile Editor.
2. Click on the Profile Explorer tab, scroll down to Falcon, and double-click it.
3. A new tab should open and under the Falcon Key Callbacks, make sure that it points to the .key file in the BMS install directory.
4. Click Profile, click Reset Monitors, and adjust your layout accordingly, taking note of what the touchscreen monitor's number is.
5. Click Profile, click Save As, and rename as desired.
6. Open the original .hpf file, locate and copy the lines from the original .hpf file, and paste it under a new Notepad++ document.
7. Use the Replace function to find and replace the monitor numbers to the correct number. If done correctly, 604 occurrences would be replaced.
8. Open the new/renamed .hpf file, locate and delete the lines required, and then insert the new, edited lines.
9. Save the profile in Notepad++.
Open up Helios Control Center and verify that the charts are now working again.
For the two-screen setup, the line starts from 14,969 to 16,478. For the one-screen setup, the line starts from 15,471 to 16,980.
Here's line 15,596 to 15,600 from the one-screen setup .hpf file:
<Binding BypassCascadingTriggers="False">One thing that needs changing is the monitor number. Refer to my monitor arrangement below:
<Trigger Source="Visual;Monitor 2.Panel FRONT CONSOLE.Panel CHARTS.Button KUNSAN;Helios.Base.PushButton;Button KUNSAN" Name="pushed" />
<Action Target="Visual;Monitor 2.Panel FRONT CONSOLE.Panel CHARTS.Chart BACKGROUND;Helios.Panel;Chart BACKGROUND" Name="toggle.hidden" />
<StaticValue />
</Binding>
As shown, my main screen is [1] and my secondary screen is [2]. Sometimes, Helios may detect the main screen as [2] and the secondary screen as [1]... or if you have more than 2 monitors, the one showing the profile may be identified as [X]. Whatever the case may be, simply change the monitor number in the .hpf file to reflect what your secondary screen number is.
So instead of having:
<Trigger Source="Visual;Monitor 2.Panel FRONT CONSOLE.Panel CHARTS.Button KUNSAN;Helios.Base.PushButton;Button KUNSAN" Name="pushed" />
and Helios has detected your main screen as [2] and your secondary screen as [1], you'll need to change the lines so that it will read:
<Trigger Source="Visual;Monitor 1.Panel FRONT CONSOLE.Panel CHARTS.Button KUNSAN;Helios.Base.PushButton;Button KUNSAN" Name="pushed" />
This is easily done in Notepad++ by using the Replace function. There should be a total of 3,370 occurrences when searching the whole profile or 604 occurrences when just editing the lines cited above.
The whole procedure should be as follows:
1. Open up the profile in the Helios Profile Editor.
2. Click on the Profile Explorer tab, scroll down to Falcon, and double-click it.
3. A new tab should open and under the Falcon Key Callbacks, make sure that it points to the .key file in the BMS install directory.
4. Click Profile, click Reset Monitors, and adjust your layout accordingly, taking note of what the touchscreen monitor's number is.
5. Click Profile, click Save As, and rename as desired.
6. Open the original .hpf file, locate and copy the lines from the original .hpf file, and paste it under a new Notepad++ document.
7. Use the Replace function to find and replace the monitor numbers to the correct number. If done correctly, 604 occurrences would be replaced.
8. Open the new/renamed .hpf file, locate and delete the lines required, and then insert the new, edited lines.
9. Save the profile in Notepad++.
Open up Helios Control Center and verify that the charts are now working again.
BMS Helios Profile Updated... Again!!
Hello again fellow simmers!!
After a break in Falcon of over a year, I'm back and ready to release my new Helios profile for Falcon BMS! I've been working on this profile for the past few months and have integrated new features thanks to YAME and being able to learn more about how to work with Helios.
Before we go any further, let me just thank the fellow simmers (you know who you are! THANK YOU!!) who have found my work useful enough and worthy of clicking the DONATE button on the right side. While I do this work for free, it's nice to be appreciated in that way and does give me a great incentive to improve on the profile.
As always, this profile is designed to work with a touchscreen with a resolution of 1920x1080. I use this profile with my own custom .key file and a modified TM WH profile from Morphine's profile. However, the new profile now comes in two flavors --- a single-screen setup which I expect to be the more popular one and a two-screen setup which is what I'm primarily using.
Credits go to xflight.de/Martin for the original images, Red Dog for his charts, Lightning for his MFDE program, Roccio/Focaldesign/Scorpion for their work on YAME64, Kolbe for the excellent .key file organization, Morphine for his original TM WH profile, and Falcas for his WDP program.
Here's what the new profile looks like:
As the two-screen setup was the primary profile, most of the features of that profile have been ported over to the single-screen setup. I'll talk about the two-screen setup first and most of what can be seen on the front console in the two-screen setup is the same on the single-screen setup.
First up is the front consoles touch zones. These are "hidden" buttons that open up various other panels or send input to the sim.
On the top left and right of the front console are the buttons to show/hide the side consoles. However, unlike the previous profile, there is now only ONE side console that incorporates both the left console and right console of the F-16. This should make ramp starts much easier and quicker.
Touching the CMDS display shows the Countermeasures panel.
The RWR opens the Charts panel and the small Data Card picture opens the Data Card panel on the left touchscreen.
The Altimeter and HSI sections are split into 4 quadrants with the upper left/right used to decrease/increase by 5 and the lower left/right used to decrease/increase by 1. The Trim gauges can be "pressed" to reset the trims to center.
For the Altimeter and HSI functions to work, the falcon bms.cfg file must be edited and this entry added at the first space at the top:
set g_nKnobAccelerationDelta 300
On the lower left corner is a Buttons panel which is moved to the lower right corner in the single-screen setup. The first button is the COMMS button which brings up the Comms panel containing all the radio commands in BMS. While the sim is ideally paired with some sort of voice command software such as VAC, Voice Attack, or LMC, this page still serves as a handy reminder of all the radio commands in the sim.
The OBS button can be used to start/stop recording via FRAPS or OBS and is mapped to SHIFT+F11 by default. The Smoke, Pause, and Freeze buttons function as advertised and the TIR Pause button pauses TIR and resets the view to the front view. I've found this very useful for practicing air-to-air refuelling.
The CPD button shows the CPD which is a new feature of YAME. Currently, only the central bottom three OSBs are working to display gauges/map/mission data respectively. On the map screen the respective labels work as advertised. In a future version of YAME, a higher-res map image can be used and the OSBs work more reliably. On the bottom of the screen, just beside the trim gauges, is a small gray button.... sometimes the CPD panel will not sync with the CPD button and this small gray button is used to resolve any synchronization issues. Again, in the future version of YAME, this will be fixed.
Because of the current low-res map in the CPD, I've added a Map screen that should be more useful. The main map is divided by green lines into sections. Pressing on the relevant section will fill the screen with that section, pressing the screen again will return to the main map. Pressing anywhere on the screen that is NOT a map section will close the map, or pressing the MAP button on the second touchscreen will also close the map. This is useful for opening/closing a section-view of the map.
Next is the VIEWS button that brings up the Views panel which can be used to control external views and grab screenshots without having to use the keyboard. Most of the contents of the Views panel is a work-in-progress as I experiment with various layouts and which views are more useful than others. On the two-screen setup, the VIEWS button can be pressed to close the panel. On the one-screen setup, pressing anywhere on the panel that is not a button will close the panel.
Finally, there is the SYSTEM button that brings up the System panel. The primary use for this panel is for starting up BMS, showing the FPS counter, and exiting a mission.
A few cool improvements I've made for this version was to make the Canopy spider switch just a switch guard like in the real F-16. It is now necessary to lift the spider cover to access the actual canopy switch underneath.
The HDG knob now changes it's label from HDG to CRS to indicate which setting is going to be changed when pressing on the HSI.
The MFDs have also gotten new rocker images which looks more in line with the graphical style. The rockers on the ICP have also been changed, and the N/S/E/W labels have been added.
The ALT GEAR handle has been adjusted to have a larger touch zone, which should make it easier to activate in case of emergency.
The TFR button now also syncs with the button inside the cockpit, making it easier to tell when the system is activated or not.
The MAL & IND button has also been implemented to show all lights in the cockpit as well as in the Helios profile. All warning lights from the side consoles and even the eyebrow lights have been implemented and the TWA and TWP buttons now have an on/off state. The cockpit mouse enable/disable button has been integrated on the left eyebrow lights for easier access and checking. I've also added a new panel for the HMCS and NVG controls.
One of the biggest implementations to the new profile is a fully-working UHF and TACAN panels. Big credit goes to Weepop for inspiring me to do this. The UHF CHAN rotary is fully working and can cycle up/down with no issues. The individual channel knobs can cycle up/down with no issues as well, although there is a sync issue with the numbers when going from 3XX.XXX and back to 2XX.XXX. This is a limitation within Helios. The touch zones for the UHF is shown below and although only one knob is highlighted, it is the same for the four other knobs.
The same has been done for the TACAN panel and defaults at 106X. Each digit can cycle up/down with no issues. Unfortunately, there may be a time when the default backup channel can be changed and saved in the DTC so that it is pre-loaded in the jet... there is no way to sync that with Helios. If the default backup channel is changed in the sim, the profile itself must be changed to reflect this, otherwise it will just show 106X and there will be synchronization issues. The touch zones for the TACAN panel is shown below and although only one section is highlighted, it is the same for the three other sections.
Now for the single-screen setup.
Due to the limited space of just using a single screen, I've had to be a bit more creative with the hidden buttons on the front console. Here are the touch zones for the single-screen setup.
On the top left and right of the front console are the buttons to show/hide the side console. However, unlike the previous profile, there is now only ONE side console that incorporates both the left and right console of the F-16. This should make ramp starts much easier and quicker. Because this is the single-screen setup, I've had to remove some of the cosmetic panels to make room. Note that the TWA panel is duplicated here for when it is needed during rampstart.
The RWR, Altimeter, and HSI remain the same. The Trim gauges can be "pressed" to reset the trims to center. Pressing on the CMDS display shows the Countermeasures panel.
The LG lights will show the backup TWA panel and the Speedbrake indicator will show the HMCS/NVG panel. It may be useful to show the TWA panel during flight for better SA and is thus placed in this position.
Pressing the DED will show the Data Card panel. When the Data Card is up, it has it's own touch zones with the ones on the left and right used to change which Data Card page is shown. The red touch zone in the middle can be used to close the Data Card panel, or press on the DED again.
As with the two-screen setup, all the lights are implemented in the profile.
For this update, I've stopped using MFDE for gauge displays and have started using YAME64. One of the benefits of YAME is that gauge placement can be saved in a layout file which can be easily distributed and changes to gauge placement or gauge size can be entered manually for pixel-accurate adjustments. Another advantage is that YAME pulls the extraction images straight from BMS so the DED/MFD/PFL displays are exactly what is seen in the pit without having to use BMS's CDE. I wasn't too fond of the YAME caution panel so I've made my own that blends in with the rest of the profile. The developers of YAME are also actively improving on the program and listen to community feedback so it can only get better and better with time.
As always, the main goal of this project is to eliminate the need of using the mouse or keyboard once inside the cockpit in the 3D world. All the necessary switches and controls should be present in the profile and should be easy and intuitive to use.
Here are the the files for the new profile:
Two-screen setup:
One-screen setup:
Any suggestions and issues regarding this profile, please post on [this thread] and I'll do my best to help! Thank you for trying my profile!
After a break in Falcon of over a year, I'm back and ready to release my new Helios profile for Falcon BMS! I've been working on this profile for the past few months and have integrated new features thanks to YAME and being able to learn more about how to work with Helios.
Before we go any further, let me just thank the fellow simmers (you know who you are! THANK YOU!!) who have found my work useful enough and worthy of clicking the DONATE button on the right side. While I do this work for free, it's nice to be appreciated in that way and does give me a great incentive to improve on the profile.
As always, this profile is designed to work with a touchscreen with a resolution of 1920x1080. I use this profile with my own custom .key file and a modified TM WH profile from Morphine's profile. However, the new profile now comes in two flavors --- a single-screen setup which I expect to be the more popular one and a two-screen setup which is what I'm primarily using.
Credits go to xflight.de/Martin for the original images, Red Dog for his charts, Lightning for his MFDE program, Roccio/Focaldesign/Scorpion for their work on YAME64, Kolbe for the excellent .key file organization, Morphine for his original TM WH profile, and Falcas for his WDP program.
Here's what the new profile looks like:
Two-screen setup
One-screen setup
As the two-screen setup was the primary profile, most of the features of that profile have been ported over to the single-screen setup. I'll talk about the two-screen setup first and most of what can be seen on the front console in the two-screen setup is the same on the single-screen setup.
First up is the front consoles touch zones. These are "hidden" buttons that open up various other panels or send input to the sim.
On the top left and right of the front console are the buttons to show/hide the side consoles. However, unlike the previous profile, there is now only ONE side console that incorporates both the left console and right console of the F-16. This should make ramp starts much easier and quicker.
Touching the CMDS display shows the Countermeasures panel.
The RWR opens the Charts panel and the small Data Card picture opens the Data Card panel on the left touchscreen.
The Altimeter and HSI sections are split into 4 quadrants with the upper left/right used to decrease/increase by 5 and the lower left/right used to decrease/increase by 1. The Trim gauges can be "pressed" to reset the trims to center.
For the Altimeter and HSI functions to work, the falcon bms.cfg file must be edited and this entry added at the first space at the top:
set g_nKnobAccelerationDelta 300
On the lower left corner is a Buttons panel which is moved to the lower right corner in the single-screen setup. The first button is the COMMS button which brings up the Comms panel containing all the radio commands in BMS. While the sim is ideally paired with some sort of voice command software such as VAC, Voice Attack, or LMC, this page still serves as a handy reminder of all the radio commands in the sim.
Tower
AWACS
Wingman
Element
Flight
Tanker
The OBS button can be used to start/stop recording via FRAPS or OBS and is mapped to SHIFT+F11 by default. The Smoke, Pause, and Freeze buttons function as advertised and the TIR Pause button pauses TIR and resets the view to the front view. I've found this very useful for practicing air-to-air refuelling.
The CPD button shows the CPD which is a new feature of YAME. Currently, only the central bottom three OSBs are working to display gauges/map/mission data respectively. On the map screen the respective labels work as advertised. In a future version of YAME, a higher-res map image can be used and the OSBs work more reliably. On the bottom of the screen, just beside the trim gauges, is a small gray button.... sometimes the CPD panel will not sync with the CPD button and this small gray button is used to resolve any synchronization issues. Again, in the future version of YAME, this will be fixed.
Because of the current low-res map in the CPD, I've added a Map screen that should be more useful. The main map is divided by green lines into sections. Pressing on the relevant section will fill the screen with that section, pressing the screen again will return to the main map. Pressing anywhere on the screen that is NOT a map section will close the map, or pressing the MAP button on the second touchscreen will also close the map. This is useful for opening/closing a section-view of the map.
Next is the VIEWS button that brings up the Views panel which can be used to control external views and grab screenshots without having to use the keyboard. Most of the contents of the Views panel is a work-in-progress as I experiment with various layouts and which views are more useful than others. On the two-screen setup, the VIEWS button can be pressed to close the panel. On the one-screen setup, pressing anywhere on the panel that is not a button will close the panel.
Finally, there is the SYSTEM button that brings up the System panel. The primary use for this panel is for starting up BMS, showing the FPS counter, and exiting a mission.
A few cool improvements I've made for this version was to make the Canopy spider switch just a switch guard like in the real F-16. It is now necessary to lift the spider cover to access the actual canopy switch underneath.
The HDG knob now changes it's label from HDG to CRS to indicate which setting is going to be changed when pressing on the HSI.
The MFDs have also gotten new rocker images which looks more in line with the graphical style. The rockers on the ICP have also been changed, and the N/S/E/W labels have been added.
The ALT GEAR handle has been adjusted to have a larger touch zone, which should make it easier to activate in case of emergency.
The TFR button now also syncs with the button inside the cockpit, making it easier to tell when the system is activated or not.
The MAL & IND button has also been implemented to show all lights in the cockpit as well as in the Helios profile. All warning lights from the side consoles and even the eyebrow lights have been implemented and the TWA and TWP buttons now have an on/off state. The cockpit mouse enable/disable button has been integrated on the left eyebrow lights for easier access and checking. I've also added a new panel for the HMCS and NVG controls.
One of the biggest implementations to the new profile is a fully-working UHF and TACAN panels. Big credit goes to Weepop for inspiring me to do this. The UHF CHAN rotary is fully working and can cycle up/down with no issues. The individual channel knobs can cycle up/down with no issues as well, although there is a sync issue with the numbers when going from 3XX.XXX and back to 2XX.XXX. This is a limitation within Helios. The touch zones for the UHF is shown below and although only one knob is highlighted, it is the same for the four other knobs.
The same has been done for the TACAN panel and defaults at 106X. Each digit can cycle up/down with no issues. Unfortunately, there may be a time when the default backup channel can be changed and saved in the DTC so that it is pre-loaded in the jet... there is no way to sync that with Helios. If the default backup channel is changed in the sim, the profile itself must be changed to reflect this, otherwise it will just show 106X and there will be synchronization issues. The touch zones for the TACAN panel is shown below and although only one section is highlighted, it is the same for the three other sections.
Now for the single-screen setup.
Due to the limited space of just using a single screen, I've had to be a bit more creative with the hidden buttons on the front console. Here are the touch zones for the single-screen setup.
On the top left and right of the front console are the buttons to show/hide the side console. However, unlike the previous profile, there is now only ONE side console that incorporates both the left and right console of the F-16. This should make ramp starts much easier and quicker. Because this is the single-screen setup, I've had to remove some of the cosmetic panels to make room. Note that the TWA panel is duplicated here for when it is needed during rampstart.
The RWR, Altimeter, and HSI remain the same. The Trim gauges can be "pressed" to reset the trims to center. Pressing on the CMDS display shows the Countermeasures panel.
The LG lights will show the backup TWA panel and the Speedbrake indicator will show the HMCS/NVG panel. It may be useful to show the TWA panel during flight for better SA and is thus placed in this position.
Pressing the DED will show the Data Card panel. When the Data Card is up, it has it's own touch zones with the ones on the left and right used to change which Data Card page is shown. The red touch zone in the middle can be used to close the Data Card panel, or press on the DED again.
As with the two-screen setup, all the lights are implemented in the profile.
For this update, I've stopped using MFDE for gauge displays and have started using YAME64. One of the benefits of YAME is that gauge placement can be saved in a layout file which can be easily distributed and changes to gauge placement or gauge size can be entered manually for pixel-accurate adjustments. Another advantage is that YAME pulls the extraction images straight from BMS so the DED/MFD/PFL displays are exactly what is seen in the pit without having to use BMS's CDE. I wasn't too fond of the YAME caution panel so I've made my own that blends in with the rest of the profile. The developers of YAME are also actively improving on the program and listen to community feedback so it can only get better and better with time.
As always, the main goal of this project is to eliminate the need of using the mouse or keyboard once inside the cockpit in the 3D world. All the necessary switches and controls should be present in the profile and should be easy and intuitive to use.
Here are the the files for the new profile:
Two-screen setup:
- -Ice's BMS 4.33 v4.17 -- place this on your /Documents/Helios/Profiles directory
- -Ice's Falcon BMS ver.3 -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.3 directory
- BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory. This is Morphine's profile with a few edits and adapted to Kolbe's format. This is v1.7 of my .key file.
- Ice's BMS WH Profile ver7.1.tmc -- open and run with TARGET Script Editor. This is also from Morphine's profile with a few edits (updated 17-04-2017)
- Ice2ScreenSetup -- place this on your /YAME64/layouts directory
One-screen setup:
- -Ice's BMS 4.33 v4.16S -- place this on your /Documents/Helios/Profiles directory
- -Ice's Falcon BMS ver.3S -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.3S directory
- BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory. This is Morphine's profile with a few edits and adapted to Kolbe's format. This is v1.7 of my .key file.
- Ice's BMS WH Profile ver7.1.tmc -- open and run with TARGET Script Editor. This is also from Morphine's profile with a few edits (updated 17-04-2017)
- Ice1ScreenSetup -- place this on your /YAME64/layouts directory
Any suggestions and issues regarding this profile, please post on [this thread] and I'll do my best to help! Thank you for trying my profile!
Monday, 23 November 2015
Fixing the TRIM
For some reason, the default TRIM functions in the .key file does not like to play nice with TrackIR so I've ported over Morphine's lines onto the .key file. Please download this new .key file so that the TRIM hat works as intended. Thanks!
BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory
BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory
Sunday, 22 November 2015
BETA Profile Update - Nov 22
Updated the charts to use the new ones for 4.33. I think most charts are the same but a few have been taken out and others have been renamed.
Also, thanks for an idea from Toto, I've modded the MFDs so that the "touch area" is bigger making it easier to use. The rockers have been made bigger too.
Because of the new images, I've uploaded a new .zip file with images.
Here are the new files:
-Ice's BMS 4.33 ver1.2 -- place this on your /Documents/Helios/Profiles directory
Custom Images -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.2 directory
For any issues or problems, please post a comment here or on the BMS forum thread. Thanks!
Also, thanks for an idea from Toto, I've modded the MFDs so that the "touch area" is bigger making it easier to use. The rockers have been made bigger too.
Because of the new images, I've uploaded a new .zip file with images.
Here are the new files:
-Ice's BMS 4.33 ver1.2 -- place this on your /Documents/Helios/Profiles directory
Custom Images -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.2 directory
For any issues or problems, please post a comment here or on the BMS forum thread. Thanks!
Thursday, 19 November 2015
BETA Profile Update - Nov 18
A bit more work done on the profile and have incorporated a few new things:
Here are the new files:
-Ice's BMS 4.33 ver.1.1 -- place this on your /Documents/Helios/Profiles directory
BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory
Ice's BMS WH Profile ver6 -- open and run with TARGET Script Editor
For any issues or problems, please post a comment here or on the BMS forum thread. Thanks for trying out my profile!
- MFD Gain and Bightness rockers now work
- The profile should sync with some of the in-game cockpit switches. This should work for the right autopilot (Pitch) switch, the Parking Brake switch, the Landing Gear lever (only if BMS is the main window during the "loading to 3D" screen), and the JFS switch.
- Added a button to turn off mouse-clicks in the 3D pit. You will still see the mouse cursor but it will no longer interact with the switches/buttons/knobs in the pit. This is a red button just to the right of the Pitch AP switch and it will turn white once pressed. You should also see a "Mouse Buttons DISABLED" message in the game.
- Changed keybindings for a few knobs and switches due to some unknown issue with Helios and BMS (CAT switch, Audio SQL/GD knobs, Threat and Missile knobs, ICP Drift Warn switch, and a few others IIRC)
- Changed TARGET profile to fix a few issues. Still has a lot of Morphine's old key bindings on the throttle switches on the base but have been "commented out"
Here are the new files:
-Ice's BMS 4.33 ver.1.1 -- place this on your /Documents/Helios/Profiles directory
BMS - FPM by -Ice.key -- put in your /BMS/User/Config directory
Ice's BMS WH Profile ver6 -- open and run with TARGET Script Editor
For any issues or problems, please post a comment here or on the BMS forum thread. Thanks for trying out my profile!
Wednesday, 11 November 2015
BETA Profile Update
Okay, starting to find bugs now, mainly due to changing/renaming/adding/deleting callbacks in 4.33. I'll have to go through the whole profile to make sure everything is still where it should be and this will take some time. I'll also have to add the new switches that are in 4.33, so again, this will be a while.
For now, I'm uploading a profile that "fixes" the HDG, CRS, and Altimeter 5-degree increment/decrement issue. With this "fix," you only have to press ONCE to get a 5-degree increment/decrement. I've also resized the "buttons" so that each button is on its own quadrant and are equally sized. Upper right is a 5-degree increment, upper left is a 5-degree decrement. Lower right/left is a 1-degree increment/decrement.
For this profile to work, you will also need to go into your falcon bms.cfg file and add this entry at the first space at the top:
set g_nKnobAccelerationDelta 300
Refer to this BMS forum thread to learn more about what it does.
-Ice's BMS 4.33 ver.1 - profile with the HDG, CRS, and Altimeter "fix," place this on your /Documents/Helios/Profiles directory
For now, I'm uploading a profile that "fixes" the HDG, CRS, and Altimeter 5-degree increment/decrement issue. With this "fix," you only have to press ONCE to get a 5-degree increment/decrement. I've also resized the "buttons" so that each button is on its own quadrant and are equally sized. Upper right is a 5-degree increment, upper left is a 5-degree decrement. Lower right/left is a 1-degree increment/decrement.
For this profile to work, you will also need to go into your falcon bms.cfg file and add this entry at the first space at the top:
set g_nKnobAccelerationDelta 300
Refer to this BMS forum thread to learn more about what it does.
-Ice's BMS 4.33 ver.1 - profile with the HDG, CRS, and Altimeter "fix," place this on your /Documents/Helios/Profiles directory
Tuesday, 10 November 2015
BMS 4.33 .key file BETA
With the release of 4.33 came a lot of changes to the .key files. While my old 4.32 .key file would work in 4.33, it lost a bit of functionality (sound feedback) and might have brought problems. I've worked on a new 4.33 .key file by using the Pitbuilder.key file as base and then adding in the Full.key file callbacks that were not present in the Pitbuilder.key file. Basically, this meant that all the switch state callbacks (on-off) were mapped to keys and all the toggle callbacks were still included but unmapped.
Another change that had to be done was to relocate all the callbacks that were mapped to the Enter and Numpad Enter keys for the simple reason that Helios doesn't seem to want to work with these two keys in any way. Slightly annoying but hopefully, once the new Helios profile is up and running with 4.33, the "change" that I had to do won't really be noticed anyway.
So for the meantime, here is my 4.33 .key file for testing. Please post any problems here or on the BMS forums. Thanks!
-Ice's BMS 4.33 ver.1 - "new" Helios version, place this on your /Documents/Helios/Profiles directory
BMS 4.33 .key file BETA - put in your /BMS/User/Config directory
Another change that had to be done was to relocate all the callbacks that were mapped to the Enter and Numpad Enter keys for the simple reason that Helios doesn't seem to want to work with these two keys in any way. Slightly annoying but hopefully, once the new Helios profile is up and running with 4.33, the "change" that I had to do won't really be noticed anyway.
So for the meantime, here is my 4.33 .key file for testing. Please post any problems here or on the BMS forums. Thanks!
BMS 4.33 .key file BETA - put in your /BMS/User/Config directory
Friday, 16 October 2015
Importing datacard images into the Helios profile
To be able to use WDP images as datacard images in the Helios profile, it is necessary to make a few changes in WDP's export settings. In WDP, click on the Settings button on the top row and under Saved Picture Size, tick the A5 size and Knee Updater format boxes.
Use WDP as normal, then after clicking on the Save DataCard button, press the Cards Directory button to go to where the images are saved. The images will be saved as:
[flight callsign]_Comm_Left.jpg
[flight callsign]_Comm_Right.jpg
[flight callsign]_Left.jpg
[flight callsign]_Right.jpg
[flight callsign]_Briefing.jpg
These need to be renamed by basically removing the [flight callsign]_ section so that the images will now be:
Comm_Left.jpg
Comm_Right.jpg
Left.jpg
Right.jpg
Briefing.jpg
Cut/copy and paste these into the /Helios/Images/-Ice's Falcon BMS ver.2/Data Card directory and they will show up once the Helios profile is started (or restarted).
Use WDP as normal, then after clicking on the Save DataCard button, press the Cards Directory button to go to where the images are saved. The images will be saved as:
[flight callsign]_Comm_Left.jpg
[flight callsign]_Comm_Right.jpg
[flight callsign]_Left.jpg
[flight callsign]_Right.jpg
[flight callsign]_Briefing.jpg
These need to be renamed by basically removing the [flight callsign]_ section so that the images will now be:
Comm_Left.jpg
Comm_Right.jpg
Left.jpg
Right.jpg
Briefing.jpg
Cut/copy and paste these into the /Helios/Images/-Ice's Falcon BMS ver.2/Data Card directory and they will show up once the Helios profile is started (or restarted).
Disabling the in-cockpit mouse cursor
One thing to be careful of is the location of the in-game mouse cursor. If it is over a switch or button when a callback is issued from Helios, it will also register as a mouse-click and will result in unwanted commands and general confusion. To keep things under control, it is necessary to disable the in-cockpit mouse cursor.
To do this, go to the /User/Config folder and open up falcon bms.cfg, preferrably using a program such as Notepad++ and set the following:
set g_bMouseButton4TogglesClickablePit 1
set g_bEnableExclusiveMouseCapture 0
Once in the 3D cockpit, move the mouse to the upper left or upper right corner of the screen and click the 4th mouse button. That will lock the mouse cursor on that area and will minimize accidentally clicking anything in the 3D pit. This is not 100% safe -- if the screen is zoomed in and there is a button or switch where the mouse cursor is locked, activating anything from Helios may also register as a mouse-click but it is still safer than leaving the mouse cursor to move around. Also, with widescreen or multi-monitor setups, it is less likely that there will be a switch/button at the extreme corner of the screen.
The big advantage with Helios on a touchscreen is that it minimizes the time needed to be heads-down in the cockpit. Even when activating switches or buttons on the far corners of the side consoles, there is less need to pan the in-game view as much as needed when using a single-screen setup so again, that minimizes accidental button-clicks from the in-game mouse cursor.
To do this, go to the /User/Config folder and open up falcon bms.cfg, preferrably using a program such as Notepad++ and set the following:
set g_bMouseButton4TogglesClickablePit 1
set g_bEnableExclusiveMouseCapture 0
Once in the 3D cockpit, move the mouse to the upper left or upper right corner of the screen and click the 4th mouse button. That will lock the mouse cursor on that area and will minimize accidentally clicking anything in the 3D pit. This is not 100% safe -- if the screen is zoomed in and there is a button or switch where the mouse cursor is locked, activating anything from Helios may also register as a mouse-click but it is still safer than leaving the mouse cursor to move around. Also, with widescreen or multi-monitor setups, it is less likely that there will be a switch/button at the extreme corner of the screen.
The big advantage with Helios on a touchscreen is that it minimizes the time needed to be heads-down in the cockpit. Even when activating switches or buttons on the far corners of the side consoles, there is less need to pan the in-game view as much as needed when using a single-screen setup so again, that minimizes accidental button-clicks from the in-game mouse cursor.
Thursday, 15 October 2015
BMS Helios Profile Updated!
Hello fellow simmers!
I can't believe it's been almost 3 years since I've released my first Helios profile for Falcon 4 BMS! I never really used that profile for very long as I've started work on this new profile almost straight away but because of some issues with the profile (chart integration) and with real life getting in the way, I've not been able to finish the new profile until recently. As things slow down a bit in real life, I find myself getting back into playing BMS more and more and that was a great incentive to finishing the new profile.
As before, this is designed to work with a touchscreen with a resolution of 1920x1080 and I use this profile along with Morphine's profile for the TM Warthog and a custom .key file. I would like to give credit to xflight.de for the original images used, Red Dog for his charts, Lightning for his MFDE program, Kolbe for his .key file organization, Morphine for his original TM WH profile, and Falcas for his WDP program.
This is the profile at the start:
This is the profile when in the 3D world:
This is the Left Console:
This is the Right Console:
This is the list of airbase charts included:
And here are the charts displayed:
The quick list of airbase frequencies are also in:
Information from WDP's Data Card images can also be displayed:
Coordination Card:
Mission Briefing:
Here is a shot of the MFDE gauges in use:
And here is a shot of the MFDE gauges with the Falcon-extracted MFDs, DED, and PFL:
One of the main goals of this profile is that when using it with a touchscreen plus a voice-command software (I use VAC), there is absolutely no need to touch the mouse or keyboard once the pilot is in the 3D world. That means all the switches that work in the game is included here, so from ramp starts to changing HUD settings in-flight, everything can be done without touching the mouse or keyboard.
I think that's about it. All the other buttons/rotaries/switches/knobs should function as they should in the game.
Here are the settings I use for the Falcon BMS Display Extraction:
MFDs -- 331x331, Window ticked, Borders un-ticked, 290/1295 from the left screen edge, 326 from the top edge
DED -- 279x93, Window ticked, Borders un-ticked, 1232 from the left screen edge, 20 from the top edge
PFL -- 232x77, Window ticked, Borders un-ticked, 1228 from the left screen edge, 740 from the top edge
Here are the needed files:
-Ice's BMS ver.5 -- place this on your /Documents/Helios/Profiles directory
Custom Images -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.2 directory
.key file used -- put in your /BMS/User/Config directory. This is Morphine's profile with a few edits and adapted to Kolbe's format
Full layout -- possibly set as wallpaper on touchscreen as a guide on placing MFDE gauges
Reading through my old Helios profile thread, a few guys have had problems with installing my profile. Make sure that the .key file is named "Ice's BMS WH Profile v4" and note the apostrophe. Another issue was the EOSBus -- refer to this page of the old thread to see how other users have fixed the issue.
I can't believe it's been almost 3 years since I've released my first Helios profile for Falcon 4 BMS! I never really used that profile for very long as I've started work on this new profile almost straight away but because of some issues with the profile (chart integration) and with real life getting in the way, I've not been able to finish the new profile until recently. As things slow down a bit in real life, I find myself getting back into playing BMS more and more and that was a great incentive to finishing the new profile.
As before, this is designed to work with a touchscreen with a resolution of 1920x1080 and I use this profile along with Morphine's profile for the TM Warthog and a custom .key file. I would like to give credit to xflight.de for the original images used, Red Dog for his charts, Lightning for his MFDE program, Kolbe for his .key file organization, Morphine for his original TM WH profile, and Falcas for his WDP program.
This is the profile at the start:
This is the profile when in the 3D world:
This is the Left Console:
This is the Right Console:
This is the list of airbase charts included:
And here are the charts displayed:
The quick list of airbase frequencies are also in:
Information from WDP's Data Card images can also be displayed:
Coordination Card:
Mission Briefing:
Here is a shot of the MFDE gauges in use:
And here is a shot of the MFDE gauges with the Falcon-extracted MFDs, DED, and PFL:
One of the main goals of this profile is that when using it with a touchscreen plus a voice-command software (I use VAC), there is absolutely no need to touch the mouse or keyboard once the pilot is in the 3D world. That means all the switches that work in the game is included here, so from ramp starts to changing HUD settings in-flight, everything can be done without touching the mouse or keyboard.
- To display either side console, tap on the upper right/left corner of the screen.
- Accessing the airbase charts is done by tapping on the RWR.
- The data cards can be seen by tapping on the Mach meter.
- Tapping on the upper half of the left data card turns the page to the coordination card, the lower half turns the page to the briefing card. Tapping on the right data card resets the view to the data card.
- On the Left Console, the cockpit can be opened and closed by using the Anti-G Test button.
- On the Right Console, the Mal & Ind Lts switch on the Lighting Panel controls the NVG.
- On the ICP Panel, the HUD button declutters the HUD view, the HUD CLR button immediately below it cycles through the HUD colors individually while the HUD CLR button lower down cycles between the green HUD color and the white HUD color.
- On the Landing Gear Panel, the white Alt Gear button is the emergency gear release (Alt Gear Handle or AFAlternateGear).
- On the CMDS panel, the HMCS switch cycles between full-on and off.
- The MWS "switch" is actually a button that can show a cheat sheet of the CMDS programs. This cheat sheet image has to be created by the user; my default CMDS program image is included as a placeholder.
- Tapping on the left/right side of the altimeter changes the altimeter settings.
- Tapping on left/right upper 2/3rds of the HSI will change the course by +/-5 degrees, tapping on the lower 1/3rd will change the course by +/-1 degree.
- Tapping on the HDG knob will turn the knob facing upwards and tapping on left/right upper 2/3rds of the HSI will change the heading by +/-5 degrees, tapping on the lower 1/3rd will change the heading by +/-1 degree. Tap on the HDG knob again (knob facing downwards) to return to changing course when tapping on the HSI.
I think that's about it. All the other buttons/rotaries/switches/knobs should function as they should in the game.
Here are the settings I use for the Falcon BMS Display Extraction:
MFDs -- 331x331, Window ticked, Borders un-ticked, 290/1295 from the left screen edge, 326 from the top edge
DED -- 279x93, Window ticked, Borders un-ticked, 1232 from the left screen edge, 20 from the top edge
PFL -- 232x77, Window ticked, Borders un-ticked, 1228 from the left screen edge, 740 from the top edge
Here are the needed files:
-Ice's BMS ver.5 -- place this on your /Documents/Helios/Profiles directory
Custom Images -- unzip to your /Documents/Helios/Images directory, so you should end up with a /Documents/Helios/Images/-Ice's Falcon BMS ver.2 directory
.key file used -- put in your /BMS/User/Config directory. This is Morphine's profile with a few edits and adapted to Kolbe's format
Full layout -- possibly set as wallpaper on touchscreen as a guide on placing MFDE gauges
Reading through my old Helios profile thread, a few guys have had problems with installing my profile. Make sure that the .key file is named "Ice's BMS WH Profile v4" and note the apostrophe. Another issue was the EOSBus -- refer to this page of the old thread to see how other users have fixed the issue.
Subscribe to:
Posts (Atom)