Lightning's MFDE and 4.33
-
QNH is working in the version so cool.
-
Nice to see Lightning made MFDE 4.33 compatible already. Nice job, works like a charm here at first install.
As you know, several new pits have been included in 4.33, and some have different RWR systems.
One if the BAF MLU which has Carapace. I noticed not all symbology from Carapace is getting extracted on the RWR screen. Is it a possibility to take that into account on a future update? Maybe getting to chose in the options what type of RWR you want to use and get the according symbology.
Related to that. I have an ATD for my pit. Would be great if I chose the ATD TFT option combined with Carapace, that the labels for the OSB’s are also adjusted. Now it shows the block52 RWR labels, which are not the same.Two other minor requests for future updates.
1/ DED font has changed in BMS. Would be nice to see that in the MFDE DED too.
2/ Some pits, like MLU’s, have red & green tape markers on the engine gauges. Would be nice to be able to select those too in the extraction -
My issue was resolved by deleting 6.1.1 install, downloading and installing 6.1.0 and the rebooting. Works brilliant
This worked well for me, too. Awesome!
-
People who have problems with 0.6.1.1 please post your system details. Let’s see if there’s a common theme here.
0.6.1.1. didn’t work for me, but 0.6.1.0 worked without a problem.
4 monitor config with 4th being for extracts, both MFD’s and the RWR are all that I currently extract. Spec’s in sig.0.6.1.1 wouldn’t let me save settings and the start stop was grayed out because of not being able to apply settings.
-
I got this resolved by installing on the root folder instead of the default location
i think i got this fixed and i want to share my story in the hope it might help a lonely soul
first of all the above is not correct. It looked that way because in fact the options do show up, but after a long time (15-20 min).
0.6.1.0 and 0.6.1.1 versions with both the same result.My setup is windows 7 with win 10 waiting to install. (my feeling is that last point is the issue, but don’t quote me on that…)
long story short: i reverted to a state of windows without any win 10 updates. Reupdated win7 with all the latest updates and installed MFD 0.6.1.1
it works like a charm now.
-
To use 0.6.1.0 with both v4.32 and v4.33, I had to:
- use the v4.32 base directory in the MFDE advanced setting. It wouldn’t work at all for my older v4.32 install unless I did this. However, it works for both 4.33 and 4.32 if you set it this way.
- however, live with the v4.32 MFDs not working.
- use the v4.32’s MFD internal extraction for the left and right MFDs since MFDE wouldn’t work for the MFDs.
This seems to get me ops with 4.33 and keep me running in 4.32.
db
-
I had 0.5.7.0 MFDE MFD’s working in fullscreen mode in 4.32. I cannot do that with 4.33. I must check the display extraction in configuration to get the MFD’s to work. 0.6.1.0 or 0.6.1.1 no luck. Anyone had better luck?
-
I had 0.5.7.0 MFDE MFD’s working in fullscreen mode in 4.32. I cannot do that with 4.33. I must check the display extraction in configuration to get the MFD’s to work. 0.6.1.0 or 0.6.1.1 no luck. Anyone had better luck?
Not needed for me.
Check in MFDE options in a certain tab (not at game pc now, can’t check) and check the box that allows extraction of shared memory or something. -
Yes, during testing I had full screen working with just MFDE (0.6.0.0 iirc but the minor updates since shouldn’t have made any difference).
I’ve gone back to using BMS Extraction for the MFDs, DED and PFL as I want the authentic fonts for the DED and PFL and using external MFD windows in BMS will always be faster than using a 3rd-party extractor like MFDE for that purpose (though the difference is barely perceptible), not to mention I only lose 1-2 fps with an AMD card. As you’re using NVIDIA I can understand why you’d prefer to stay full screen and not have to stomach the bigger framerate hit.
Check you have changed ‘Export a new set of images to shared memory’ to ‘every 1 video frame’ in MFDE Options > Performance > BMS Advanced Options, and of course ‘Enable exporting…’ ticked.
-
Not needed for me.
Check in MFDE options in a certain tab (not at game pc now, can’t check) and check the box that allows extraction of shared memory or something.Yes, during testing I had full screen working with just MFDE (0.6.0.0 iirc but the minor updates since shouldn’t have made any difference).
I’ve gone back to using BMS Extraction for the MFDs, DED and PFL as I want the authentic fonts for the DED and PFL and using external MFD windows in BMS will always be faster than using a 3rd-party extractor like MFDE for that purpose (though the difference is barely perceptible), not to mention I only lose 1-2 fps with an AMD card. As you’re using NVIDIA I can understand why you’d prefer to stay full screen and not have to stomach the bigger framerate hit.
Check you have changed ‘Export a new set of images to shared memory’ to ‘every 1 video frame’ in MFDE Options > Performance > BMS Advanced Options, and of course ‘Enable exporting…’ ticked.
Thanks. Did all these things. Still no MFD’s in fullscreen mode. Any more suggestions? Is there something in the callsign.ini I might have to tweak? I seem to remember something like that back in the day with 4.32.
All the gauges work in fullscreen, just not the MFD’s.
-
Hmm, just went back and checked this in 0.6.1.1 just to be sure and it works fine for me.
What I did:
1. Check in Falcon BMS Config > Hardware > External Displays > Cockpit Displays to External Windows is unticked
2. Set MFDE Options as below (and move MFDs where you want them):
3. Check in falcon bms.cfg (\Falcon BMS 4.33\User\Config) in Misc Settings that:
- set g_bExportRTTTextures 1
- set g_nRTTExportBatchSize 1
That’s it.
I’m not sure what else to suggest.
-
I had all this and it didn’t work. But now it is all of a sudden working now and I have no idea why. Time to clone my hard drive to save my setup. Thanks guys for helping.
Edit. It worked once and stopped working again.
-
Shhh, don’t touch anything, just back it up and fly! :mrgreen:
-
This post is deleted! -
i think i got this fixed and i want to share my story in the hope it might help a lonely soul
first of all the above is not correct. It looked that way because in fact the options do show up, but after a long time (15-20 min).
0.6.1.0 and 0.6.1.1 versions with both the same result.My setup is windows 7 with win 10 waiting to install. (my feeling is that last point is the issue, but don’t quote me on that…)
long story short: i reverted to a state of windows without any win 10 updates. Reupdated win7 with all the latest updates and installed MFD 0.6.1.1
it works like a charm now.
Could you please tell me which version of your framework runs now ?
-
Shhh, don’t touch anything, just back it up and fly! :mrgreen:
I did not touch a thing and it stopped working again.
Can’t even get the MFD’s to extract in standalone.
-
I have a similar problem to Icarus, sometimes the MFD’s work perfectly, most of the time they don’t.
The gauges work every time, using version 0.6.1.0 which works perfectly in BMS 4.32.
It’s like the MFD’s are not getting initialized at the session start up…. very frustrating.
Is it true that they are working on a version of MFDE for 4.33 ?.
Thanks.
-
I have a similar problem to Icarus, sometimes the MFD’s work perfectly, most of the time they don’t.
The gauges work every time, using version 0.6.1.0 which works perfectly in BMS 4.32.
It’s like the MFD’s are not getting initialized at the session start up…. very frustrating.
Is it true that they are working on a version of MFDE for 4.33 ?.
Thanks.
See post #23…This is the only way I got both versions to work reliably. https://www.benchmarksims.org/forum/showthread.php?23359-Lightning-s-MFDE-and-4-33&p=338743&viewfull=1#post338743
-
I cannot even get the MFD’s to work in standalone. All the gagues work fine. Whatever the reason my MFDE server is not allowing MFD extraction seems to be bypassed by BMS config option to extract MFD’s.
-
I got it working in fullscreen! MFDE.exe compatibility set to run as admin and disable visual themes and desktop composition.