IFlyBMS
-
Ice.
I might like to make an improved version, with more panels and switches. Maybe by downsizing some of them.
I have two questions for you.
What font are you using for the panel writings.
How hard is it to create a new buttons/switch ? Could you quickly explain ? I plan on using the same switches graphics you have already created. I just don’t really know how to create a new switch, with it’s own input and it’s active area.
Thanks a lot
-
It’s easy enough once you get to it to be honest. The hardest part is getting them all to fit.
Tell you what… if you can figure out the actual real-estate size of the horizontal layout on the iPad, and using Photoshop or some such program, draw me a layout of what you want and where and how it all fits together. If I only need to “assemble” this and not “figure out” which goes where, I can do it on a weekend or so. It was the grouping, arranging, and “fitting” of the switches and buttons that took the most time for me.
Send me a PM or email (better!) and I’ll get it sorted.
-
well, this is what i am working on ICE…
i still have to think about what important toggle switches or rotaries I can implement in the top left panel though
Im struggling on how to create a new switch, and I would appreciate some help. just give me a few clues, and I should work this out. By what am I to start ?
I noticed that for each toggle switch, there is a label (starting position, to witch i can affect an image from the toggles section) and then 2 or 3 positions (AHK) and then a GP…
I just dont know by what to start…
My idea was to simply duplicate an existing toggle (such as the one used for the autopilot) and then modify the inputs it sends, but I am unable to do this.
can you help me ?
-
Ok… i know understand how to create all this thinks (AHK, LABEL, GP) and how to assign gestures to each of them… What I would like to understand is how i can visually make them appear on the layout !!! I know how to change the image of an existing one, but not how to make a new created one visually appear !!!
thanks !!!
-
damn, just dragging it on the screen !!!
Im starting with the speed type (CAS TAS, GND SPD) toggle, as it should work exactly as your Autopilot Left toggle… so basically i am copying what there is there.
ETA:
ok, now I managed to drag the speedtype label AND the GP on the layout… I can see them, and they work on my IPAD… (they send the input)… but problem, they dont update their visual position. I litteraly copied the “set data” from your APLef toggle, and mine is Speedtype toggle… So i have:
SpeedType (label)
SpeedType (GP)
SpeedTypeDown (AHK<)
SpeedTypeMid (AHK<)
SpeedTypeUp (AHK<)Each of the label and AHK has its corresponding toggle image too
What am i to do with the 3 AHK I created for my speedtype ? Do i have to drag them on the layout too ???
-
damn… my mid and down inputs work (sending imputs, but no visual position update on the IPAD either), but the "u"p keeps giving me a timeout, and this message error…
its more complicated than i thought…
-
Lol, you lost me there Shung. But yes, there’s more there than just copying the switches over
-
Lol, you lost me there Shung. But yes, there’s more there than just copying the switches over
no problem. its working now. Didnt know why it was giving me this error. Anyway, switches were not working because I once dragged all 5 things instead of just the LABEL and GP
I have added 5 toggleswitches yet (FLCS NORM/OVRD , Altimeter type, Hud brightness mode and Test step)
I think I will add one more line on top right.
Its easy once you understand how it works, but it takes some time.
I am admirative for all you have done !
-
Hello Shung,
Would this become available for public use later on?
@Ice,
Is this something you would consider for Helios? -
this is what it looks like so far !
I think im gonna split the CRS HDG QNH and HCMS in a line instead of a column, so that I can add another row of 4 switches above the 4 I just created.
Im using ARIAL as a font, which is close to yours, but not exactly. If you can tell me what font you are using, im gonna fix it.
Also, I am thinking of making the Master Arm, laser etc panel half that size, so i can add another pannel there.
Maybe you can give me an information… If i downsize the LABEL button, will it automatically downsize the corresponding feedback image called ? lets say the label shows the toggle at the mid position… if i downsize this one, when i switch the toggle up, and the up toggle appears, will it be automatically downsized to the size of the label ?
-
this is where I am at now… Ill finish thise toggle switches tonight, and then go to bed
-
Ok, I am done for tonight. here is where we are at ! Im quite happy with it !
Does anyone knows where to find the keystrokes for the last switch of the first line of the HUD pannel ? the DEPR RET/STBY/PRI OFF/ toggle switch ? I looked into my Dunc Keystroke file and couldnt find anything…
-
ice, quick questions.
Is there a way for touchcontrol to remember the switches and toggle positions when switching to an “activity” to another ?
I explain you why.
your main activity page is named “Switch Panels and ICP”
Whenever I go to a Nav charts, and come back there, the switches go back to their starting position…
Its not much of a problem since I rarely use these charts in flight… BUT…
I just created another “activity” wich is named “ALLPS” (for all panels) and in which I have replace the ICP and the MASTER ARM panels with a few more switch panels, which I intend to fill with ALL the other switches present inside the cockpit, so that you can make a full ram start from the IPAD.
I have put on button on your “Switch Panels and ICP” activity that brings me direcly to the “ALLPS” activity, and there there is another button to bring me back to your “Switch Panels and ICP” page… the only problem is that when I switch from one to another and vice versa, the switches always reset to their original and starting page.
Any way to fix this ? I understand that switch from both pages cannot be “synchronized” , but it would be great if they would at least stay in the position I put them before changing page.
If that doesnt work, I plan to have both page in the same activity, one above the other (1024x1536)
Thanks
-
Thanks for the kind words, Shung.
While I am at awe with your work, I am worried that you are cramming too much in such a little space. It isn’t exactly the “fit” I am worried about but your ability to operate them in-flight! Have you set it to recognize taps or swipes? In any case, that is the reason I made them work with the gesture pad, to give you a bigger “space” from which the control inputs will be recognized. The smaller the space, the more likely you will hit a wrong switch by accident. That is what I meant by “fitting” of the switches earlier. That is also the reason why the Master Arm panel and switches are big.
For instance, the HUD panel and Sensor Power panel do not need to be on the screen… you set these switches as you power up the aircraft or at fence in and shouldn’t need to touch them again. You will notice that I’ve only put in the controls available in the Aux panels and Center pedestal (plus lights and refuelling switch!), those that you need in front of you.
As for the switches resetting, I never got that far… sorry.
Sparks, what do you mean for Helios? I have a 22" touchscreen now (and the reason why I can’t continue development on iFlyBMS) and I am using Helios on that.
-
All the toggle switches I added are gesture pads (swipe actions) and while they are more crammed than originally, I have had no issue using them at all. They work fine and I have no conflicts in between them. The Ipad is very accurate for that.
I happen to change certain HUD settings during flight, and that is reason why I integrated them to your page. same goes for the FLCS switch… I would like to add more (like the EPU switch, or even all the test switches) but there is no room anymore. This is why I had the idea of a second page, without the ICP but all the switches.
But i cannot work this out if switches reset while you change pages.
Maybe i’ll go with the double lenght resolution background instead.
Too bad about switches reseting with page (activity) changes. I think I am going to ask Dave about it. Maybe he has a clue.
-
A scrolling background option might be your best bet for the meantime.
-
Hello Shung,
Would this become available for public use later on?
Well, I dont consider any of this to be mine. So as long as Ice agrees, I will share any mod that I have done
-
Hello,
I agree with Ice that your layout possible will be too compressed to be easy operational on
the relative small IPAD screen. For helios with bigger screen it woul become better.Anyway i certainly would try to see how it does work as working with helios does cost me too much fps.
Perhaps your profile / iflybms also would work on a standard touchscreen?
-
My layout is not too compressed. It works just fine
-
Or you just have smaller fingers or more accurate input, Shung. I know I sometimes had trouble with the switches in iFlyBMS.
Sparks, what is your problem with Helios? How much FPS are you using? Or what videocard do you have? I lose 10fps when using Helios and MFDE but that’s from 40fps to 29-31fps. Funny thing is I noticed when flying with clouds off, I get bumped back to 40fps even with Helios and MFDE. But that’s with my HD 6970 pushing pixels on 4 screens, so I think that’s fair enough.
I doubt if iFlyBMS will work with any other device than an iPad, simply because TouchControl is an iPad app. For a standard touchscreen, Helios is what I’m using.