-Ice's Falcon BMS Helios Profile Updated… Again!
-
I took the jet up for a flight last night and much to my amazement-everything worked. Your Helios profile and target script were right on and I loved YAMA and the map with waypoints. If this package were a commercial product, I would have definitely bought it.
Did you use the Korea KTO.png I supplied in my blog? That’s a higher-res version to be used in the moving map.
One change that I am considering is to add a next/prior steer point command to the shifted left and right mic switch, but I am having an issue locating the key command for this ICP button. Any thoughts?
I presume you are talking about SimICPPrevious and SimICPNext?
Your XML file provided is not compatible with YAME64 current version. It renames the file to old.
Do I have to manually place all of the YAME gauges again? Or do you have an updated layout file?Did you download the Ice1ScreenSetup v121 from this page ?? That is specific for YAME v1.21.
-
Did you use the Korea KTO.png I supplied in my blog? That’s a higher-res version to be used in the moving map.
I presume you are talking about SimICPPrevious and SimICPNext?
Did you download the Ice1ScreenSetup v121 from this page ?? That is specific for YAME v1.21.
Did not see that page. I just did it all by hand, using your config file.
Thanks!
-
Did not see that page. I just did it all by hand, using your config file.
Thanks!No offense, WombRaider, but can you tell me how you “did not see that page?” Did you just CLICK THIS LINK and end up on the very first blog post? I’m just trying to figure out how you did not see the latest blog post, why that happened, and so that I can fix any issues if there are any. Thanks!!
Oh, and use the new profile I’ve linked. Even if you’ve “moved” each gauge to a new profile by hand, I’ve got loads of key combinations mapped in the new profile that you may be missing –- these key combos are for use with the CPD moving map. So I suggest just downloading and using my v121 profile. Enjoy!
-
Yes, I clicked that link. It’s the only link you provide in your OP. Perhaps update the link to the newest version?
I ended up using your file. But I set the profile up to use my keyfile, because my x-55 was a PITA to get working right in Falcon. When I started into a mission the aircraft rolled hard left. I figured out that your key commands on the CPD conflicted with the trim and some other functions (which I already have mapped to my stick) on my keyfile so I re-mapped those keys. Everything seems to be working nicely.
Thanks for your help!
-
Yes, I clicked that link. It’s the only link you provide in your OP. Perhaps update the link to the newest version?
Makes sense. I may add a link that will go directly to the blog itself, not just one particular post. However, on that page, if you click on the text “-Ice’s Helios Profile for Falcon 4 BMS,” it will take you to the blog and you will see the rest of the posts.
I ended up using your file. But I set the profile up to use my keyfile, because my x-55 was a PITA to get working right in Falcon. When I started into a mission the aircraft rolled hard left. I figured out that your key commands on the CPD conflicted with the trim and some other functions (which I already have mapped to my stick) on my keyfile so I re-mapped those keys. Everything seems to be working nicely.
Yeah, the YAME profile was made in conjunction with my BMS .key file which is used in Helios. If you’re just using YAME, that’s fine, you can use your own .key file. If you’re using YAME and Helios and not using my .key file, then you will run into some issues.
-
What kinds of issues? I notice some of the view keys are not working. Nothing crucial so far. The keyfile change was done in the Helios profile editor.
-
It depends how similar your .key file is to mine.
-
It was A LOT different. I used the default keyfile. I noticed that the switches on the side panels were not working so I switched to your keyfile.
Is there a way to start with all of the switches on? A lot of the power switches are defaulted -off-
-
Is there a way to start with all of the switches on? A lot of the power switches are defaulted -off-
It’s on the to-do list The nice thing about switch state callbacks is that if the switch is OFF in Helios but it’s ON in the sim, flicking it onto the ON position simply syncs the switches so there is no danger there.
-
Go to CLIENT -> WINDOWS -> RIGHT SCREEN in YAME and make sure MASKED is ticked. If it isn’t, then click EDIT, tick the MASKED box, and click SAVE.
Also, with the new profile, you can make a shortcut in your YAME folder, point the YAME button in helios to that shortcut, and you’re done.
In my current setup, I start Helios first, then use the buttons on the SYSTEM panel to startup what I need. Check out p.14 of the YAME64_manual_v1.2.pdf to find out more. My current shortcut has this on the target box: Y:\YAME64\YAME64.exe -client -layout Ice1ScreenSetup_v121.xml -minimize
Hi Ice,
As I am enjoying this, I am trying to fine-tune with your recommendations. When Helios opens, I push on your “System” menu and I get all the buttons, the YAME one is not yet working. So I created the shortcut you mention above (with my C:\ directory, not your Y:). But how do you assign this YAME button from your System Menu to the shortcut? It’s a YAME64.png button and I don’t know how to point it towards the shortcut.
Thanks for the help,Johan
-
Go to your YAME folder
Right click on the YAME64.exe file, click on CREATE SHORTCUT
Rename the shortcut to something useful, in my case, I named it YAME64 1Screen… I also have another shortcut called YAME64 2Screen… pretty self-explanatory
Right click on your shortcut, click on PROPERTIES
Unter the TARGET: box, add the following extensions “-client -layout Ice1ScreenSetup_v121.xml -minimize” minus the quotes. Mine looks like this: Y:\YAME64\YAME64.exe -client -layout Ice1ScreenSetup_v121.xml -minimize
Click OKOpen my Helios setup in the Helios Profile Editor
Navigate to the YAME button
Under OUTPUT -> BINDINGS -> PUSHED, make sure it points to the correct .lnk file. For example, mine looks like this: Y:\YAME64\YAME64 1Screen.lnk –- note how the naming is done
SaveGood luck!!
-
Thank you Ice, I will try this tonight.
…just did it, very nice, it works great.
Thank you,Johan
-
Hi Ice!
I finally got both YAME and Helios working together, I’ve tested all the buttons and they work perfectly but the landing gear lever does not work for me.
I’ve gone to BMS setup and moved the landing gear to test if it produced the desired button but it didn’t so I configured it in the BMS keyfile but still nothing on flight…
Any idea what’s happening?
Thanks. Regards
-
I’m using YAME 1.2 I think. I didn’t update to the hot fix yet I guess. My bad.
Can’t do anything about it for several days though. I’ll try taking a look at it when I get home and seeing what I can figure out.
You can certainly try setting up the gauges yourself and opening my xml in a text editor so you can use it as a reference for where everything goes. Would be a little tedious but it would work.
Sent from my iPhone using Tapatalk
Just in case anyone had a problem with mine (Ice, I’m sorry but I thought he was talking to me), I installed YAME 1.21 and my layout works fine with it.
-
the landing gear lever does not work for me.
Not sure what’s going on here but it’s working on my system for sure. Just tested again now. Besides, if the LG lever were not working, it’d be an issue straight away I would suggest re-downloading my .key file just to be sure you have the correct, original one.
Just in case anyone had a problem with mine (Ice, I’m sorry but I thought he was talking to me), I installed YAME 1.21 and my layout works fine with it.
No need to apologize His original issue was because he was using the first YAME release version which is not compatible with 1.20. Any profile made in 1.20 should be compatible with 1.21.
-
Not sure what’s going on here but it’s working on my system for sure. Just tested again now. Besides, if the LG lever were not working, it’d be an issue straight away I would suggest re-downloading my .key file just to be sure you have the correct, original one.
Downloaded it again from here: http://www.mediafire.com/file/k85jg9eek97h0m9/BMS±+FPM+by±Ice.key but still doesn’t work…
If i change it in Falcon with the mouse it does move in Helios, but It doesn’t do anything when I click on the touch screen (I mean the lever moves but It doesn’t produce any effect)…
I’ve checked the profile and the callbacks seem to be configured ok…
Regards.
-
Hmmm… not sure what to tell you. Did you fiddle with my Helios profile? Maybe download a new copy of my Helios profile and see if that works? Are you using a TM WH HOTAS? Does the FLAPS switch work with putting the gear up/down?
-
ICE
I have taken the liberty of borrowing Rogue’s method of having 3 profiles in one. The switch in the combined console panel with a red background was taken from Rogue’s profile. Thank you Rogue. However, instead of using his key commands, I used your method #2 from your video tutorial. Most of the profile works, but I have issues with all of the radio volume dials. I guess I will have to do that manually. I couldn’t figure out how to label the red panel.Down is cold start
middle is hot start
up is air startThis is still in the experimental stages, but I thought you would like to see what some of your students are doing with Helios.
-
Hmmm… not sure what to tell you. Did you fiddle with my Helios profile? Maybe download a new copy of my Helios profile and see if that works? Are you using a TM WH HOTAS? Does the FLAPS switch work with putting the gear up/down?
Looks like the AFGearUp or AFGearDown callbacks doesn’t work for me… I’ve put the SIMCATI and SIMCATIII callbacks just for testing in the landing gear lever and and they do work fine, can I send a keystroke instead of a callback?
Regards.
-
The switch to control SEQ/RET Up and Down is VERY inconstant. Any tips?