YAME64 suite
-
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.
-
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.
As I came up with the idea to integrate display extraction into Helios I realized that wheelchook was already working on it, so I stepped back and just provieded information mainly on how to identify areas for reading displays from F4TexSharedMem.
For CPD there is a partially working one based on C# as well it’s just a seperate project within lighningtools. I will have a look into 1.6 branch in order to get work on it to integrate the lightning CPD into Helios -
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.Thx for your reply. Unfortunatly, I don’t have any .NET C# knowledge (and far from that :roll:).
No prob, I’ll use YAME64 the way it is now and stay tuned for any update. -
Thank you oakdesign for your interest in improving Falcon software.
We are in the middle of testing the 1.6, the EHSI has been modernized and repaired.
The CP60 will be a great step forward for the 1.6. -
The demise of YAME is exaggerated.
Hope to be able to report progress in 3-4 weeks -
Happy to learn that Yame is always followed, I use it but it must be recognized that the use with 4.34 is not very simple.
And without the CP60 100% functional it loses its interest.
And in advance thank you to the programmer at Yame for the work he provides. -
Hi, in 4.34 the CPD dont show the waypoints and the flightpath in the moving map. How to setup the CPD in Yame for 4.34? It works in 4.33…
Thx
-
Has anyone had instances of extremely high memory usage with YAME/4.34? I’m currently getting 3-5 mins in the pit with YAME64/Helios running before my system memory (16GB) is fully used and performance is sub 20fps. YAME peaks at 2.5GB+ usage but generally settles around 600-800mb for me, whereas a friend using the same YAMME/Helios setup has usage around 90mb. BMS memory usage increases to 2-3 times normal usage while YAME is running. Any ideas?
-
Has anyone had instances of extremely high memory usage with YAME/4.34? I’m currently getting 3-5 mins in the pit with YAME64/Helios running before my system memory (16GB) is fully used and performance is sub 20fps. YAME peaks at 2.5GB+ usage but generally settles around 600-800mb for me, whereas a friend using the same YAMME/Helios setup has usage around 90mb. BMS memory usage increases to 2-3 times normal usage while YAME is running. Any ideas?
Are you using the Direct3D Hook or RTT shared memory ?
If the latter, try setting everything up for the D3D Hook -
Are you using the Direct3D Hook or RTT shared memory ?
If the latter, try setting everything up for the D3D Hook3D hook doesn’t work with 4.34 (yet)
-