Falcon MFD Extractor v0.6.3.0 rpm guage
-
I have been trying to find a solution to this problem since BMS 4.34. When I extract the RPM guage the guage extracted is different then the one in the 3D pit. It goes to 110% while the one in the pit goes to just 100%. Searching the forum and internet along with the technical manual for Falcon has not helped me. Either not looking in the right place or not using the proper search terms. Can anyone point me in the right direction to help fix this problem. I am running win 10 with a asus nvidia 1070 grachics cards. extracting to just a plain lcd monitor. MFD’s, fuel guages, compass all work fine.
-
The BMS Tech manual won’t help you - this is after a 3rd party software you are looking for help with. Red Dog is good, but not so good as he could write manuals for everything available!
The RPM gauge - as best as I can recall - is not optional in MFDE. There is only the one available, and the choice to offer 110 percent only is a “catch all” and you’ll just have to put up with it I fear.
-
There are 2 main types of engines in F-16’s, and modeled in BMS. Some have 110%RPM gauges and others have 100% RPM gauges.
IIRC, but it’s been a while, at starting MFDExtractor for the first time, or adding the RPM gauge for the first time, it asks if it should be the 110 or 100 % one.
Try deleting your settings/config file of MFDE and try again. -
As MFDE is open source, I’ll have a look into it. The Tachometer class is not that complicated most work is to make a 100% background.bmp adjust the calculation of needle rotation. Just haven’t had a look where to determine which one to use.
-
I will try deleting that file but I have checked multiple times for a setting to choose which one and can not find a setting to choose which one. There is a choice for needle style between c and d models and have tried that but had no effect. Thanks for your help.
-
Version 0.6.3.0 at least the lastest code base only has the 110% version
Edit: so as RPM is Engine related so I looked on the most obvious. GE vs PW Engine
-
So I made a PW Engine Fuelgauge within MFDEs with 100% max RPM. I’m still thinking of how to switch it. My first thought was to make it dynamic by reading either the F16 Block that is currently used or the vehicleACD from the shared memory but I’m still looking then where to get the Engine Type that is associated with that block. Another option which I think I might go for is to put an option into the the MFDE Configuration options UI and let the user select which one to use
-
That is awesome Oakdesign. If I new what you were talking about I would gladly help. Not a programmer though trying to learn. Thank you for the help.
-
Hello pilots.
I would like to ask you a question as this thread is hot and you have experience working with the extractor MFD.
At the moment we have version 4.35 and we have enabled the latest version of MFD Extractor 0.6.3. All analog instruments work, rpm indicator, altimeter, speedometer. But the MFDs only show a bit of the HUD information, as I show you in the photo below.
You know that it could be what is happening.
Greetings from the Caribbean.
-
Yes you are using the 0.6.3.0 version which has been compiled before the latest code changes. In order to fix the issue add
set g_bDoubleRTTResolution 1
to your Falcon BMS 4.35/User/config/falcon bms.cfg file.
Even so 4.35 itself doesn’t use that parameter it forces your MFDE version to set the MFDE Resolution to 1200x1200 instead of 600x600 because of the missing parameter.I’m not the original Dev of MFDE but with the changes of the RPM gauge I will provide a 0.6.3.1 version based on the latest code base which doesn’t need the double resolution fix for 4.35 anymore
-
Yes you are using the 0.6.3.0 version which has been compiled before the latest code changes. In order to fix the issue add
set g_bDoubleRTTResolution 1
to your Falcon BMS 4.35/User/config/falcon bms.cfg file.
Even so 4.35 itself doesn’t use that parameter it forces your MFDE version to set the MFDE Resolution to 1200x1200 instead of 600x600 because of the missing parameter.I’m not the original Dev of MFDE but with the changes of the RPM gauge I will provide a 0.6.3.1 version based on the latest code base which doesn’t need the double resolution fix for 4.35 anymore
When I grow up I want to be like you. :bowd:
Greetings from the caribbe.
-
I visited the Github page, but it was unclear if MFD Extractor can show gauges on an Android tablet? And if so, what to install on the Android device ?
Thx,
JB -
No, not natively as MFDE is a Windows only application.
What works to show MFDE on an Android tablet, if you use software like DuetDisplay, SpaceDesk, IDisplay which connects your Tablet as a monitor over USB or WiFi to your PC. -
Thanks, I will look into those tablet-as-monitor softwares
-
Left is a 15" touchscreen with Helios and MFDE gauges, right an IPAD mini connected with Duet Display and additional MFDE gauges.
I’m using DuetDisplay as it works for both Android and Apple Devices.Even so the image shows connected an IPad tested with my Samsung Tablets as well.
On my Machine it’s running at 60FPS for the tablet refresh rate but for gauges setting the display app to 30 FPS is still sufficient for the use with gauges
Gesendet von meinem SM-G930F mit Tapatalk
-
Appreciate the details oak, nice setup you got there.
-
Alright, so I got MFD Extractor up and running with a tablet as 3rd monitor. I went with SpaceDesk as monitor extension software.
In the Networking tab, I have selected Standalone. And in Performance-BMS Advanced Options, I ticked the “Enable exporting of 3D …”.
The MFDs render real-time, but I do not have the frame around the MFDs with the OSB buttons. And I can’t seem to find an option for that, like you have on your touchscreen. Any advice is much appreciated …
-
MFDE is an extraction only Tool. So in my setup I use MFDE for the Gauges and MFD/DED images. All input parts are build with Helios Software.
If you want t go for MFD Extraction with Bezels and input you might be better off wth an Android Extraction app. Such as the just newly Released App by kugfoo -
ah, so MFDE is the graphics only. I see, I will look into kungfoo’s app and also try and understand Helios. Thank you very much for the clarifications
-
Yes you are using the 0.6.3.0 version which has been compiled before the latest code changes. In order to fix the issue add
set g_bDoubleRTTResolution 1
to your Falcon BMS 4.35/User/config/falcon bms.cfg file.
Even so 4.35 itself doesn’t use that parameter it forces your MFDE version to set the MFDE Resolution to 1200x1200 instead of 600x600 because of the missing parameter.Oak bro…you’vd made my day…thanks :hail:
I’m not the original Dev of MFDE but with the changes of the RPM gauge I will provide a 0.6.3.1 version based on the latest code base which doesn’t need the double resolution fix for 4.35 anymore
and this is the second perfect news on this year :hail: