MFD Extractor in 4.35.2 makes some guages flicker
-
The log files exceed the Forums size requirements. I can email them if you like.
Upload it to https://www.file.io/ and share the link
-
ok, so I tried cutting the log file in half and it still exceeds download limit of the BMS forum.
Just saw your post Oakdesign. -
ok, so I tried cutting the log file in half and it still exceeds download limit of the BMS forum.
Just saw your post Oakdesign.Ok first analysis. The MFDE Version you use is not build on the latest source code. Your log is filled with with an error message caused by code has been removed from the latest source code.
2021-06-27 00:23:56,377 [SimStatusMonitorThread] ERROR F4Utils.SimSupport.ThreeDeeCockpitFileFinder : C:\Falcon BMS 4.35\data\Terrdata\objects\FALCON4.CT - F4Utils.Campaign - at F4Utils.Campaign.ClassTable.ReadClassTable(String classTableFilePath) in C:\lightningstools\trunk\F4Utils\Campaign\ClassTable.cs:line 14 at F4Utils.SimSupport.ThreeDeeCockpitFileFinder.FindThreeDeeCockpitFile(Int32 vehicleACD) in C:\lightningstools\trunk\F4Utils\SimSupport\ThreeDeeCockpitFileFinder.cs:line 53 - F4Utils.Campaign.F4Structs.Falcon4EntityClassType[] ReadClassTable(System.String) - (null) - ```which occurs multiple times a second and might/can cause the render thread to cause flicker Can you try the MFDE version linked below. No need to uninstall the version you already have. Just unzip and run the MFDEEXtractor.exe from the unzipped folder. Just make sure that you have in the performance tab the path to your BMS installation set. set up the gauges you need and report back if you still have the flicker effect with this version [https://drive.google.com/file/d/177VhX_kTKOSL9vjobD7fzHGk2GupigrP/view?usp=sharing](https://drive.google.com/file/d/177VhX_kTKOSL9vjobD7fzHGk2GupigrP/view?usp=sharing) ![](https://up.picr.de/41782455mq.png)
-
Ok, So I downloaded the verson above, extracted, ran the MFD Extractor a a Pop-Up says Falcon MFD Extractor has stopped working, with details below
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: MFDExtractor.exe
Problem Signature 02: 0.6.3.0
Problem Signature 03: 5eac2463
Problem Signature 04: MFDExtractor
Problem Signature 05: 0.6.3.0
Problem Signature 06: 5eac2463
Problem Signature 07: 103
Problem Signature 08: 8
Problem Signature 09: System.DllNotFoundException
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt -
No idea if this is the problem but it may need a newer version of .NET Framework runtime?
v4.8 is the latest, and I believe it’s still supported on Win7…
https://dotnet.microsoft.com/download/dotnet-framework/net48 -
Yes you Need at least .NET 4.7.2 4.8 will so as well
Gesendet von meinem SM-G930F mit Tapatalk
-
Looks like i already have Net 4.8. Tried going back to previous restore points and MFDE still stops working.
-
Well, at this point I’m thinking this is un-fixable and I’ll try to find another program/tool that will export guages. Thanks for checking it out guys.
-
Ok, just an update.
I uninstalled the new MFDE and went back to a version with an installer from 2012 and it at least brings back all of my guages, including the ones that flicker. So, i will cut the bad guages out and use helios to replace them. So that will be my solution for this. Supposedly it is possible. BTW my video driver was 3 years old but that had no effect. I’ll report back when everything is set up. -
Ok, so I installed Helios, copied a few guages from Ice’s profile to replace the bad ones in MFDE and they work fine. The only problem I ran in to was some of the guages have a bezel or border around them and can’t be resized. Otherwise, success. Never could get some of those MFDE guages to work right but at least this was a work around.