New free MFD/ICP app to control Falcon BMS from touch devices

[MCDeedle]

@kungfoo I’d say about 60% of the time.

[Grimberno]

@MCDeedle I guess I was able to reproduce what you are experiencing (minus the odd bar). I use 2 tablets simultanously, an ancient non-brand one and a Samsung Galaxy Tab, both in a cradle with one above the other. The old one is on the top, displaying RWR and ICP/DED, the lower shows both MFDs, all in landscape. More often than not my MFDs froze but the buttons still worked, I always had to shut down the app and restart to get it running again.

Initially I thought that it relies on the Samsung one because RWR never freezes but was finally able to trace it down to just the MFD-page, no matter which tablet I am using.

Interestingly this always happens when using the F16, I also utilize the Hornet (where the MFDs are not displayed properly) there this never occured. So, it seams that the streamed ‘input’ of the MFDs causes this behaviour, after reducing the quality I can definitly say that the frequency of this freezing is cut down to a bare minimum.

@kungfoo which reminds me, any news on the Hornet-MFD-topic?

[kungfoo]

@Grimberno I will see to it that I can address quite a few of these things today.

• fix the hornet extraction code
• release a new version of the server with the changes for 4.37.6+ (no more busy waiting)
• release new clients with newest base libraries/engine and the new layouts

Let’s see how far I can get.

I feel like the MFDs stopping code has to be the server side sending thread either crashing or giving up on the client due to too many missed packets. I’d wager it’s the second one, since (i hope) a crash of the thread would show up in the logfiles. Maybe you can send me the log file of when the stop happens with the newest server version, since I added some more logging to when it gives up on a client that seems unreachable.

[Grimberno]

@kungfoo firstly, I don’t want to push you but I’m glad. I really have to point out that your tool makes my experience with BMS extremely good…being haptic without major investments is a sweetspot for me (I don’t like VR, so relying on desk-tools is key)

Regarding the log-files, I’ll look into that but I make no promises, I’m on a business-trip momentarily so my capacities for flying are ‘compromised’

[kungfoo]

Does anyone here have the app running on an iOS device with iOS 18.3.X installed? Is auto-discovery working for you? I cannot get it to work with the current dev version and I think Apple broke UDP broadcast (again)…

[Grimberno]

@kungfoo Sorry, Android only…and regarding the logfile for freezing, it’s like at the dentists. No more freezing since

[Dracfalcon]

@kungfoo Just to make sure, you have “not” released an update to this App yet. Is that correct? I’m hoping the “screen freeze…buttons working” may be resolved in the update.

Thanks

[kungfoo]

@Dracfalcon Nope, I am currently working on upgrading all the server libraries and then also the client base libs.

And I’m wondering, why the extraction display on the tablet is laggy af in 4.37, because it sure hasn’t been that way and my PC sure is fast enough to handle it easily…

[Grimberno]

@kungfoo: funfact which I remember just now…I think there was a correlation between the possibility for freezing and speeding up time in 3D. From my totally ignorant POV I would presume that the ‘more dynamic’ the streamed image on the MFDs is, the more likely is a freezing. This also correlates with never experiencing it with the RWR/DED/ICP view…there’s not much going on in dynamic image

If this is just meaningless mumbo-jumbo from my siede, feel free to ignore this. And as mentioned earlier - I am currently not able to reproduce it.

[Nielzs]

I have an issue, and that’s this:

• I start the server app on my desktop
• I start the client Android app on my chrome os tablet
• I start falcon BMS

The server finds the client and vica versa. Is see the mfd’s on the tablet. When I start a flight i see the mfd info streaming on the tablet but none of the mfd buttons work. I can press them on the tablet but they do exactly nothing.

I’ve added the set line in the cfg.
I’ve imported the BMS full key layout.

Am I doing something wrong?

Log entries:

