MFD Display Extraction - Any tips?
-
latest version link ?
-
-
If you are on Nvidia you may have a little fps penalty using the in sim extractor. I recommend YAME too. If fps is not an issue then use the sim extractor.
I’m running it on a geforce gtx860… not sure if the fpms will impair me hard with 3 displays…
-
I’m running it on a geforce gtx860… not sure if the fpms will impair me hard with 3 displays…
I use an old 20 LCD positioned below my main 32" and extract to that.
There is usually no FPS penalty for the extra monitor, but the display extraction will cost between 5-10% in FPS.
MFDE is less costly then BMS extraction. But BMS extractor is good to start with as its already there.
Yame is the newer kid on the block, but I have not tried it yet.
Good hunting……
-
I would say MFDE and YAME cost the same in terms of FPS…. at least on an nVidia GPU system.
-
Between YAME and MFDE does one work better with NVIDIA and one better with AMD, or is it a toss?
-
You can see/read my results in my FPS Testing thread, although I need to transfer the actual screenshots due to the Photobucket snafu.
Here’s the summary:
With this info, the choice of MFDE vs. YAME basically boils down to performance and aesthetics. While MFDE averages 2fps more, YAME seems to run as smooth as MFDE and has the advantage of the DED being exactly as shown in the cockpit as opposed to the different “font” used in MFDE. I do prefer the look of the gauges in MFDE, but maybe that’s partially because I’ve used them for quite a while. YAME’s gauges doesn’t really look out of place, but I hope there’s an option to tweak the look later on (I think there is, but I’ll need to learn how to do this). I also like the ability to specify gauge sizes to-the-pixel, adjust gauge position to-the-pixel, and the ability to save gauge layout in YAME. I look forward to roccio implementing feature requests into YAME so in the end, that may be the better program to work with.
You’ll have to find someone with an AMD system for that side of the story though
-
I guess I can add that what you use also depends on how you’re doing things - I have Pegasus’ landing gear box, RWR, EHSI, AOA, VVI, DED, and PFD which contain their own fonts and are USB devices of their own…so the font issue solution YAME provides isn’t a factor for me, and may not be for others whom are building such. I only extract MFDs and the HUD and use MFDE…currently.
But if your setup has you doing everything on LCD panels and putting multiple displays on a panel then YAME is certainly more “current” and versatile. If I ever decide to do a CPD (I have an LCD panel for one) then I’ll probably have to switch to YAME.
-
True! Like I said, if you already use MFDE and are happy with it, then no reason to move to YAME…. especially in your case where all you want is HUD and MFD extraction. I use YAME for much more… and there are even plans to make it work ala-Helios so that’ll be interesting as Helios has been abandonware for… 3 years now?
The main reason I shifted to YAME was that sometimes, MFDE would be confused and would move ALL my gauges and MFDs to one of my display screens. Having to drag all those gauges back to exact placement was a pain! One of the things I immediately requested to roccio was to be able to input gauge sizes and placement… this way, if I only wanted a 1-pixel size change or a 1-pixel adjustment in location, I could do so. With YAME’s window approach to gauge placement, this is so much more easier now.
-
I managed to test run it now… my FPS dropped from 45 to 24 average with the BMS display extraction tool. It’s still “ok” to play if necessary but I think i rather give YAME a go.
-
Check out this post for some hard numbers on extraction performance. Simply put, my 5760x1080 setup went from 50fps to 37fps using CDE, but only went from 50fps to 49fps using MFDE or 46-48fps using YAME.
-
I managed to get YAME going. FPS are at about 35-40 which is ok.
I used the 3D hook mode (that’s the one to save FPS right?).
The displays seem a little laggy though.Can I do any fine tuning?
-
Try WITHOUT the hook mode.
-
I managed to get YAME going. FPS are at about 35-40 which is ok.
I used the 3D hook mode (that’s the one to save FPS right?).
The displays seem a little laggy though.Can I do any fine tuning?
make sure that the you use the 3D hook mode, you have also set RTTextraction to 0 in your config file, otherwise the possible FPS gain is void.
-
Try WITHOUT the hook mode.
will do!
I experienced a couple major FPS lags in an otherwise smooth mission using YAME. It ended with a CTD and a Windows 10 message: Application has been blocked from accessing graphics hardware falconbms.exe
I keep troubleshooting…