Lightning's MFDE and 4.33
-
Let’s keep it on-topic please; this is a MFDE thread.
Please discuss YAME in the YAME thread, so ideas, help and support can more easily be found by those needing it.
-
Before YAME I used MFDE and GPT. Believe me YAME is much more user friendly and versatile, once you become familiar with it. The YAME Manual is a pretty thorough guide to setup and a good place to start. Beyond that advice, provide a detailed description of your issues and help should be forthcoming.
That is why I have not moved to YAME yet. MFDE is working perfectly and I need time to figure YAME out and I haven’t had any time lately. It is not as simple as MFDE to setup when you are not familiar with it. I look forward to trying it though.
-
If you are using only MFDE, the performance hit is about the same. The advantages are mostly not having to use CDE and being able to save and share layouts. As a multi-screen user and having used MFDE for years, sometimes the program would go berserk and display my gauges on one of my display screens and not on the touchscreen. I would then have to manually drag each and every gauge and place them juuuuuust right so that they “fit” perfectly under my Helios profile. YAME solves this problem in a few ways, making it easier to move/adjust gauges and you can adjust gauge size and position to-the-pixel. I also used to pair MFDE with CDE as I did not really like the MFDE DED and PFL display, and for some reason, there was a bit of lag on my MFDE MFD images, so I used the CDE for MFDs, DED, and PFL.
For any more questions (ie, advantages, how-to?, etc.), please do go to the YAME thread and I’m sure there’ll be someone happy to help out. Bikeman, to get the RWR image (rings), tick TRANSPARENT BACKGROUND and BACKGROUND IMAGE, then click the IMAGE button and select the appropriate RWR picture. Click APPLY and you should be sorted.
Again, for any more concerns on YAME, head on over to the YAME thread and you should have help in no time!
-
Thanks for the replies,
Sorry I didn’t realize it was going to be a knots & nickers issue. :munch:
-
I run both MFDE and Yame at the same time. Yame for the standbys’ and MFDE for the RWR.The mfds I still extract
from BMS itself.They all work good. -
It is my understanding that both YAME and MFDE render the MFD’s with less FPS impact than the BMS extraction utility. Correct or no?
-
It is my understanding that both YAME and MFDE render the MFD’s with less FPS impact than the BMS extraction utility. Correct or no?
Yes, but how much depends on your graphics card. AMD cards will typically only lose 1-2 fps running BMS extraction, NVIDIA cards will lose much more.
The tradeoff is that using RTT (either using RTTRemote, MFDE or YAME) is slightly more laggy for MFDs compared to using BMS extraction, even if you have ‘Export a new set of images to shared memory’ set to ‘every 1 video frame’ in the config options (recommended). Using external MFD windows in BMS will always be faster than using a 3rd-party extractor like MFDE for that purpose.
Because of the slight lag, AMD owners who like running in windowed mode may still prefer BMS extraction for the MFDs, as cursor control in particular is more responsive. Others may decide that the framerate hit (NVIDIA) or need to run in windowed mode of BMS extraction makes other options preferable.
-
The tradeoff is that using RTT (either using RTTRemote, MFDE or YAME) is slightly more laggy for MFDs compared to using BMS extraction, even if you have ‘Export a new set of images to shared memory’ set to ‘every 1 video frame’ in the config options (recommended). Using external MFD windows in BMS will always be faster than using a 3rd-party extractor like MFDE for that purpose.
Note that Yame also offers a 3DHook extractions which does not require RTT and has a positive impact on FPS on most reported user systems so far
-
Interesting about AMD having different framerate hit than nVidia…
As for using MFDE for the RWR, there is no need to. YAME can display the RWR with image… just follow my instructions above.
-
@Terminator: it works! Tnx for your help
Gesendet von iPhone mit Tapatalk
-
Does any one (Lightening for instance) have plans to make the analog clock in the pit extractable (is that a real word?) using MFDE ?
-
AFAIK, Lightining has stopped working on MFDE sometime ago. He gave the source to anyone that wanted it.
The club cirque and many other goodies are “extractable” with YAME64.
-
Yep, clock is extractable with YAME but I fail to see the point as there is the same info on the DED… unless you’re just looking for stuff to fill up your other screens!
-
You’ve never had your DED go out?
With the analog clock displayed you can be sure if it’s still happy hour when you RTB.
-
You’ve never had your DED go out?
With the analog clock displayed you can be sure if it’s still happy hour when you RTB.
The important things in life are always worth keeping track of.
-
Yep, clock is extractable with YAME but I fail to see the point as there is the same info on the DED…
Then why is it extractable with YAME ???
-
New version available
https://app.assembla.com/spaces/lightningstools/subversion/source/HEAD/releases/End%20User%20Applications/Falcon%20MFD%20Extractor/Version%200.6.2.0compatible with the latest Falcon BMS version and easily configurable
Enjoy!
-
because could be a backup instrument, because if you are using DED for to insert/read some other information could be useful to get time from clock…because it is used from the Pit builder could be intersting to have a similar replica on the screen. As reported in many feature in Falcon it could be also only as an “Eyes candy” if you have it it’s your choice to usse it or not…
-
Then why is it extractable with YAME ???
because there’s a real clock in the real f-16 too.
because then you can read the time when your jet is cold, or when UFC is not available (power issues, battle damage etc) -
Hmmmm another hint with this new version…
Thanx for sharing Varhn.
Anyone had the time to test it and let us know of the goodies of 0.6.2.0?