YAME64 suite
-
-
Hi,
Is there a way with multi-monitor setup, to maintain original position for all windows opened prior to launch BMS? When I exit BMS all opened windows ( for example YAME app, Discord etc.) moves from original position on primary monitor and appears on extended monitors.
Regards
-
Yes, you need to place all your extra monitors to the left of your primary monitor.
Not in reality of course, but in the windows configuration. When BMS starts, it changes the resolution of your primary monitor. Thus all coordinates starting from that point shift with it. If you place all extra monitors left, those coordinates start with a negative value and don’t shift compared to the original 0/0 point.Hi,
Is there a way with multi-monitor setup, to maintain original position for all windows opened prior to launch BMS? When I exit BMS all opened windows ( for example YAME app, Discord etc.) moves from original position on primary monitor and appears on extended monitors.
Regards
-
yep, all secondary screens to the left and you’ll be fine
-
Yes, you need to place all your extra monitors to the left of your primary monitor.
Not in reality of course, but in the windows configuration. When BMS starts, it changes the resolution of your primary monitor. Thus all coordinates starting from that point shift with it. If you place all extra monitors left, those coordinates start with a negative value and don’t shift compared to the original 0/0 point.Good! I set all my extra to the right XD XD XD .
Ok try now and let you know.
Thankyou man!
-
Done, now it’s perfect.
Thank you guys!
-
Hi guys.
I am new to yame and i have issues with it and bms 4.34.
I followed the how-to on the site and i made also the registry modification indicated there.
The configuration in both 4.33 and 4.34 cfg for rtt extraction is to 1 (was there by default anyway ).
I tried different yame profiles and weepops helios+yame profile. All with the same results.
With 4.33 (unsurprisingly) yame works well.
With 4.34 it is able to extract some data (fuel flow, altimeter, altitude indicator etc all works) but it is not able to export any display, mfds rwr, ded etc etc.
Here i attach some screenshot to show this.
You can see the flight instruments animated but no displays as I described.
Can someone help me resolving this?
Thankshttps://uploads.tapatalk-cdn.com/20200418/7282cb6dfdf92ca0fa7b2784ac48f93a.pnghttps://uploads.tapatalk-cdn.com/20200418/560d7736d2b9e97c32b84c390378dffe.png
I found the reason for the lack of display of MFD, RWR, DED.
Do not change the registry key, “C: \ Falcon BMS 4.33 U1” to “C: \ Falcon BMS 4.34”, as indicated on the Yame website.
To launch Falcon BMS do not use the button on the launcher but add a “Batch”. -
Do not change the registry key, “C: \ Falcon BMS 4.33 U1” to “C: \ Falcon BMS 4.34”, as indicated on the Yame website.
The webpage clearly mentions it in red: warning, some people report issues with method 3.1!
So it seems you are one of those -
I’ve posted on Reddit but I’ll seek for help here to.
I’m trying to use the MFDs on my Surface Pro 4 but it doesn’t send the callbacks. Do I have to set ALL the callbacks manually from the client? Isn’t there a preset I can use? Or transfer the .key files from BMS to YAME?
-
Maybe have a look on Helios for building the inputs. And even another tool to extract. Like MFDE as it works out of the box with 4.34
15.6 " touch with Helios and MFDEGesendet von meinem SM-G930F mit Tapatalk
-
What’s MFDE? YAME64? Why do I need helios if YAME is supposed to send callbacks?
-
What’s MFDE? YAME64? Why do I need helios if YAME is supposed to send callbacks?
Cause Yame doesn’t work out of the box with BMS 4.34 you need to have 4.33 installed as well as hacking around with the registry.
Helios provides way more capabilities to build inputs to BMS you can literally build a full virtual touchable cockpit.
MFDE does the same as YAME it extracts Displays and gauges from BMS shared memory.
At the Moment MFDE would always be my preferred extraction tool over YAME as it currently way easier to setup and use. Not need to have 4.33 installed, extracted Displays and gauges.And YAME is currently not actively developed.
Your asking to have a working solution for external MFD with working input to BMS. I just try to provide you one
And to answer your initial question
Yes you would have to setup the callbacks manuallyhttps://github.com/lightningviper/lightningstools
https://github.com/BlueFinBima/Helios
Gesendet von meinem SM-G930F mit Tapatalk
-
as well as hacking around with the registry.
Not correct, It’s working for me with no hack in the registry. All it takes Indeed is having 4.33 installed, which is needed as well if you want to convert TE, so no real harm done on that front.
And YAME is currently not actively developed.
Neither is MFDE.
Beside for CPD users, YAME is the only option working with BMS for instance.
CPD extractor from MFDE does not work out of the shelf. You may have made it working for you because you modified it for your own tests, but for us users it does not work out of the shelf.
MFDE works though.As for the MFD, the most native solutiion is the built in way of BMS. in 4.34 you have either the display extraction from the launcher menu aor the RTT clients. Both works perfectly for HUD, RWR, MFDs, DED, PFD
but you Don’t get gauges or the fancy stuff yame or MFD extracts.Nothing is ever perfect
but pitbuilder would know if there was Something that wasn’t possible to do. and that’s clearly not the case. You might need extra software, but all is working fine one way or another -
If a registry hack is needed or not is currently unclear. I would need to have it on my machine
I have been asked if I would take over or contribute to Yame but have to reject due to time restrictions.
CPD works without any changes to the code. I’m currently debugging why the compiled version from git does not work.
As lighningtools are Open source and people like myself use and work on it, it is actively developed.
Even Helios is currently extended to get native display extraction (based of MFDE library)
Gesendet von meinem SM-G930F mit Tapatalk
-
CPD works without any changes to the code. I’m currently debugging why the compiled version from git does not work.
As lighningtools are Open source and people like myself use and work on it, it is actively developedGood to know and I’m personnally looking forward to play around with CPD from Lightning again (I used it before)
So I hope you will release your work to us here once done That way Indeed, we can say that this software was Indeed still being developpedCheers
-
MFDE doesn’t always work (Polar, FO Balkan to name a couple).
As for Helios for BMS…it’s a wonderful software that is actively developed but with BMS its issue is differences between individual key files on which it heavily relies.
So each person needs to adapt it to his own key file.I’m currently using a combination of MFDE, RTT and Helios and while it works fine by me not all users can get good extractions with low FPS without a huge hassle.
YAME64 used to be a solution but way to many are having issues, as seen with repeated posts regarding the work around (which is simple for many but not all).
If there could be a simple extractions tool, actively developed, for all instruments that is included within BMS…I think many would benefit.
The power users shall be able to enhance with available other tools.Sent from my iPhone using Tapatalk
-
MFDE doesn’t always work (Polar, FO Balkan to name a couple).
As for Helios for BMS…it’s a wonderful software that is actively developed but with BMS its issue is differences between individual key files on which it heavily relies.
So each person needs to adapt it to his own key file.Sent from my iPhone using Tapatalk
I have tested MFDE on all available theaters with 4.34 it works on all. Technically the sharedMemory extraction is not related to theater at all.
Another point is that helios relys on callbacks taken from keyfiles and thats the great advantage. As long as 2 different user have at least a keystroke,keycombination bound to a callback it doesn’t matter if user A who made the profile has his callback bound to keystroke “X” while user B who uses the profile from user A has bound that callback to keystroke “Y”
Polar with working MFDE
-
Hi, there !
Just downloaded and started to use YAME64 with BMS 4.33 to have the Mirage 2000-10 (!) simpit I’m currently building go live. Here is a link of my building :
http://www.checksix-forums.com/viewtopic.php?f=286&t=181224&sid=ee3b025316720d35a0d75f2bfb21f1ea&start=1000The digital fuel and engine gauges are pretty similar to the ones used in our mighty french fighter.
I was just wondering (dreaming ?) if there was any chance those digital gauges could be modified (or maybe just their layout) to better reflect the Mirage 2000 ones ?
I will post (hopefully next week) some pix of my layout compared to the real one.
All the best
EnZo
-
Hi, there !
Just downloaded and started to use YAME64 with BMS 4.33 to have the Mirage 2000-10 (!) simpit I’m currently building go live. Here is a link of my building :
http://www.checksix-forums.com/viewtopic.php?f=286&t=181224&sid=ee3b025316720d35a0d75f2bfb21f1ea&start=1000The digital fuel and engine gauges are pretty similar to the ones used in our mighty french fighter.
I was just wondering (dreaming ?) if there was any chance those digital gauges could be modified (or maybe just their layout) to better reflect the Mirage 2000 ones ?
I will post (hopefully next week) some pix of my layout compared to the real one.
All the best
EnZo
I had been asked to take over development of YAME but had to refuse due to other projects. If noone else had taken over don’t expect to get anything updated in YAME anytime soon.
Alternative would be MFDE as it’s open source and with some .NET C# knowledge you could make your own gauges based on that code. -
And a partnership with the Helios team is not possible?
Helios 1.6 will manage the extraction of textures, it only needs the implementation of a CP60 as in Yame.