Weepops Falcon BMS 4.34 Helios Profile…Updated
-
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?
-
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?
Picture says more than 1000 words.
That a helios profile which is itended to be run on a touchscreen monitor so you can flip/press all the switches. Could run on a non touch as well but the you loose all the input but All light like Eyebrow would still work.The white checkered areas (instruments gauges) have to be filled backlayed with one of the extractions tools such as MFDE,YAME, RTT or BMS Cockpit Display Extraction, where only the first two have the full range of instruments included.
Helios in future version might not need as it gets the extraction feature inbuild itself (currently based on the code that MFDE provides)
-
Thanks for the great job; but I am also missing te {F16GaugePack}.
Is this a separate software? Where canI buy/download this ?Thank You
-
See post 5 for answer.
In profile editor on left hand side is “toolbox”
Open >F-16 for ICP Panel and gauges
Open>F-16 Parts for ICP buttons
Drag and drop into your profileHope this helps weepop
-
Thank you weepop.
I renamed the profile to a .txt file; and edited it like a normal HTML file by removing the {F16GaugePack} sections.
Afterwards renamed it to a *.pfl file again.Thank You.
-
Hi Weepop, great work on your profile which I use since ages. Any chance you will do an upgrade to 4.35?
Keep up the good work and a happy, prosperous and healthy 2021!
Regards
Bikeman -
Hi Bikeman
Thats a definate yes. in fact I am almost finished with the update. will be posting shortly.
Happy New Year to you too.weepop
-
NEW PROFILE FOR 4.35 RELEASED see new post