Rick, and all in this thread,
Sorry to have been AWOL for awhile from the forum and having missed this thread until this morning !
Pretty much everything has been said about the how's and why's in the various replies.......so I would just like to add some ENCOURAGEMENT to those of you who are just getting started with the multi monitor setup.
It IS worth it.....and the FIRST time that you takeoff from a runway, say 14R at ORD.....and then fly a left hand traffic pattern at 2000 AGL for a touch and go back on the same runway of 14R.....and NEVER EVER lose sight of that airport out of your left side views........you will THEN know that your setup was all worth it !!
I do feel that we are going to see more and more multi monitor home cockpits because of the EASE of setting up a LAN with WinXP. I am sure that James, Greenie, and myself have spent MANY an HOURS<g> in the past with the old WinSE, ME, etc., in doing that LAN setup because it used to be so darn HARD to get everything to sing from the same page. NOT today.....WinXP makes it very easy with the Wizards......and to top it all off....you can buy a 10/100 ethernet card for less than 20 bucks.......or if you are in the market for a new computer the networked card is already onboard in most cases.
WideView does not yet permit the Instrument panels to be spread out over other Clients from the Server....so until Luciano comes up with that brainchild.....it IS best to use the Project Magenta software to have the Primary Flight Display, the Navigation Display, and the EICAS display on other Clients and screens. NOW, all your Server has to do is provide an OUTSIDE view...and that greatly relieves its workload and gives you superb frame rates EVEN in 2D mode.
I run ALL of my clients.......4 of them powering 8 monitors...in 2D mode. Each of those 4 clients AND the 1 Server are all using the Matrox G-550 dual head cards and run at 2048x1024 resolution ACROSS 2 monitors per computer. My resolution setting for FS2002 is 1024x760.
I limit my frame rates to 16 fps for the Server to keep the "blurries" away......and I run the Clients at 10 fps for the same reason........this still allows those Sliders to ALL go full to the Right !
My Server computer is a Dell 1.5 ghz.
The Clients are a mix mash of brands....and run from a 900 AMD, a 1.1 P4, a 650 P3, and a 1.5 P4.
The Instrument portion of the cockpit has a P4 1.5 running the PFD and ND(this is OVERKILL for speeds.....not needed but nice) and a lowly HP 450mhz that runs the CDU and MCP software.
I would recommend that when you begin this plunge.....you first PLAN your layout for what you NOW have....and for what you MIGHT have in the future. In other words....allocate DESKTOP space NOW....so that when you do add more screens and CPU'S later that you do not have to change your "core". You WILL add more later. Grin.
It is also very much simpler, for that future time.......to have ALL monitors the SAME size....so that your horizon lines are easier to maintain on those outside view turns....and luckily with 15" monitors so CHEAP these days....almost anyone can afford to buy more.....NOT forgetting that IF you are using the Matrox G-550's....that you ARE turning TWO 15" monitors into ONE 30 INCH MONITOR!
I think a nice basic starting point would be two add at least TWO computers to your current FS2002 setup....and I would place them as a Look Forward Left and a Look Left setup along with your regular Look Forward view of your current display.
You will then do a lot of LEFT turns in the pattern. Grin.
Until you add the Magenta software.....you can switch your Server view between regular and Virtual cockpit views.....using the regular Instrument view for takeoff....the VC view for the pattern flying, or enroute...and then back to regular for the landing.
Once you have added enough computers and monitors to use Magenta for the inside stuff.......you can keep that Server banging away with the W key of nothing but enjoyable outside views.
Okay.......off of the soap box........time to fire em up. Grin.
Regards,
Cap'n Tarmack