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:
  • 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:
Please use the new /Images items to get the new button images.

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

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!

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.

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.

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.
<RWR zindex="4">
    <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>
This should be how the RWR should be set up in YAME:




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:
    <Binding BypassCascadingTriggers="False">
      <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>
One thing that needs changing is the monitor number.  Refer to my monitor arrangement below:



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.