New free MFD/ICP app to control Falcon BMS from touch devices
-
To the people having problems with some buttons not working: you need to use bms full.key file or copy the keyboard key binds from it to your keyfile. The reason is, that the server app does not (currently) act as dx device and thus can only call keyboard callbacks.
As you already reading shared mem with your server side app. With 4.35 there is a new datastructure Stringarea wich included which key file is used by the running BMS instance so maybe an idea to check against either by filename or as other apps do by checking if the required callbacks are present and bound
-
@oak: I am already using that to read the keyfile. The thing that I still need to do is check that all the required callbacks are present and bound and otherwise yield a big helpful error message that tells people what is going on. I will make sure to add this to the next version of the server app.
-
Hey everyone: I published a new release of the server app: https://github.com/kungfoo/falcon-bms-control/releases/tag/0.3
If you face any problems with buttons not working, make sure to use this release, as it logs a pretty aggressive message every time a button is pressed and no callback is found for it in the key file, so you know whatâs going on.
-
Thanks KungfooâŚyour server works well with your app. I use it alongside komercuâs. I use yours for the ICP, and his for the MFDs. Yours is more responsive and I like the sound when I push the buttons to confirm the keystrokes are imputed. Great work and I really appreciate it.
-
@Trini: Good to hear. I supposed the MFD exports also have less delay, but I might be wrong. Using the newest version, you can also have haptic feedback (vibration) when you press buttons. Depends on whether the hardware device (tablet or phone) has support for it, though.
-
And another new release: https://github.com/kungfoo/falcon-bms-control/releases/tag/0.4
This release helps people with keyboard layouts with shifted layers, like AZERTY, since BMS uses not the key names, but the actual key codes, when handling keypresses.
-
4.35 is the version I am using. Also the hud video freezes after sometime. I have this set in the falcon cfg. set g_bExportRTTTextures 1 I will have to add this (set g_bDoubleRTTResolution 1)
turn the exporter off for now. That is what is causing the freeze.
-
Yes, I can make an apk available for download. Iâll build and upload it as soon as I get to it.
hey kungfoo, not to be a pain, just wanted to check in on the apk ?
-
@jayb: will get to it soon, was busy with my kids and debugging issues with keyboard layoutsâŚ
-
Take your time, what you are providing here is so great
Cheers,
JB -
@Jayb: I updated the newest release with a signed android APK for devices that do not have access to the play store. https://github.com/kungfoo/falcon-bms-control/releases/tag/0.4
-
Thankyou so much, I will test it tomorrow
Edit: It works really well. Thank you so much for the apk, I was really kicking myself for ordering a Huawei tablet (no wonder it was cheaper than other brands), but now I can put it to good use!
-
Great work @Kungfoo âŚ
Love?? ---- https://love2d.org/wiki/Main_Page
- maybe add one thing to the client (apk,ios) - select network/device ⌠ip address of server input manually
Since I (personally) use usb-tethered network (RNDIS) , on completely other network subnet ⌠donât hog up my wifi with rtt-ex , and faster transfer via usb2 (400mbps) - client auto-config is totally unaware of that ⌠so for someone who needs it , so the option is there ? pretty Please ?
- Remote NDIS is commonly on 192.168.42.x network (it varies with versions of windows/linux, ⌠but on Win10 it is) ⌠So , just need to hit the pc server from client âmanuallyâ - not by broadcasting udp âhelloâ
âAAND ⌠select of keyfile manually , eg, with some server config line override ( I have no problem to rename my key-file to FULL , just so we donât have to do it in the future)
(personally I like auto-config âfoolproofâ solutions , but in case of trouble it is harder to debug stuff - what went wrong ?? )
â@admin - Maybe put this thread in Input/Touchscreens for better finding ? Anyone?
-
Yep, this is using the love2d engine. I see you took a look at the apk (probably). It took me a while to make this decision to use it, but it is the most hackable thing i could find that would allow it to run on all platforms, which is a huge bonus. It also has zero compile times while working on it. Also when other people want to start working on the client (soon open source) you basically have the easiest development setup ever: you need the love2d binary and a text editor. No dependencies or complex IDEs to set up.
On broadcast discovery: i know there should be a config option for setups where udp broadcast does not work. It will be added, give it 3-4 weeks.
The server (should) take your active keyfile from bms shared memory export, so this should just work. However if your not using the full key file youâll have to make sure the callbacks are there. I think thatâs a minor inconvenience.
-
Ok cool.
Naah, didnât go that far to disassemble the whole thing , I was merely trying to figure out why it donât like my rndis connection. âŚ
Actually , your solution is pretty neat , itâs probably just me where things get complicated - but you may change that udp âhelloâ in the future ⌠as you wouldnât believe how many âhelloâsâ ⌠or âfalconâsâEverything works out of the box⌠didnât have to touch anything. Refresh @60 is hard to get via wifi (thatâs where rndis comes in handy.) , but 30 is smooth enough.
Keys work, and I have different key-combos for mfdâs so I would notice that something is wrong⌠Great.
(but I already renamed key file to default ââŚFULLâ name ⌠so⌠Iâll see if it works when using different key-file in config)âOne more suggestion, everyone puts AA/AG/LIST/etc⌠(ICP) buttons on ICP panel (thatâs there they are) ,⌠but when on MFDâs screen and need to switch QUICKLY from AA-> AG or vice versa , then need to switch from:
MFD -> ICP screen ⌠select AA / AG , ⌠return to MFDâs ⌠etc ⌠get me?
⌠and I know there is no too much screen space on devices ⌠but if itâs possible to âsqueezeâ (copy) just AA and AG buttons to mfdâs section -> it would be a miracle
âŚCOM1/2 ⌠IFF/LIST ⌠donât need on mfd section , since their mode of operation is exactly there on ICP/DED , ⌠hence AA and AG are more âgeneralâ modes
SOâŚOR ⌠why donât put everything into one screen ?? These are all screenshots from my 10.1"@1920x1200 ⌠so all icons are copy/paste 1:1
â You have all the time in the world to think about it ⌠also you could name your symbolic price / since it is some handywork/intelectual property ⌠but ⌠thatâs another story// wonât get into.
CHEERS and Thanks for another MFD tool !!
-
I like the layout as it is now, but it would be great with a swipe-action to switch between the two screen layouts. I find myself hunting for the slider control, a swipe would be very nice to have when you need to switch in a hurry.
-
be good if it was a full ICP panel, & radar
-
@jayb: i noticed that too while using it and will likely implement it in the next version.
-
@tj1: i donât think i understand. you mean the rollers on the side of the icp? or which part are you missing? drift cutout switch is currently missing, but will be added
-
Tonight I experienced that the MFD display in the app froze (stopped updating) mid-mission (30 minutes in or so). The OSB buttons still worked, but the displays themselves stopped updating. As I was in single player, I paused and Alt-Tabâed out and restarted the control server, but it did not fix the problem. Is that this RTT-bug that has been reported in BMS, which may be fixed in first upcoming release?