-Ice's Falcon BMS Helios Profile Updated… Again!
-
Nothing major - will post at weekend when I can get to my pit - working away at the moment - good old London town ��
-
Sure, no rush. What did Red Dog say?
I know how to make PDFs from other files, like MS Word or Excel or a picture, but I don’t really know how to edit them once they are PDF already. I think you need the source material for that and obviously, that is with Red Dog. Can you recall which areas or locations the anomalies are? Radio freq? TCN channels? Approach plates telling you to go to 500ft right into the side of the mountain? Hehehehe….
-
Nothing dramatic - choongwon approach to 16 left and right tells you to hold a 20 bank angle - you can’t get onto the correct radial if you hold 20 deg - it should be 40 deg which is a bit tight so may be the chart is wrong - but certainly to 20 bank angle is wrong - try it ��
No reply from Red Dog but I suspect he has bigger things to do - all hail the devs!!!
-
:woohoo:^ Hey Ironoman
@ Ice. I suspect an issue with YAME rather than your profile, but I’ll post here first then move it to the YAME page when your happy it’s nothing to do with you.
I was doing a simulated IFR recovery to Kunsan 18 yesterday. Set the TACAN to Kunsan (75X if I remember correctly) and the HSI TACAN needle stated spinning round and round constantly at a fairly high rate. When I say needle, I mean the whole needle - not just the white arrowhead at the top.
This did not match with the (correct) HSI indications in sim where the HSI was locked onto Kunsans beacon and was quite still.
Before this occoured I had been using TACAN in A-A mode with no issue.
- Sharpe
-
@Ice,
Separate point to that above. 2 questions:-
Do you have a lead time on getting the new single screen layout for departure/arrivals set up for all the KTO airbases?
-
Do you have any plans to include plates from other theatres in your profile (e.g. Isreal/Siani or Balkens)?
I was thinking a cool way to implement this might be similar to the way the comms menus are laid out and work. E.g. you select tower and it holds that menu open for you while you use it until you select something else (like AWACS).
You could do this for theatres so that the first time you need a chart you select the theartre (e.g. KTO) then you get the menu as it exists and works in the profile now with the list of airbases.
Just a thought.
- Sharpe
-
-
I was doing a simulated IFR recovery to Kunsan 18 yesterday. Set the TACAN to Kunsan (75X if I remember correctly) and the HSI TACAN needle stated spinning round and round constantly at a fairly high rate. When I say needle, I mean the whole needle - not just the white arrowhead at the top.
This did not match with the (correct) HSI indications in sim where the HSI was locked onto Kunsans beacon and was quite still.
Before this occoured I had been using TACAN in A-A mode with no issue.I’m not 100% proficient with IFR stuff so I may be wrong here, but I usually play with the ILS on the AAR TE… I enter Kunsan tower freq, ILS freq, ILS LOC and fly in with ILS T/R and TCN or ILS/TCN mode on the INSTR panel. The needles work fine for me. Can you tell me exactly what you’re doing and I might replicate it? I tried fiddling with stuff just know to get the needle to rotate but all I get are the “flags” to come up.
- Do you have a lead time on getting the new single screen layout for departure/arrivals set up for all the KTO airbases?
- Do you have any plans to include plates from other theatres in your profile (e.g. Isreal/Siani or Balkens)?
- Lead time will be 3-4 Falcon weeks, as usual I can whip up a quick profile with your favorite airbases if you want, but the whole thing will take a while.
- Yes. Still figuring out how to do this though… maybe have separate profiles for each theatre that way a single profile does not get too “heavy.”
I was thinking a cool way to implement this might be similar to the way the comms menus are laid out and work. E.g. you select tower and it holds that menu open for you while you use it until you select something else (like AWACS).
You could do this for theatres so that the first time you need a chart you select the theartre (e.g. KTO) then you get the menu as it exists and works in the profile now with the list of airbases.The charts profile already works like this.
-
Hi Ice,
I am a new Helios user and trying to use my ipad for the F16 cockpit. My ipad works fine as a second screen, I can see your layout correctly, but when I launch BMS, none of the gauges appear on the layout. I have followed your procedure step by step, YAME64 is installed and running…I am not sure what I am missing. Maybe you already have responded to this problem, so I apologize in advance. Please let me know if there is a post I should look at.
Thank you for this wonderful new tool I just discovered.Johan
-
I’m not sure if Helios and YAME works for iPad… and last I heard, even Microsoft Surface tablet user had an issue too.
I have zero experience with tablets; my last foray into this was using and iPad 2 and iFlyBMS so I am way out of touch with the current tech. How are you getting Helios to show up in your iPad? Does YAME show up there as well?
Even if we get this working, I suspect the iPad will not be usable for you unless you trigger everything with a stylus. The touch areas required to work the controls will be very, very tiny. You can use the iPad to show you your MFDs, but to have it at a usable size and have the MFD OSBs at a workable size, that’ll be all you can really fit into your iPad real estate…. so my Helios profile won’t be the solution for you, I’m afraid.
-
Thank you for your reply. Helios and Yame are on my main monitor, I have assigned the ipad as a second monitor through an app called “Duet”, and it works. I can see my monitor and the ipad on the upper left corner of the Helios window.
I have created a small profile with just a couple of single gauges and when I launch BMS, I can see them on the ipad and they are working fine. So I am quite sure that your profile would work as well, it is just much more elaborate than mine. I just don’t know if I am missing some setting…
I understand the size issue you are mentioning, the use of my ipad is just a test. When I am confident I can see all these gauges working, I will purchase a much larger touch monitor (Dell maybe?).
I will continue to play around and let you know if I am successful.
Thanks again,Johan
-
Hello Johan,
As I said, I’m unfamiliar with this so I don’t even know what you’re talking about. Going back to your first post…. Helios is for switch control but YAME is the one displaying the gauges… if none of them appear on the layout, then you’ve probably not installed my profile for YAME. Take a look at the blog again and download the Ice1ScreenSetup.xml file, put that in your \YAME64\layouts directory, and load that when you start the YAME UI.
My suggestion would be just to try out my profile on a secondary monitor or a TV… it’s much more straightforward to set up. You will, of course, not be able to use any of the touch features but it should be enough for proof-of-concept to you. When you take the jump, I would recommend at least a 22" touchscreen, but bigger is always better, if nothing but to increase the touch area sizes.
-
Thank you Ice, I will follow the advice and try on a secondary regular monitor.
Johan
-
2nd implementation – Departure and approach plates for Kunsan and Pusan…
Please feel free to give it a try and tell me your thoughts! Credits to Sharpe for the idea!
Thanks!
-
Hi Ice,
I am new at Yame64, so I am trying to understand some of the settings.
There are a few default layout files that came with the program like:
blck50_analog.xml or epaf_atd-ehsi.xml, etc…when I load those and run YAME Client, the panel window opens and I see all the gauges. They are working fine with BMS launched.
When I load Ice1ScreenSetup.xml, I get an error message saying:
“Window mask not correctly created, now run without masking”
And no panel opens when I start YAME Client….
Please let me know if you have encountered this before.
Thank you for all the help,Johan
-
That’s because those profile don’t use masking, mine does…. although I think I can do without it??? No, I don’t think so as my CPD window will need masking…
Here’s how you force YAME to create masking:
Start YAME
On the UI, go to CLIENT -> MISC -> LOAD LAYOUT and load my Ice1ScreenSetup.xml file
Click APPLY
Go to CLIENT -> GAUGES -> FLIGHT INSTRUMENTS
Click APPLY
Go to RUN and click START YAME CLIENTThere will be a small window that will come up with some %% numbers as YAME makes the masks. Windows may even report YAME as not responding, just tell it to wait for YAME to respond. As soon as YAME finishes its voodoo black magic mumbo-jumbo, you should see the gauges come up.
Good luck!
-
Hi Ice,
Thank you, it works. I see your gauges when running YAME CLIENT and making some monitor layout tweaks.
I have a follow up question:
When I run Helios and load your profile, it shows that your monitor#2 is to the left. I can reset monitors according to my screen layout (my monitor #2 is on the right) and save it under a modified name. However, this action doesn’t modify your Ice1ScreenSetup.xml which still shows your gauge screen (monitor#2) to the left. Correct? (posx has a “minus” sign). Therefore, running Helios with my modified Helios profile will show all the buttons to the right (my monitor #2 is on the right), and running YAME with your loaded key will show all the gauges to the left…Thank you for confirming.
<window><name>RIGHT SCREEN</name>
<width>1920</width>
<height>1080</height>
<posx>-1920</posx>
<posy>0</posy>
<fullscreen>true</fullscreen>
<border>false</border>
<visible>true</visible>
<background>RIGHT SCREEN.png</background><antialias>true</antialias></window>
-
Correct, because YAME and Helios are two different programs. First, I suggest having your 2nd screen to the LEFT of your main screen as far as Windows Display Settings is concerned, regardless of where your monitor is physically, especially if you play fullscreen mode.
Second, assuming you have two 1920x1080 monitors and continue to use your current setup, then yes, change POSX to 1920 (positive instead of negative). You’ll also have to change POSX for the CPD MAP SCREEN window to 2643, POSY should stay the same (436).
-
Hi Ice,
Just checking back with you to give you an update. I received and installed the Dell S2240t touchscreen, loaded the latest drivers and tested the monitor. It works fine with regular softwares (Excel, Word, etc…). With BMS, I see your panel, I load your profile in YAME and Start Client, then launch BMS. All the gauges appear on the touch screen and needles are moving. But there is no action when I press the keys, it doesn’t seem to communicate back. I see the keys illuminating when I push on them, but no reaction…I haven’t loaded the Target script, could that be the problem? Thanks for letting me know if you have a idea for a solution. Should I reinstall Helios?
Thanks for your help,Johan
-
refer to this webpage for troubleshooting profile issues, http://ihpff4bms.blogspot.co.uk/2017/03/profile-not-working.html
-
Thank you. I had already done that and corrected accordingly. I will try to find the thread you are referencing to “Sandman”.
Johan
-
Just checking back with you to give you an update. I received and installed the Dell S2240t touchscreen, loaded the latest drivers and tested the monitor. It works fine with regular softwares (Excel, Word, etc…). With BMS, I see your panel, I load your profile in YAME and Start Client, then launch BMS. All the gauges appear on the touch screen and needles are moving. But there is no action when I press the keys, it doesn’t seem to communicate back. I see the keys illuminating when I push on them, but no reaction…I haven’t loaded the Target script, could that be the problem? Thanks for letting me know if you have a idea for a solution. Should I reinstall Helios?
Hello Johan,
I’m assuming you’ve also started up Helios… go to SETUP -> CONTROLLERS and see if stuff responds there. Try moving the MASTER ARM switch to the up/mid/down positions and see if the correct callback is identified. If you have followed the link Fletch posted, it should work. The TARGET script is more for the WH interfacing with the .key file (and thus, the sim) so the Helios profile should work regardless of the TARGET script being loaded or not.