MFD Display Extraction - Any tips?
-
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…