stevehookem wrote on Sep 17^th, 2008 at 11:18pm:


Steve,

Nice gift for your son!!!

First off, I do have to say that the phrase "on the cheap" and "simpit" are oxymoronic.    But it doesn't have to be a Warren Buffet budget either.

Almost anything is "possible" given enough time, money, and expertise.  One guy I know runs his whole pit off of ONE computer with undocked views.... but also a lot of "hardware" attached to interface it.

This subject is NOT easy to do; there are no real overall total "plans".  It is a "solve issues as you go along" type project.

My pit is rather "generic".  So you might want to look at all the threads in the sticky at the top of this forum section for some ideas and construction concepts.  

Typical layout for the MIP in a three monitor setup is the PFD on the left monitor (with maybe also the clock and so on), the ND and backup altimeter, airspeed, and horizon on the middle monitor, and the upper EICAS screen on the right monior.  In some cases you can squeeze the PFD and ND on the left monitor, and then the backups and Upper EICAS on the right monitor.

As to avionics packages:  Personally in the "bang for the buck" department, I think the new Ellie Avionics Systems offerings are the way to go for most or all of it if the features meet your needs (Boeing Glass).  The full package is still under development, but the existing releases are excellent.  

I also am highly partial to FSXpand.  That package gives flexibility that most others don't:  The ability to create and CUSTOMIZE individual gauges.  I use that for my EICAS...and have all the internal function parameters set to match the tech specs of the Lycoming engines in my BAe 146-200.  

Project Magenta's features are fantastic.... but so are their prices.  And thay are very aircraft specific as to the package.

Using freeware for this to me comes with a liability.  Waiting for people to have the spare time to update/fix/finish it.  Most of the freeware I have found just doesn't hit the bullseye.  Free is a nice price....... but there IS that saying "you get what you pay for". (Which DOES apply to Project Magenta too.)

One thing you need to add to your list above is a LAN switch and the cables to set up a home network for the two machines that will run the pit.  You want a SWITCHED network, not a hub.  You need to set up the network so that data traffic is smooth and free between the two machines.  ("Home Networking for Dummies" anyone?) I will venture to say that as this develops, you'll eventually add a third machine and maybe a fourth.  

How to install the avionics packages on the second machine is usually well documented by the seller of the specific package.  Most depend on WideFS.  In some ways it works like "magic".  The Ellie ND is a self installer.  Once the network is running, and WideFS is installed, you just install it, position it on the monitor where you want it, and it works.

The really large amount of "missing stuff" in your above posting is the interfaceing to get buttons / dials/ switches to be read by the program.  The goal of a pit is to eliminate the keyboard and mouse.  THIS area is the part that usually takes the most money and time.  Somehow you need to get a toggle switch on your panel to be seen by the sim.  There are LOTS of approches to this.  (Rather than rehash all this, see the threads about my pit for one example.)

One of the simplest to hook up and maybe the "starting point" is to get somethiong like the Hagstrom KE109 keyboard encoder.  That unit will let you hook up switches of all types and directly address anything that can have a keyboard assignment from the default FSX menu of keypresses.  

The second "half" of this interfacing issue is that the avionics package on the second machine does not "work" from the avionics in the sim.  So for example to change the range on the ND display, changing it in the aircraft in the sim will not change it on the second computer.  So you have to get the SEPARATE controls for the avionics into the SECOND computer.  This usually involves a second interface system.  On my pit the ND computer ALSO has a Hagstrom keyboard encoder card running on it.

Going one step further in "complexity", with the paid version of FSUIPC, those keyboard encoders will also allow you to use FSUIPC offsets to change values in the sim that are NOT on the default key assignment listing.  

Unfortunately, learing to use FSUIPC is a matter of wading through the HUGE documentation that Pete Dowson provides and learning a bit by trial and error.

One of the things that you DO want to do right off is ditch the standard Windows joystick controls and use FSUIPC to control the axis inputs.  That one thing will improve you sim experience 100%.

One thing to remember is that in a simpit, you "lose" access to all of thoise mouseclicks on virtual panels that you have in a desktop situiation.  On those three TripleHead2Go monitors.... you just want outside scenery.... not the inside of a fake cockpit.  SO that becomes a REAL problem for some aircraft.  many functions are ONLY accessible from those mouseclicks.  THAT is a whole subject unto itself...and one that any simpit builder wrestles with.

The last great frontier of simpit building is enclosing it.  I don't think HOW you enclose it is as important as just doing that.  Having an "aircraft looking" interior is certainly nice...... but just isolating the pilot from outside visual references makes a WORLD of difference in immersion.  (BTW... on the outside myu pit looks like a closet.  On the INSIDE however, it looks like an aircraft.)

Hope all of this helps.

best,

...................john

stevehookem wrote on Sep 18^th, 2008 at 10:09pm:


Steve,

Aside from throwing the "Warren Buffet budget" at it... I really don't know.  Again, from what I know, there are no "simple" solutions.  Aside from purchasing an already set up cockpit system.... which ARE available.... and which are BIG bucks.  Even the kinda "generic" ones.

I think that you need to research what each component you are considering can actually DO... and then decide what other "plug and play" components will add necessary functions.  It'll take a lot of research to figure out what is the best combination of things.

One place to look for a lot of "plug and play" functionality (which STILL takes configuration and setup to assign the functions you want it to control) are the Goflight units.  They are highly configurable.  Take a look at their "packages" already set up in metal console cabinets.  I use a number of their panels including the MCP and four of their VRP 166-s for my comm stack; they are GREAT. 

With enough of their units, you could likely eliminate the keyboard and mouse for a lot of aircraft.  Not maybe the more complex aircraft....but certainly the default stuff.  It will be a very generic look......but that is not necessarily bad.  Still a HUGE jump from a monitor, keyboard, mouse, and joystick  .

Undocking screens might be the way to go for you.  But that is a difficult row to hoe too....in getting it all to go where you want and getting it to STAY there.   

I am sure some others will chime in here soon with more thoughts.

best,

..................john