Falcon MFD Software for android tablets
-
But… wait a minute guys…
YOU ARE talking about MFDE !!! (MFD Extractor) OR (this thread) “Falcon MFD for Android” …???
As I have actually ZERO problems with Komurcu’s Android MFD app - client/server … ZERO!! Everything works as it should, rtt extraction is correct, no freezes, no crashing.
It was working out of the box AFTER I configured directories for 4.35 via that registry workaround I’ve “hacked” for 4.34 … few more pages back…
Komrucu’s “server” side app was originally written for 4.33 so “server” doesn’t know for 4.35 … just that need that little registry hack , literally 1 text line with path to the 4.35 install directory.Other then that , all is GO. - same same.
But if you’re referring to the “MFD Extractor” … may I suggest that you’re in the wrong thread … no support here… I personally don’t use “MFD Extractor” ~10yrs ago , well after my 19" touchscreen broke.
So maybe you should ask your questions in “MFD Extractor” dedicated thread as, hey!, no hard feelings, … just you’ll have more chances for support there …
Cheers
Sorry but I do not understand what are you trying to said.
I’ve been using Komurcu’s sw for a long time with great satisfaction. In 4.34 as well as the previous ones to install Falcon MFDserver you had to use the option “cockpit display extration” from the initial BMS menu.
In the new version, 4.35, that option has been removed and now you have to use RTT. And this is where the problem is as I have tried to explain.
If you are using komurcu sw in 4.35 without any problem, please share how you have configured to avoid the problem, a problem that the BMS Team is trying to solve to get a solution.
Please try to read the “remote-freezing RTT” thread in Thecnical support topic and especially the post number 20
thanks.
-
Alright…
- See there already exists another, older “MFDE” , and this one (Falcon MFD for android tablets) is NOT in any way related to the original one.
So they are NOT the same, and they are named differently, OTOH, in essence they share the same/similar purpose … mfd extraction
Lemme explain then. Are you talking about this software : “MFD Extractor” or short “MFDE” or “MFDEx”
link:
https://www.benchmarksims.org/forum/showthread.php?23359-Lightning-s-MFDE-and-4-33So, if you’re using that old piece of soft, then any questions about support is more likely to be answered in that thread.
OR,
Are you taking about (this thread) “Falcon MFD for android” by Kommurcu . - and have problems with it?
If above case, then I’m curious also, as I repeat, have ZERO defects with it. It was working OOB. - well after that reg micro hack. I didn’t have to add anything in “Falcon BMS.cfg” (old doubleres line)
For reg-hack see this post,… https://www.benchmarksims.org/forum/showthread.php?16247-Falcon-MFD-Software-for-android-tablets&p=532135&viewfull=1#post532135
Only need to do it for 4.35 now … originally was for 4.34 version … but in principle it works the same
…
So, remove that old line from cfg , or just rem it with “//” (no quotes)
Line 129: set g_bDoubleRTTResolution 1 // Doubles the resolution of the cockpit displays (MFDs, HUD, HMS, RWR, DED, PFL), internal and external-then apply reg “hack” , select 4.33 U1 in server (top left) - as we are “emulating” 4.33 U1, find and select your key-file in !4.35! /config dir
-fire it all up
-report?Cheers
- See there already exists another, older “MFDE” , and this one (Falcon MFD for android tablets) is NOT in any way related to the original one.
-
Hey everybody,
I use FalconMFD server on Android 7" for a long time. Suddenly it stoped working with BMS 4,35 or I should say it works (shows both MFD’s form BMS) but the OSB’s don’t work. I’ve selected the correct key stroke file with the correct BMS 4.35 path but still no go.
Any ideas? -
When you run server and then connect with android , you can see in server small debug window, … then try pressing buttons on mfd’s … are the keys registered , anything ?
-
Hi everybody, with the BMS new update it seems everything goes on the right direction.
When I start BMS and I have in my two Lenovo Tablets de ICP and the MFDs The letters of the OSB buttons in 4.35 come out with a too large font, nothing to do with 4.34. Does anyone know how to change the fonts so that it looks similar to 4.34?Thanks in advance
-
I can’t seem to get the program to work with 4.35 or at least totally. I can get the tablet and desktop to communicate but it doesn’t accept all input. It accepts the input from the ECM panel and when if I turn on FCR from the computer it shows up on the tablet but it will not accept any input from the tablet. The debug window shows SimCBEOSB_1L is invalid.
I have check and double checked and everything in the keyfile is correct and using the BMF - FULL keyfile. Is there something I’m missing that it will not accept these keystrokes?
-
EDITED:
Connectivity is good now, to both tablets, but getting intermittent/no screen updates on one, and no screen updates or input on the other. Still debugging.
-
When you run server and then connect with android , you can see in server small debug window, … then try pressing buttons on mfd’s … are the keys registered , anything ?
Fang you appear to have good success with this. Could you please share your keyfile which works with it. (inside code tags in a post would be fine).
Cheers. -
When I Launched FalconMFDServer.exe I got the following message: “Falcon BMS 433U1 version does not exist Please Select Correct version” This Message is not an issue, everything works fine but is a bit anoying.
How can I fix it? I am using the current version: Falcon BMS 435 U1
Thanks in advance
-
You would have to create an registry entry for 4.33 U1 with a basDir node pointing t your 4.35 installation
-
You would have to create an registry entry for 4.33 U1 with a basDir node pointing t your 4.35 installation
Thanks!! but to complex for me
-
I’m confused…. I found two versions in my download folder for the android client (1.6.5 and 2.1.2). As I’m re-installing my a10 tablet (ancient android 4.x) I tried 1.6.5 first which failed (“unable to parse package”) but this version installed fine on my other, newer tablet (galaxy tab something). Then I tried client apk version 2.1.x on the android 4 device and it installed just fine. Weird! I’m wondering where version 2.1.x is coming from? I must be getting old.
All the best,
Uwe
-
@hoover - sorry for necro , i haven;t use this for some time , now i fired it up again it said (server app) “no network detected” … do it died finally.:)
Do you still use this or i can forget about it … windows and whole tonne of stuff got changed in meantime so it could be anything that causes this - even my setup // i just needed a confirmation , and you were the last here. TY
Probably NET4 mismatch …
See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.Exception: No network detected at FalconMFDServer.ServerClass.InitServer(Int32 Port) in F:\YAZILIM CALISMA ALANI\FalconMFDAll\FalconMFDServer\FalconMFDServer\ServerClass.vb:line 26 at FalconMFDServer.frmServer.frmServer_Shown(Object sender, EventArgs e) in F:\YAZILIM CALISMA ALANI\FalconMFDAll\FalconMFDServer\FalconMFDServer\frmServer.vb:line 116 at System.Windows.Forms.Form.OnShown(EventArgs e) at System.Windows.Forms.Form.CallShownEvent() at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) at System.Windows.Forms.Control.InvokeMarshaledCallbacks() ************** Loaded Assemblies ************** mscorlib Assembly Version: 4.0.0.0 Win32 Version: 4.8.4470.0 built by: NET48REL1LAST_C CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll ---------------------------------------- FalconMFDServer Assembly Version: 1.0.0.0 Win32 Version: 1.0.0.0 CodeBase: file:///C:/Users/~!iceman/AppData/Roaming/FalconMFDServer/FalconMFDServer.exe ---------------------------------------- System.Windows.Forms Assembly Version: 4.0.0.0 Win32 Version: 4.8.4488.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 4.0.0.0 Win32 Version: 4.8.4488.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 4.0.0.0 Win32 Version: 4.8.4390.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- Microsoft.VisualBasic Assembly Version: 10.0.0.0 Win32 Version: 14.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System.Core Assembly Version: 4.0.0.0 Win32 Version: 4.8.4470.0 built by: NET48REL1LAST_C CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll ---------------------------------------- F4TexSharedMem Assembly Version: 1.4.0.0 Win32 Version: 1.4.0.0 CodeBase: file:///C:/Users/~!iceman/AppData/Roaming/FalconMFDServer/F4TexSharedMem.DLL ---------------------------------------- System.Configuration Assembly Version: 4.0.0.0 Win32 Version: 4.8.4190.0 built by: NET48REL1LAST_B CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 4.0.0.0 Win32 Version: 4.8.4084.0 built by: NET48REL1 CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box.