Huge thanks to the BMS team, Red Dog (for the awesome manuals) and all involved in bringing 4.33 to realisation.
Can’t wait to get stuck into it!
- Hyp3rion
Huge thanks to the BMS team, Red Dog (for the awesome manuals) and all involved in bringing 4.33 to realisation.
Can’t wait to get stuck into it!
Ah ok, sorry Shadow but it was lost on me as I couldn’t tell from reading your response if you seriously thought I had somehow insinuated some gay vibe…
I did however pick up on your other humour
Hi Hyp3rion ……
Sorry about the vague age requirements , but no we aren’t a gay squad looking for young boys, not there’s anything wrong with being gay, just we aren’t.
Heaven forbid but we have even had female members at times. And I personally even married one once, I know silly thing to do. (no she wasn’t a squad member)Any way back to topic. We have had young members in the past who were committed and valuable members so I thought it reasonable not to exclude those under the age of 18, passion for flight siming respects no age boundary.
Shadow …father of 3 boys the youngest of which is your age.
PS: Arty I will delete this post tomorrow as not to clutter this thread.
Hi Shadow,
Rebel had already sorted me out but thanks for replying nonetheless.
I don’t know where the gay comments are coming from though? The way the “16yo” requirement was listed, it simply read as if you only accepted 16 year old applicants and so I thought maybe you were just a group of young people that didn’t want oldies or young kids cramping your style. I also thought it could have just meant 16 years old minimum and is why I posted my query to confirm. I would advise editing your 801st TFW post so it reads “16yo minimum” or something similar that removes the ambiguity for any other potential recruits
I am glad to hear it’s an open minded group, I happened to marry a female once as well…it must be catching, watch out all you bachelors!
Hi Shadow,
Could you please expand on the “16 y.o” requirement as I meet the others but don’t quite understand this one…16yo minimum? I’m 30, turning 31…does this disqualify me?
I was checking your site out yesterday and thinking of applying to join soon but seeing this, I am wondering if I am allowed to LOL
@Morphine - Been using your profile for a couple of months now and I can say that it works great! The only qualm I have is the shift and zero trackIR mappings need to be swapped (as it can be quite hard to hold in the pinky button while operating other controls with the same hand whereas the paddle is so much easier to hold in) but I can see you already have a linked tip on how to do that, brilliant!
Thanks for creating and sharing it as well as making the print outs (currently stuck to my wall beside the PC )
@Kosmo - Great App! This kind of stuff is really handy to have to hand whenever and wherever you need it!
…although I had some issues after initially getting it to work. Everything was working except for the values along the very top bar like fuel flow but after being in and out of BMS a few times, the MFDs screens started lagging a fair bit in updating (the left more than the right at first) while the MFD buttons still worked really quick. Eventually the MFD screens stopped working altogether after trying to play around with resetting the MFD server and app on the tablet. Funnily enough I got the top bar values working but the MFD screens would only ever show the initial image and never update again for the entire flight, yet all the buttons worked fine…
So, I ended up popping home at lunch and testing it with the android tablet reset to factory settings and version 1.7.1 of the MFD app installed:
This is the first time that everything worked at the same time in the tablet app and I never ran into the MFD display lag / freezing issues I had last night. I believe the freezing may have been resolved by resetting my tablet back to factory and disabling everything bar the essentials to run the Android OS and the MFD app as the tablet itself beforehand was quite inconsistent in it’s performance in it’s use with other apps. So now I’m pretty much relegating it to BMS use only so it will only ever have the MFD app and the Electronic Flightbag installed.
I think getting everything in the app to connect to the server properly needs a fresh instance of the server with a fresh instance of the app which you then click each of the “Start on…” and “Start…” buttons to connect in each of the individual cockpit display extractions before starting BMS (going of my troubleshooting last night and today). I can see in reading the simple instructions for two tablets the “Start on…” buttons are meant to preference which mode the app starts in when opening on each tablet but I couldn’t seem to get the MFDs to work properly until clicking both of these mode buttons today before even getting into BMS.
Please correct me if I am wrong on any of this, it’s just what I’ve found from my experiences so far in using the software. In having trouble with it initially, I have tried as part of my troubleshooting to follow the instructions to the letter but I kept getting different outcomes than what was documented to happen. I think this indicates a review of the official doco could be beneficial to anyone trying to set this up for the first time like myself.
What you were doing initially with the testing is to make sure the server and tablet are communicating. Once you have verified communication, from that point on, you only have to start the Server and Apk and go. Do not go through the testing again.
Ok, that’s the confirmation I was looking for. It’s also what I said in a previous post so I don’t know why you didn’t just confirm what I said then ha ha
No definitely in the MFD server application on the PC, under the testing section. Unless specifying the IP in this area is only for testing the actual connection and that data is transmitting but otherwise the tablet app makes the necessary connection to the PC. Makes sense thinking about it that way since the PC is “serving” and so you only need to point the tablet to the server, not the other way around. The instructions for installing are a little cryptic so it wasn’t exactly clear if this setting was required for use every time (attached particular section in question).
Thanks for clarifying that for me
Komurcu, I think the documentation could use a slight update ;). Step 5 of the single tablet simple instructions (that come after the initial installation instructions) specify to verify the Android IP address is correct which is under the Testing Part area of the MFD Server. If this field is blank each time when starting the MFD Server, the only way to verify this field is to in fact re-enter the tablet’s IP address, even though as confirmed by Dracfalcon this is not necessary.
The only time I would think you’d need to do this is if your tablet IP actually changes because you are using DHCP (and it’s IP lease has expired, therefore your router / switch will assign it a new and most likely different IP address) and not static IP addresses on your local network. Even then, I am thinking that as long as the tablet points correctly to the server IP then it’s still not necessary to set that field unless wanting to actually test the connection from the server end.
I’m an IT tech and so understand how this all works but I can’t know how the MFD server application itself works (since I didn’t code it) without reading the documentation and in this instance I feel it is a little misleading in trying to understand the essential configuration required for the tablet app to communicate with the server application.
Please take this as constructive feedback. For something that someone has created in their own time though as a free enhancement on this great game, it’s without a doubt a brilliant effort
Once it’s set, you are good to go. What version of the Apk are you using…since you talk about the freeze? Version 1.7.0 to me is a better one to use if you are using one tablet.
See this is what I don’t get - if you have to initially set the “Android IP” field under the “Testing Part” settings to be good to go, when I next open the MFD server and find this field blank would I not need to then set it again?
Running version 1.7.0, will be testing with 1.7.1 tonight.
Hi Dracfalcon,
I think you are misunderstanding my original post. I did and still can get the app to connect to the MFD server and was just asking out of curiosity in a completely separate sense about the Android IP field needing to be set each time when trying to troubleshoot the issues I detailed below:
Everything was working except for the values along the very top bar like fuel flow but after being in and out of BMS a few times, the MFDs screens started lagging a fair bit in updating (the left more than the right at first) while the MFD buttons still worked really quick. Eventually the MFD screens stopped working altogether after trying to play around with resetting the MFD server and app on the tablet. Funnily enough I got the top bar values working but the MFD screens would only ever show the initial image and never update again for the entire flight, yet all the buttons worked fine.
The official documentation seems to indicate the need to set it each time (Step5. Verify “Tablet/Android IP address” is correct), though from what you are saying you in fact do not need to do this. I’ll play with it when I get home tonight (which will be in another 6 hours as I am in Australia) and let you know.
Cheers for all the help