Weepops Falcon BMS 4.34 Helios Profile…Updated
-
The link is broken. It shortens and gives the false URL. The right one is:
https://www.mediafire.com/folder/6ejj30zf2slhc/BMS_upgrade_to_4.34
The one in the opening post is:```
http://www.mediafire.com/folder/6ejj...pgrade_to_4.34So this should work: [https://www.mediafire.com/folder/6ejj30zf2slhc/BMS_upgrade_to_4.34](https://www.mediafire.com/folder/6ejj30zf2slhc/BMS_upgrade_to_4.34) Without Mediafire Premium one has to download every file in every folder seperate. I would sugest to use a different hoster like Dropbox or OneDrive or provide a zip where every needed files are in.
-
Hi,
thanks for your profile.
Anyway i am trying to use it but i am quite new to Yame and also with Helios i am not too much proficient (i use premade profile for DCS but the only needed change there is to reset monitor configuration in Helios).
When i open your profile in Helios i see that the panels are on the main monitor, while i am using the touchscreen as second monitor logically (per windows) on the right of my main panel physically under it.
How i can copy the panels from 1 screen to 2 screen in Helios?I am trying to figure it out but right clicking does not do anything and also i don’t see any option to move stuff from monitor 1 to monitor 2.
Thanks for help -
Sorry i figured it out……thanks
Now i need to understand how Yame works…there i am an absolute noob -
Guys i need some serious help.
I am trying to use the profile but i am stuck and cannot find any tutorial or guide.
I read also the yame manual but I don’t understand why things don’t work i did everything following the instructions.- problem with Helios
I loaded the profile in Helios and then resetted it for my monitor configuration.
Then I started it and started falcon in windowed mode. Loaded the weepops keyfile in falcon.
Then when in the cockpit i try to operate my touch screen nothing happens in the sim…no one of the buttons works.
I tried to see in helios in the output part but everything seems normal there.
That is strange, i am quite familiar with helios with dcs world and there everything works. But it is the first time with falcon.- yame instruments don’t show
I am not familiar with Yame I tried it today for the first time so maybe i did something wrong.
But i read the whole manual and i did everything requested to make it work with 4.34. Obviously i loaded weepop xml
start the client and then i start the sim.
Yame sees falcon bms as running but then in the sim i see no instruments.Is there some easy tutorial for yame?
I looked on YouTube but all i find is people showing their wonderful panels but without a clue on how to make it work.
Thanks -
Are you running Helios as administrator. When I started using Helios that was the issue of BMS not recognizing any Helios input.
For Yame have you already installed 4.33 parallel to 4.34 at least on my side only with both installed and the registry hack as stated on the Yame website it’s working
Gesendet von meinem SM-G930F mit Tapatalk
-
yes i did both the things you mentioned.
Anyway about the first problem i could have found the solution. I did not know that helios needs the falcon keyfile (neither is mentioned it the instructions in the first post) i saw in the interface in helios that it was pointing to the wrong keyfile (c:\Falcon BMS\ etc etc while my install is on D:) so i corrected that and now will check if it works.
About yame i think that the problem could be that the window is configured on monitor 0 (by default) reading the manual i should make it appear on monitor 2, but the instructions are not clear.
I have a 3440x1440 monitor (main one) and a 1920x1080 touch screen on its right (logically but under it phisically) so i try to put +1440 for x in yame option but the windows don’t change to monitor 2.
The manual is not clear on how to configure windows and how to configure the gauges and with which coordinates. -
yes i did both the things you mentioned.
Anyway about the first problem i could have found the solution. I did not know that helios needs the falcon keyfile (neither is mentioned it the instructions in the first post) i saw in the interface in helios that it was pointing to the wrong keyfile (c:\Falcon BMS\ etc etc while my install is on D:) so i corrected that and now will check if it works.
About yame i think that the problem could be that the window is configured on monitor 0 (by default) reading the manual i should make it appear on monitor 2, but the instructions are not clear.
I have a 3440x1440 monitor (main one) and a 1920x1080 touch screen on its right (logically but under it phisically) so i try to put +1440 for x in yame option but the windows don’t change to monitor 2.
The manual is not clear on how to configure windows and how to configure the gauges and with which coordinates.OK i solved the helios issue with the keybind.
About Yame well….i simply don’t understand how it works. The more i read the manual the more i am confused
I changed the value in window and if i do edit gauges the instruments appears in the right position on the second monitor.
Then i start the client and the instruments appears there but my computer become a slide show. If i load falcon then instead of the istruments i see black images and the fps in the simulator is 1.
if i disable the instruments (in weepops profile there is already binded the f12 key) my fps go back to 100 (my monitor is 100hz).
I will try to post imagesEDIT: I tried one of the default yame profiles (the one with the pedestal) and there something works. I am not able to see the mfds from falcon, but the data in the pedestal are there. Also i don’t have any slide show.
So something must be wrong with weepops profile and my system. -
Picture says more than thousand words.
Monitor 2 is my primary Monotor so upper left corner of #2 is 0,0
#1 is my touchscreen logical to the left but physical underneath. So in order to get Yame window on the touchscreen the window width,height set to the resolution of the touchscreen and position X - touchscreen widthThe extracted Gauges,MFD positions are from the 0,0 position of the YAME window
I have a 3440x1440 monitor (main one) and a 1920x1080 touch screen on its right (logically but under it phisically) so i try to put +1440 for x in yame option but the windows don’t change to monitor 2.
The manual is not clear on how to configure windows and how to configure the gauges and with which coordinates.so if your #1 is logically on the right side and your #0 is 3440 x 1440 your Yame X position has to be >= 3440
-
Thanks, I think I figured out yame window position but still mfds, rwr, ded and fpl fail to be extracted from yame.
Here i have some pictures of my configuration and the results.
Monitor 1
Monitor 2
Yame window config
And this is with the helios profile working, but yame not extracting the displays but extracting data because the analog instruments works
-
Can you make a screen of your Yame Gauges Tab wich shows the MGS setup
Gesendet von meinem SM-G930F mit Tapatalk
-
Do you mean this?
Sorry butni don’t know what mgs stands for
-
Looks ok MGS = MFD after mobile auto correction kicks in.
If you start Yame and run the client without having the Helios profile running do you at least get the black boxes for the MFD shown on your second monitor?
Gesendet von meinem SM-G930F mit Tapatalk
-
Yes the black box are there (the same that you see with helios overlay). Tomorrow i will do a screenshot of yame only without helios
-
Ok I think I will give up for now. I cannot do any troubleshooting as the instructions are scarce and not clear.
I tried bms 4.33 and the extraction worked correctly. Including all the displays.
I did the configuration as yame how to page decripted for falcon bms 4.34 including the registry modification.Here are the pictures I promised without helios running as you can see yame is able to take data from the sim, but it is not able to extract displays. So rwr, mfds, ded and fpl are not extracted in 4.34
-
Ok I think I will give up for now. I cannot do any troubleshooting as the instructions are scarce and not clear.
I tried bms 4.33 and the extraction worked correctly. Including all the displays.
I did the configuration as yame how to page decripted for falcon bms 4.34 including the registry modification.Here are the pictures I promised without helios running as you can see yame is able to take data from the sim, but it is not able to extract displays. So rwr, mfds, ded and fpl are not extracted in 4.34
https://uploads.tapatalk-cdn.com/20200418/6714f2241e8b6df42e3a1e92c43c374c.pnghttps://uploads.tapatalk-cdn.com/20200418/b580a28e592921ada90f303947d06bf9.png
I had the same problem before. But I fixed my MFD’s not extracting (gauges were extracting just like yours) by installing all the incremental updates for 4.33.
-
@kEnnY_m.:
I had the same problem before. But I fixed my MFD’s not extracting (gauges were extracting just like yours) by installing all the incremental updates for 4.33.
I’m running YAME64 with 4.33 U1 so that should not be an issue, but maybe it is with Helios?. Virus, have you tried creating a new “Window” in Yame64 (leave Helios out of it for now), let’s say call it MFD_Left, and position it on the screen wherever just for a test. Set the left MFD to go to the new window, start 4.34 and jump into IA to see if the MFD goes live. Also, even though you are running 4.34, you do have the “Global” tab pointing to your install of 4.33, yes? The registry hack I came up with causes problems and I let Focal know as soon as I did, hope you are not using that… Your Global tab needs to look like this (with your correct path to 4.33 and with whatever theater you use of course)…
-
You could still go with MFDE Extractor for all gauges with Helios. which woks with 4.34 and no need to have 4.33 installed at all. Helios doesn’t care whch tool is used for the extraction. And btw Helios gets updated to have extraction natively included and the code to do this is based of of MFDE not Yame
-
You could still go with MFDE Extractor for all gauges with Helios. which woks with 4.34 and no need to have 4.33 installed at all. Helios doesn’t care whch tool is used for the extraction. And btw Helios gets updated to have extraction natively included and the code to do this is based of of MFDE not Yame
My ignorance is without limits and I know zip about Helios and MFDE extractor, would love to hear exactly what they do and how they work vs. Yame64 by itself. Other than the 4.33 fakeout and having to load the same theaters in 4.33 as you use in 4.34 U4, Yame64 is so easy to use I don’t see a need for me to use separate extraction/display tools. Put an MFD on my touchscreen, be sure touch is enabled in Yame, and all the OSBs just work without assigning callbacks or any other work. I just wish someone would update it to work with the current version without the 4.33 workaround!
-
This threat is around a Helios profile. So the OSB buttons would be handled by Helios in any way and not by YAME.
Gesendet von meinem SM-G930F mit Tapatalk
-
This threat is around a Helios profile. So the OSB buttons would be handled by Helios in any way and not by YAME.
Gesendet von meinem SM-G930F mit Tapatalk
Got it, not sure how I got here…. lol. Is there a breakdown or Helios vs. YAME64 vs. MFDE Extractor features somewhere? I’m just not clear on why one or the other?