Solved MFD extractor does not seem to work anymore. Any other ideas?
-
Looks like Lightenings MFD extractor does not work with 4.35 U3. Is there any other options? I see RTT is an option but I have no idea how to use it correctly. Would really like to get my MFD’s to work on my touchscreen.
-
@icarus with the version I linked above none of those cfg setting you have to take care about as it’s all done by MFDE itself
- if checked will set the set g_bExportRTTTextures to 1 or if you have a MFD as one of the gauges MFDE will check if the setting is 1 and if 0 or not present will add/change it in the cfg
- will set the value for set g_nRTTExportBatchSize
As said with the latest souce code version set g_bDoubleRTTResolution is not needed at all as MFDE will read the true image size directly from the memory
-
Works fine for me. Must be something other than BMS that is causeing it. What are the settings in your falconbms.cfg?
-
Same here MFDE works with 4.35.3 but I’m not using the Release version from github but build it from the source code which has some improvements that are not in the prebuild release version.
You can try my build version.It’s basically a portable version so dosn’t have an installer. Just unzip and run the MFDExtractor.exe. No need to uninstall your already installed version of MFDE.
https://drive.google.com/file/d/177VhX_kTKOSL9vjobD7fzHGk2GupigrP/view?usp=sharing
Other than that what is the behaviour, cause does not work is not a very helpful description.
Can you chekc and provide your MFDE log which might include error messages to anylyze what is failing. which can be found in
C:\Users\username\AppData\Local\MFDExtractor\MFDExtractor.exe_Url_hashstring\0.6.3.0\log.txt
Other than that RTT you find in your Falcon BMS 4.35\Tools\RTTRemote\RTTClient64.exe
But unlike MFDE where you can activate and place the MDE’s in UI and Drag and Drop in place with RTTClient you have to activate and place them by editing the RTTClient.ini fileTo make placement with RTT a bit easier there is an external tool to do so
https://forum.falcon-bms.com/topic/19489/f4-bms-4-35-and-display-extraction-with-rttconfig -
I use the RTT Client to extract my MFDs only and us MFDE to extract everything else. After 4.35 MFDE would not display my MFDs correctly. This was the easiest fix for me and RTT seems to give a slightly better resolution for the MFDs than MFDE did.
I found this tool on the forum for RTT client and it sure made setup very easy once you figure out how to use left and right mouse click drag and place and sizing of windows.
https://forum.falcon-bms.com/topic/19489/f4-bms-4-35-and-display-extraction-with-rttconfig
-
@cantoo The issue with MFDE not displaying the MFD not correctly is that with 4.35 the RTTDoubleResolution cfg parameter has been removed from the cfg as BMS now export the image containging MFD , DED,RWR,HUD fixed as 1024x1024 image to the memory (in 4.34 it could be either 512x512 or 1024x1024) and be set with the cfg parameter.
The MFDE Version 0.6.3.0 that is available as release from github still relies on that parameter to be present in the cfg file even if it’s not used by BMS anymore.A build from the most recent source code as the one I provided above doesn’t rely on that parameter anymore as it has som e significant changes in the code how to read the BMSTexture for MFD,DED,RWR,HUD from the memory
-
I think he does not have double resolution setting in his cfg file. I need that for my mfds to work. U3 makes cfg file changes.
set g_bExportRTTTextures 1 // This enables the shared texture memory area for HUD/MFDs/HMS/RWR/DED/PFL
set g_nRTTExportBatchSize 2 // This determines how often the shared texture memory area (if it is enabled) will be updated (every Nth frame, default/min is 2)
set g_bDoubleRTTResolution 1 // Doubles the resolution of the cockpit displays (MFDs, HUD, HMS, RWR, DED, PFL), internal and externalI will startusing your version oakdesign.
-
@icarus with the version I linked above none of those cfg setting you have to take care about as it’s all done by MFDE itself
- if checked will set the set g_bExportRTTTextures to 1 or if you have a MFD as one of the gauges MFDE will check if the setting is 1 and if 0 or not present will add/change it in the cfg
- will set the value for set g_nRTTExportBatchSize
As said with the latest souce code version set g_bDoubleRTTResolution is not needed at all as MFDE will read the true image size directly from the memory
-
@oakdesign Yes thanks. That is why I will switch to yours
-
thanks guys everything is working now
-