IFlyBMS
-
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.
-
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.
Ice,
We already did discuss on the helios/gadroc forum, still looking for improvements
Think it is time to setup 2nd computer for testing in network environment.Regards
-
Looks great. Only 1 small problem: Touchcontrol no longer available in Appstore.
Any other solutions?
FF -
Looks great. Only 1 small problem: Touchcontrol no longer available in Appstore.
Any other solutions?
FFWeird, I still see as available on Dutch App Store.
Perhaps also check http://www.touch-ir.com/
-
The new offical version works fine !
Anyone interested by the horizontal ICP ?
-
I am, definately. Thanks for trying. What would also be cool is to have all switches and buttons positions update when the “ICP and buttons” page is accessed. Right now, I have to put them al in the correct positions each time I select that page, whether I’m selecting it from the main iFlyBMS page or from the other pages (“Nav, Checkists”, etc).
Thanks again for your great work.
Judy -
I am, definately. Thanks for trying. What would also be cool is to have all switches and buttons positions update when the “ICP and buttons” page is accessed. Right now, I have to put them al in the correct positions each time I select that page, whether I’m selecting it from the main iFlyBMS page or from the other pages (“Nav, Checkists”, etc).
Thanks again for your great work.
JudyThat is my main problem too. I was trying to build more switches panel to make a full ramp start from there, and I manage to do it… The only problem is that switches reset to their original position when I go from a panel to another… And I haven’t managed to fix this.
I think I should try talking with the creator or touch control to see of there is anything we can do about it. I think Ice is not focused on developing IflyBms at the moment, cause he went another route, but with his approval, we might try developping it further.
I am going to upload the horizontal and improved ICP version tonight.
Btw, you might have to rework your falcon keystroke, because mine was adapted to use in conjunction with Ifly BMS, a hotas cougar with dunk profile, and shifted thrustmaster mfds.
-
Great work Shung. I cannot imagine why I would not approve of you (or anyone) taking iFlyBMS further than where it already is, so please do go ahead! I know of at least 3 other people who I’ve spoken with that use this program so I know it’ll benefit at least a good few simmers.
I do apologize for leaving the project and appreciate the understanding. However, I am close to finishing my Helios setup so I may be able to look at this project again in the near future although I do not see myself using it much.
The biggest problem here is the .key file –- everybody has different needs and different setups so the .key file will always be different. Proper documentation of the callbacks added and the keystrokes assigned to them is very important. I would recommend that you guys use Kolbe’s keystroke layout (see here!) and that will give you 1) a complete set of callbacks and 2) a standardized format of the callbacks.
So the callbacks you don’t use, simply keep them blank, but if you ever need any callbacks, they are there ready to be assigned to a keystroke. Also, the callbacks are all arranged in a logical order so it is very easy to find the specific callback both in the game’s UI or in Notepad++
I am currently working on an Excel file that should allow you to plug in your .key file entries, the Excel file will sort it out, and then spit out the end result that you can simply copy-paste back into your .key file giving you Kolbe’s layout. Having said that, Shung and Judy, check PMs.
-
Ice,
Attached please find my key file. Thanks again for your great contribution. With iFlyBMS, F4 is a brand new experience.
-
Excellent work, Shung. I wish I could be of more help, but what you and Ice are doing is beyond my pay grade. Thanks a lot for your contribution.
Judy -
Judy (and Shung), you can get the Excel file here. Please give it a test, I’d like to hear your thoughts.
-
Thanks Ice. Will do. Give me a couple of days.
-
Ice, I’ve followed your instructions about the Excel spreadsheet and the sound mod and made a few test.
First, the conversion of my .key file into a standard “Kolbe-style” .key file worked without a flaw.
Of course, I’ve had to modify the callbacks in BMS Setup to accomodate my configuration (HOTAS Cougar + 2 Thrustmaster MFDs + iFlyBMS), but that went OK too. The only problem remaining, well at least on my end, is that the ICP page in iFlyBMS still resets to its original state after I select it from another page (e.g. Nav charts). Maybe I’m doing something wrong. I’ll keep testing and let you know.
Judy -
Nice to hear the Excel file is working. I’ve noticed a few issues though…. some callbacks that I use (HUD declutter, HUD color change) were not in Kolbe’s full .key file, but it was easy enough to add them.
Can you confirm that the sounds are now working in iFlyBMS? I think the gear lever did not have a sound before this but it should have a sound now, a big, strong “thunk!”
-
havent had time to test yet. will do.
is that the ICP page in iFlyBMS still resets to its original state after I select it from another page (e.g. Nav charts). Maybe I’m doing something wrong. I’ll keep testing and let you know.
Judythis is something I dont know how to change either. And its a major limitation for creating more switches panel on new pages. (my goal would be to create a whole set of panels, for each cockpit part)
for DCS A-10C i use a thing called I control DCS… it has its own app, and its own server software. the cool thing is that in I control DCS, when you depress a switch on the virtual cockpit, it actually gives a feedback to the Ipad app, and changes the switch there too ! I dont think we can ever do that in BMS…
But i would settle for iflyBMS and i touchControl, memorizing the previous switches positions when you go from a page to another… and not reseting to initial position.