MFD Extractor in 4.35.2 makes some guages flicker

[Lurch16]

Hello folks,
After installing the 4.35.2 update, my MFD Extractor makes some of the guages flicker constantly, rendering them useless. It does the same thing whether I use the newer version or the older version The RTT works great on the MFD’s though. Anybody know what might cause this?

[Lurch16]

Looks like nobody has a solution for this one.

[airtex2019]

Haven’t heard of anything like this … but I don’t have a lot of exp with MFDE so I’m little help.

But I think it might help to explain more … what is flickering – the actual 3D cockpit gauges, or the MFDE overlays?

What graphics mode are you running in… refresh rate? g-sync? etc. And what are your system specs (CPU, GPU, OS version, etc)

[malpaso]

@Lurch16:

Hello folks,
After installing the 4.35.2 update, my MFD Extractor makes some of the guages flicker constantly, rendering them useless. It does the same thing whether I use the newer version or the older version The RTT works great on the MFD’s though. Anybody know what might cause this?

Who can help you is oakdesign!

[Lurch16]

Ok, so here are the guages that are having a problem, which i described as flickering back and forth, for lack of better way to describe it. These are not the guages in the pit, rather the ones
displayed on a separate monitor. If they have a needle it twitches up and down or back and forth. Digital numbers flash off and on.

HSI
Att Indicator
VVI
Airspeed Indicator
Altimeter
Ball Compass
Fuel Guage
Fuel Flow Indicator
RWR (flashes off and on)

I run an Asus motherboard with I7 Pentium, 8 gigs RAM Nvidia 1050 with 3 different monitors going through Display Port Hub. The Monitor with the guages is an older HP LCD with 60 hz. Win-7, 64 bit. Direct X 11. Have had it for years and everything worked fine until the 4.35 update. That’s all i can think of for now.

[Stryker]

In the past (some years ago) there occured some problems with nvidea-driver when extracting gauges or MFDs.
Solution in these days had been to use older version of the nvidea-driver, not the newest ones.
Sometimes it worked, sometimes the flickering still occured.

Maybe worth a try to roll back to an older driver-version.

[airtex2019]

@Lurch16:

everything worked fine until the 4.35 update. That’s all i can think of for now.

Are you running the “latest” MFDE? (I don’t know what “latest” is … hard to follow the whole ecosystem of tools … not sure which are being maintained, by whom, and where.)

In this thread, OakDesign offers a fresh build for 4.35 compat (actually sounds like it may need U1 or later):
https://www.benchmarksims.org/forum/showthread.php?41644-MFD-Extractor-not-working&p=568457&viewfull=1#post568457

HTH

[oakdesign]

@Lurch16:

Ok, so here are the guages that are having a problem, which i described as flickering back and forth, for lack of better way to describe it. These are not the guages in the pit, rather the ones
displayed on a separate monitor. If they have a needle it twitches up and down or back and forth. Digital numbers flash off and on.

HSI
Att Indicator
VVI
Airspeed Indicator
Altimeter
Ball Compass
Fuel Guage
Fuel Flow Indicator
RWR (flashes off and on)

I run an Asus motherboard with I7 Pentium, 8 gigs RAM Nvidia 1050 with 3 different monitors going through Display Port Hub. The Monitor with the guages is an older HP LCD with 60 hz. Win-7, 64 bit. Direct X 11. Have had it for years and everything worked fine until the 4.35 update. That’s all i can think of for now.

So Reading you system spec and the description of the flickering not beeing a graphical flicker but more a data loss. Next I assume your CPU is a Core i7 as ther is no I7 Pentium.

First can you check C:\Users_yourusername_\AppData\Local\MFDExtractor\MFDExtractor.exe_Url__hashvalue_\0.6.3.0 which should contain 2 files
log.txt
user.config
and provide the log.txt to be able to check if errors might be logged

to check the DataStrem from BMS you might start Falcon BMS 4.35\Tools\SharedMem\BMSFlighData.exe and start BMS and go into 3d world. Use the FDVars tab. The values there should be constantly be updated. If those numbers make large jumps that might indicate an issue with BMS writing to the memory or tools reading from the memory the tools uses basically the same code to read from memory as MFDE does. If the datastream seams fluid to BMSFlightData.exe than it’s more likely to investigate MFDE processing the data

Haven’t heard of the issue you described before so hard to give a remote analysis or have a solution on hand

[Lurch16]

Ok, so I was running what I think was the older version of MFDE. When that didn’t work I downloaded the “newer” version and ran it. That didn’t work either. I’ll get the other information later today.

[Lurch16]

The log files exceed the Forums size requirements. I can email them if you like.

[oakdesign]

@Lurch16:

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

[Lurch16]

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.

https://file.io/BTJPIHlXHew2

[oakdesign]

@Lurch16:

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.

https://file.io/BTJPIHlXHew2

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)

[Lurch16]

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: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

[airtex2019]

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

[oakdesign]

Yes you Need at least .NET 4.7.2 4.8 will so as well

Gesendet von meinem SM-G930F mit Tapatalk

[Lurch16]

Looks like i already have Net 4.8. Tried going back to previous restore points and MFDE still stops working.

[Lurch16]

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.

[Lurch16]

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.

[Lurch16]

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.