2025-05-09 09:08:32.0899|INFO|FalconBmsUniversalServer|Starting up...
2025-05-09 09:08:32.1569|INFO|FalconBmsUniversalServer|Listening for broadcast packets on: 0.0.0.0:9020
2025-05-09 09:08:32.1910|INFO|FalconBmsUniversalServer|Running on 0.0.0.0:9022
2025-05-09 09:08:39.3097|DEBUG|FalconBmsUniversalServer|Received 12 bytes from 192.168.72.115:55728
2025-05-09 09:08:40.2078|DEBUG|FalconBmsUniversalServer|Received 12 bytes from 192.168.72.115:55728
2025-05-09 09:08:40.4899|INFO|FalconBmsUniversalServer|Peer connected from 192.168.72.115:43051
2025-05-09 09:08:40.5187|DEBUG|FalconBmsUniversalServer|Starting to stream f16/right-mfd to 192.168.72.115:43051
2025-05-09 09:08:40.5307|DEBUG|StreamedTextureThread|"f16/right-mfd": Refresh rate is: 30, Quality is: 90
2025-05-09 09:08:40.5307|DEBUG|FalconBmsUniversalServer|Starting to stream f16/left-mfd to 192.168.72.115:43051
2025-05-09 09:08:40.5307|DEBUG|StreamedTextureThread|"f16/left-mfd": Refresh rate is: 30, Quality is: 90
2025-05-09 09:08:40.5307|DEBUG|FalconBmsUniversalServer|Starting to stream f16/ded to 192.168.72.115:43051
2025-05-09 09:08:40.5307|DEBUG|StreamedTextureThread|"f16/ded": Refresh rate is: 30, Quality is: 90
2025-05-09 09:09:54.7035|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/right-mfd:OSB_7
2025-05-09 09:09:54.7552|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/right-mfd:OSB_7
2025-05-09 09:09:54.7948|DEBUG|CallbackSender|Down SimCBEOSB_7R
2025-05-09 09:09:54.8169|DEBUG|CallbackSender|Released SimCBEOSB_7R
2025-05-09 09:09:54.8339|DEBUG|KeyboardEmulator|KeyboardEmulator: keyboard layout 0xF0010413 detected (not necessarily active)
2025-05-09 09:09:55.6352|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/right-mfd:OSB_7
2025-05-09 09:09:55.6352|DEBUG|CallbackSender|Down SimCBEOSB_7R
2025-05-09 09:09:56.3652|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/right-mfd:OSB_7
2025-05-09 09:09:56.3698|DEBUG|CallbackSender|Released SimCBEOSB_7R
2025-05-09 09:10:02.4985|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/right-mfd:OSB_13
2025-05-09 09:10:02.4985|DEBUG|CallbackSender|Down SimCBEOSB_13R
2025-05-09 09:10:02.5908|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/right-mfd:OSB_13
2025-05-09 09:10:02.5908|DEBUG|CallbackSender|Released SimCBEOSB_13R
2025-05-09 09:10:04.7254|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/right-mfd:OSB_12
2025-05-09 09:10:04.7254|DEBUG|CallbackSender|Down SimCBEOSB_12R
2025-05-09 09:10:04.8522|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/right-mfd:OSB_12
2025-05-09 09:10:04.8562|DEBUG|CallbackSender|Released SimCBEOSB_12R
2025-05-09 09:10:05.4209|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/right-mfd:OSB_11
2025-05-09 09:10:05.4209|DEBUG|CallbackSender|Down SimCBEOSB_11R
2025-05-09 09:10:05.5523|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/right-mfd:OSB_11
2025-05-09 09:10:05.5523|DEBUG|CallbackSender|Released SimCBEOSB_11R

Video: Korea KTO, Instant Action, Fighter Sweep

Update:

Trying to bind keys in BMS launcher Keymapping to keypresses in the client app on my tablet, result in these Logfile entries:

2025-05-09 09:51:51.5100|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:51:51.5100|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:51:52.1018|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:51:52.1048|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:51:58.9352|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:51:58.9352|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:51:58.9352|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:51:58.9352|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:51:59.6860|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:51:59.6860|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:51:59.8104|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:51:59.8104|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:00.3074|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:52:00.3074|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:00.4601|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:52:00.4631|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:03.2749|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:52:03.2749|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:03.4278|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:52:03.4308|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:04.4077|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:52:04.4077|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:04.5079|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:52:04.5129|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:15.3449|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:52:15.3449|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:15.5579|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:52:15.5579|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:16.0795|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:52:16.0795|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:16.3472|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:52:16.3472|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:18.1011|DEBUG|OsbButtonHandler|MFD OSB message received: osb-pressed:f16/left-mfd:OSB_1
2025-05-09 09:52:18.1041|ERROR|CallbackSender|Could not find process named Falcon BMS
2025-05-09 09:52:18.2676|DEBUG|OsbButtonHandler|MFD OSB message received: osb-released:f16/left-mfd:OSB_1
2025-05-09 09:52:18.2676|ERROR|CallbackSender|Could not find process named Falcon BMS

Update:

nevermind, tried it again this evening. put the server app in the falcon BMS tools folder, ran it, started the client app on the tablet, and it works like a charm…NICE!