The idea is to have all the input/output at the right positions respective to the player. For me it’s no use/fun to just have all crammed on 1-2 monitors. It’s about kinesthetic memory so that, in any simulator the player gets in, he can play right away, without accommodation.
I tried to play BMS on a regular monitor/TV and a joystick with throttle and even with FreeTrack, it’s too complex, too realistic, too damn sweet not to play it as close to a real… simulator.
As for the money, I guess the frame would cost me just as about as the monitors; and I don’t have the room for it, so I’m gonna improvize something in the living room and mount/dismount every time. Something like a chevalet for central panel and 2 stools for aux

In that video he’s using a 3- video card rig and I guess he plugs in the 10 monitors plus the projector in 4-output cards. I prefer monitors over tablets so much more because I’m not willing to delve into Android but if I’d have to eventually, I would. The link you gave is about touch overlays to put over regular monitors. I looked for touchscreens on ebay on my own and could only find the same: screen overlays.
BTW Nice cockpit the one on YouTube. It fills me with constructive envy :d although I wouldn’t go so far as to build/buy the framework.

Thanks for replying.
Focaldesign, all I could find is touchscreen monitors, which are useless since you can’t connect multiple ones. Without sarcasm I’m saying that I’m not aware of other technology like i.e. touchscreen without OS that’s purely an input/output HID. It would be awesome if it were, since I wouldn’t have to program for Android. Or it may be some video signal splitting but I doubt it’s feasible for 6 screens. As for tablets use, a PC can have like 12 USB ports
BTW, thanks for open up my mind – I have to reduce the monitor count to a total of 6: 4 central console + 2 aux. Please tell me if there’s more I don’t know.

roccio, first thank you for offering me your software. I’ll check it out what it can do and whether you can totally customize layout of output/input on the tablet. If it can pull it off with your ware then I’ll be in debt

Hello there.
I want to make BMS experience as enjoyable as I can of course like everyone else here.
In my opinion, the best compromise is a physical cockpit but as for the poor mortals like myself it’s impossible to build one, the next best thing is extracting MFD’s and consoles to touchscreens (tablets). It has been done on various ways (komurcu, steveh2112, mikej et al). Now what I am after, is to extract ideally all the consoles (left/right, aux, Instrument Panel) zone by zone according to their layouts/positions as close as possible and put them on android tablets as they’re very cheap – you can get one with $50. So ideally:

• instrument panel 4-6
• aux consoles (left + right) 2
  and maybe if it’s not much hassle,
• left+right consoles 4-6
  So you have a physical virtual pit made of 8 to 14 tablets, for $400 to $700. Plus you avoid hardware labor. Plus you can easily mount/dismount the pit. Plus you can also use the tablets for some other projects etc.
  I’m willing to spend $400 and have 3 consoles – center + aux.

Now the questions:
1. Is there a way for a regular user to do input/output (cockpit buttons/MFD) extraction to android tablets? regular user = beginner C++/C#/Java programmer. Are there any tutorials/documentation/walkthrough’s? Where can I get help?
2. What limits the number of tablets simultaneously usable?
3. Other considerations?

Hello.
You guess what I’m asking here. I’ve been looking for stuff about it on the web but can’t find anything. So, anyone knows anything? I could bet Kinect beats TrackIR.
If no one tried it, I could come up with something like outputting Kinect data but where to feed it?

@Dog:

yeah we use that but only after 4 am and 3 six packs each

“Theres a !”$#%$#%$#%!!! on my six" is the most heard anyways hheheheheeh

Second price goes to “Im Funking TUMBLEWEED!!! AAAARRRRRRRRRRHHHHHH!!!”

You got me getting off the desk laughing, lol

Thank you very much, tyrspawn for the tuts.
Man, call me lazy but IMHO this is the best approach for learning BMS (and any other possible subject you could come up with): visual crash course to constitute a general overall frame upon to start building details from documentation. Now, I’ll figure the docs out at the first glance w/o the need to re-read it 3-4 times (it could only work for me – I may be dumb). Think of it as interlaced vs. progressive image rendering.
LE:
Thank you Chappy, I didn’t see your post first time.

@crazyTom:

PS: One exception…I recommend checking this for an alternative and easy way of landing the F-16 (good weather, no ILS) and be automatically on the correct AOA, pitch and speed values…pics in that doc pretty much tell all you need to know once you understood the basics of the shown symbology.

http://www.scribd.com/doc/22015850/F-16-Landing-Tutorial

Cheers

Can you post a download link, please?

Wow! It looks like you have what it takes to rule the skies, man. Nice panorama on those monitors. And giving it a thought, it’s the (one of the) best setups for its worth. I suppose you’d have displayed the HUD only on the central mon. if it weren’t for the FOV decrease. Otherwise why would you need the upfront on the mon?

It’s never too much visual for my taste and that looks yummy

@-Ice:

Why not have everything you want on a touchscreen and buy a different monitor for the display? That will work 100%. With my Cougar MFDs, Warthog HOTAS, and a 10" Lilliput touch screen (running Helios), the only time I reach for the mouse is when I’m on the 2D screen. Once I’m in the pit, all the controls I need are literally on my fingertips!

I’d like to see the setup, can you post an image?

A software implementation would be through shaders. At rendering time, when the objects’ coords on screen are known, output them for clicking coords. Who knows shaders may find an idea in this