Gumps

Are you folks running FSX in 'windowed' mode? Anyone else doing this with multiple monitors?I noticed when in full screen, my FPS are down around 8 FPS! I suppose it lives up to it's name of "Frame Limiter", but that's not what I had in mind! :-)I followed the directions in this thread, launched the *.bat file, FSX launches, but is a slide show. It seems that the applet is having an effect, but not the correct one.My OS and FSX are tweaked per Nick's guides. With unlimited in my test scenario, the FPS bounces between 40 and 60 without the applet...hangs around 8 with it running. (??)Anyone else seeing this?Noel WBrisbaneC2D E6850@3.8WinXP SP2FSX SP2

Hi NicolaI'm at work at the moment but will put something more descriptive together later. I started out with one screen, added a couple more...and got carried away I suppose. You can never have too many screens!Noel WBrisbane

I hear you on not liking to use a mouse. Not only the mouse, but I wanted to get away from having to rely on my CH HOTAS buttons, which becomes messy when flying different aircraft with different functions. You can certainly program different profiles, but often have to assign different functions between aircraft to the same controls.I've ended up with 4 touch screens. I decided that anywhere I had an instrument panel, I'd make it a touch screen. I added 2 17" widescreens to my existing setup, and added touch screen overlays to 2 19" widescreens I already had. Having the extra 'real estate' of the larger screens, versus say an 8" screen, allows the flexibility to place various panels and subpanels on the touch screen(s). I open and close various panels as I need them.I'm quite happy with the outcome, but I was not able to completely get rid of the mouse. 'Right-Clicks' can be tricky sometimes as well. For the FMC (MCDU), it's magic. Ditto for many other controls. I bought everything off of eBay.The other gem is TouchBuddy - I use that on a networked computer to add my own 'controls'. Great piece of software.Attached is an overall view of my setup, which really involves three computers. (These pictures happen to be of the CoolSky Super80 Pro...rest assured I have several PMDG aircraft...the MD-11 being my absolute favorite addon bar none.) The touch screens are where all the panels are located, and the lower left approach plate, which I also use for the TouchBuddy software...just toggle between the two.Noel WBrisbane

Heck, I'd think it would work. If I'm not mistaken, the 8000 series cards are all DX10 capable. Perhaps someone can correct me if I'm wrong.Noel W

Hi GeofaMy 'outside view' monitors are 4:3 19" 1280x1024. So TH2go Digital (a must, not the analog version with no 'bezel management') tells the computer that those three screens are really just one screen at 3840x1024. So that is on one port of the graphics card, the other drives the lower screen. They can be different resolutions. You must tell FSX that each are different as well (in the Display menu). There is a driver upgrade for TH2go which allows you to use three widescreen monitors for a resolution of 5000+ x 1000+ (I don't recall the exact resolution).And yes, I use only 2D panels. I have seen people just use the TH2go and VC, plus TrackIR. That's a nice arrangement as well.Now this is just me of course, but I like the sharpness of the 2D panels, and nothing blocking my outside view. With three screens totally dedicated to the outside world, you can sure see a lot more. Coupled with all of the nice texture and terrain modifying addons (GEX, UTX, REX, FEX, FTX etc), the view can be spectacluar.In my current setup I'm using six screens. In the same way that the extra screens open up the outside view, more panel views give you more room to layout the instruments and other detachable windows. A lot depends on how accommodating the addon developer with their panel management. PMDG is a good friend to the multi monitor users, as are others.There's a pic of my mostly complete system in this post (maybe you saw this already): Pic of MultiMonitorsHope this helps.Noel WBrisbane

Hi RonI use multiple monitors and video cards, and TH2go. There's really no way to duplicate what TH2go does with two video cards, that I know of anyway, if the object is to run FSX in Full Screen mode. If I'm following you, the outside view, which is desirable to be placed across 3 side-by-side screens, won't work using two cards, unless perhaps in Windowed mode. My FSX runs poorly in Windowed mode. And running the outside view on just two screens...you end up with the break in view right in the middle. OK for autolands; bad for manual landings.Once you go to Full Screen mode, the images snap to whatever screen they were mostly on. I say "mostly on", because, for example, with the PMDG MD-11, before I go to Full Screen, part of the Capt's panel, the center post etc. spill over onto the upper screens. But when I go to Full Screen, only the portion on the lower screen shows. (Thank goodness Microsoft made it this way.) Maybe someone else has had better luck trying to span multiple monitors in Full Screen; bad stuff always happened when I tried this.I see you're on the other end of this great continent...I'm on the east coast in Brisbane. This stuff is a whole lot easier to explain in a 2-way conversation, and I could get a better understanding of just what you're trying to do. I'll PM you my contact details; feel free to call if you would like to discuss further.By the way, are you running WinXP or Vista?Noel WBrisbaneP.S. Here's a pic of my system a while back when I was using four monitors...is this what you're after?

JimYou're right about the MB PCIe slots...I looked that up in the manual. Now why didn't I think of that? [Please, I don't need any suggestions from anyone. :-) ]And yes, I think your thoughts regarding DX10 make sense. It certainly works this way in practice. I think FSX is thinking something like this (when the DX10 card is in the 1st PCIe slot):"Say, I see you have a DX10 card there (8800). Great! Wait, who's that with you? (7900) Nope, your buddy is weak, my friend. Friends don't let friends play with weak video cards."But when the 7900 (non-DX10) card is in the 1st slot, the conversation takes a different twist:"Ooooh, 7900! I have not seen someone using that for a main video card for a long time. [Computer thinks to itself, "what a dope".] Well, if you want to try and run FSX with that, go ahead. I do see you have a muscle bound friend, I wonder what he's doing with you...run along and have fun." [Computer snickers to itself and notifies other computers on the internet of owner's gaff.]I did get a 9600 card and put it into the second PCIe slot, and *tada*, success. [sound of champagne cork popping.]All is well with the system now. Oh, except for all of the tweaking and loading I have to do now.Finally, I have successfully migrated from XP 32 to Vista 64, and no animals were harmed in the process. Hehe, that was easy. Not.Thanks Larry and Jim for taking time to post your informative thoughts. Hopefully the next poor slob that runs into this will surface this thread and benefit.And finally, running multiple monitors is well worth it. I have two touchscreen overlays on the way, which will enable all (3) of the monitors with panels. When I get this all nice and tidy, I'll post a picture. Perhaps it will inspire someone else...or scare them away.Best Regards,Noel WBrisbane

LarryGood to know...I'm hunting around for an inexpensive solution.Also, can you confirm that this was a Vista issue for you? Are you using the 32 bit or 64 bit versions?Noel W

LarryThanks for that info. That is the first report of someone actually running two cards successfully. I'm assuming that you're running Vista too. (??)In a similar vain, yesterday I took a spare 7900 GS and installed it along side the existing 7900 GS. I was at least able to prove to myself that yes, I could run two different graphics adapters without the dreaded FSX dialog box. But the 7900 GS does not have enough horsepower to run TH2go + another monitor.Then I installed the 8800 GTX in the lower PCIe slot...and voila, that worked too.Not so fast. I run TH2go on the 8800 GTX, and when the outside visuals are spread across those three screens, it gets real choppy. Stutters every second or so. This is with a default airplane. I've not optimized the OS yet, but this doesn't look right. I'm starting to wonder if the 8800 GTX doesn't like being 'second fiddle' in the second PCIe slot. I wouldn't have thought it made a difference. (MSI P35 Platinum Combo MB).I swapped the 8800 back to PCIe slot one, and the FSX error dialog box once again prevented FSX from running. Grrrr. Not there yet...but making progress.Based on what you've written, I wonder if I could get away with replacing the 7900 with a later (DirectX10 compatible) card that doesn't cost an arm and a leg, as opposed to the more obvious adding another 8800 GTX. Again, I'm not running the outside visuals on the second card, just panels. And in XP, the 7900 was enough to do that. Hmmm.Thanks again Larry,Noel WBrisbane

Thanks for the response, Nick. I too would have waited until Win7 Final, but as I indicated, I'm compelled by the OOM issue.And yes, the Vista 64 DVD I bought was already at SP1, and I downloaded a large number of subsequent MS updates...so it's as patched as much as possible at this point.In this case, it seems to be FSX SP2, when combined with Vista, that's the bad actor. Apart from coming up with something clever on my own, I can't see MS addressing the issue as it's certainly a 'corner case' - not that many people are affected.As I said before, it would sure be good to hear from someone trying a similar configuration. If someone has managed success with Vista and multiple cards, I'd know whether to keep pursuing this or not. From my reading, I've not come across any successful reports.Noel W

Hi NickSeeing your reference to multi-monitors...I'm hoping you might have some advice on an issue I'm having with multiple monitors, or more correctly, multiple graphics adapters, Vista 64, and FSX SP2. I posted the details but have not gotten any replies. Vista64 + FSX SP2 + MultiMon Impossible?, "This graphics card does not meet minimum requirements..." In fact, here's the text of that post:=====================After a bit of reading (apparently not enough) I figured it was time to upgrade from WinXP Home to Vista64 for my FSX machine. My machine has 4Gb of ram installed that I wasn't able to employ, and the OOM villain was beginning to knock on my door. I tried Win7 64 but the necessary drivers for some things were missing...and the V64 drivers didn't work. So, new HDD, and new OS.I was working my way through the load list, controllers, touch screens etc. I use TH2go (3 x 1280x1024) and a 1440x900 monitor on a 8800GTX. I run two more 1440x900 monitors from a 7900 GS. Works fine in XP. Worked fine in Vista 64...until I loaded FSX SP2. After the FSX splash screen appears, a dialog box pops up that says, Invalid Hardware or Driver Detected - "This graphics card does not meet minimum requirements for shader support. This product requires a geForce3/Radeon8500 class or better graphics card. Flight Simulator will now exit."I've tried a couple different Nvidia drivers, currently using 185.20. Vista itself seems happy with the extra monitors, so it does not appear to be the issue cited by microsoft having to with "Homogenous multi-adapter". http://support.microsoft.com/kb/929456. It seems tied directly to FSX SP2. Some of my newer addons require SP2, so just going with SP1 doesn't seem like an option.If I disable the second adapter, FSX will start. I even tried disabling the adapter, starting FSX, then enabling the adapter...nice try. It just ignored the 'new' monitors'.I searched the web and found similar reports but no solid solutions.I wonder if there's a way to get FSX to not check...mind it's own business, so to speak. (??)It's not looking real promising but figured maybe someone has solved this. Otherwise, it's back to XP. Geez, I wonder if Microsoft will give me a refund. Ya, right.Thanks in advance for any advice.Noel WE6850 @ 3.88800 GTX + 7900 GSTH2go4Gb RamMSI P35 Platinum Combo MBCH ControllersVista 64FSX SP2====================I've uninstalled FSX SP2, and all is well. This is a real pisser as I'm stuck with buying an OS that I can't use for the purpose I bought it. I've tried a number of drivers, old and new beta, to no avail. I've wondered about trying to get a hold of another graphics adapter, ideally another 8800 GTX like the one I have. But I'm not sure that will work either.I did loadup FSX SP2 on Win7 32 with one of my complex addon aircraft and verified, that with the memory command you supplied in your tuning guide, I'm not having any OOM issues. And the way I was running it, heavy weather, autogen, etc., it would have burped on WinXP. I'd really like to get Vista 64 going though.If you have no comments, well then so be it. I suppose the million dollar question is, does anyone have Vista 32 or 64 running with FSX SP2 using more than one graphics adapter?I can run multiple monitors off one card, but if I activate the second card, FSX SP2 won't start.Noel WBrisbane

Well heck, I feel like I'm talking to myself! I figured someone would have something to say...no one has seen this?I tried some older Vista64 Nvidia drivers for the heck of it. No joy. Tried the last beta drivers too (181.22 as I recall.)I uninstalled FSX SP2, and FSX works fine with multiple adapters and monitors.I was on FSX SP1 for a long time because I read so much about the menu CTD problem. I always fly full screen, so I knew I didn't want those problems. But, with so many new addons 'requiring' SP2, I loaded it...and no problem. On WinXP, that is.Does anyone know what problems I'm likely to encounter if I run, say for example, the PMDG MD-11X or other addons with FSX SP1? What kind of stuff doesn't work?Incidentally, I've added touchscreens lately. Doesn't completely replace using the mouse (yet), but very nice for many things. I'm also using TouchBuddy to control a number of FSX items. Work in progress.Any responses are appreciated...even if it's just condolences.Noel WBrisbane

One additional item - I did verify that this (FSX with multiple adapters/monitors) works fine in Win7 32 beta. I don't have FSX installed on my Win7 64 beta, not sure there...I do know my touch screen drivers don't work in Win7 64. (All OS's are on different HDD's).So, if nothing else, I guess there's hope for the future and Win7. My problem now is that I'd like to have a working 64 bit OS for FSX and my hardware. I chose Vista 64 over XP 64 because, I figured it would be more advanced in some areas...and it was cheaper.Again, if anyone has any advice, I'm all ears.Noel W

After a bit of reading (apparently not enough) I figured it was time to upgrade from WinXP Home to Vista64 for my FSX machine. My machine has 4Gb of ram installed that I wasn't able to employ, and the OOM villain was beginning to knock on my door. I tried Win7 64 but the necessary drivers for some things were missing...and the V64 drivers didn't work. So, new HDD, and new OS.I was working my way through the load list, controllers, touch screens etc. I use TH2go (3 x 1280x1024) and a 1440x900 monitor on a 8800GTX. I run two more 1440x900 monitors from a 7900 GS. Works fine in XP. Worked fine in Vista 64...until I loaded FSX SP2. After the FSX splash screen appears, a dialog box pops up that says, Invalid Hardware or Driver Detected - "This graphics card does not meet minimum requirements for shader support. This product requires a geForce3/Radeon8500 class or better graphics card. Flight Simulator will now exit."I've tried a couple different Nvidia drivers, currently using 185.20. Vista itself seems happy with the extra monitors, so it does not appear to be the issue cited by microsoft having to with "Homogenous multi-adapter". http://support.microsoft.com/kb/929456. It seems tied directly to FSX SP2. Some of my newer addons require SP2, so just going with SP1 doesn't seem like an option.If I disable the second adapter, FSX will start. I even tried disabling the adapter, starting FSX, then enabling the adapter...nice try. It just ignored the 'new' monitors'.I searched the web and found similar reports but no solid solutions.I wonder if there's a way to get FSX to not check...mind it's own business, so to speak. (??)It's not looking real promising but figured maybe someone has solved this. Otherwise, it's back to XP. Geez, I wonder if Microsoft will give me a refund. Ya, right.Thanks in advance for any advice.Noel WE6850 @ 3.88800 GTX + 7900 GSTH2go4Gb RamMSI P35 Platinum Combo MBCH ControllersVista 64FSX SP2

Hi GerardI'm currently running FSX and the MD-11 with 5 monitors (dang, that MD-11 is just incredible)...TH2go Digital runs 3 19"(1280x1024) at 3840x1024, and 2 19" widescreen monitors above and below for the main instrument panel and overhead panel. (Note: TH2go *Digital* is a must IMO, because of the 'bezel management' feature...vs. the Analog version.)A 8800GTX runs the TH2go and the main intrument panel.A 7900GS runs the overhead panel.When they arrive, I will be adding a 17" widescreen touchscreen for the MCDU and other subpanels, plus, I'm adding a 17" touchscreen to a second computer networked to run TouchBuddy (so I can control some of the 'administrative' FS items without poking around in the FS menus...just poke a button on the screen). If the touchscreens work out, I'm hoping to add touchscreen overlays to my existing overhead and main instrument panels...but I'm not sure if all of those touch screens will play together happily. I'm hoping Win7's touted touchscreen support will help out here. I have the beta, but haven't gotten that far yet.In anticipation of adding yet another screen, I temporaily hooked up another 19" monitor, bringing the total to 6 actual monitors, and noticed only a slight effect on performance. I think that this might be due to the fact that I'm only using instrument panels on the 'extra' screens - no outside views.My system is:C2D E6850 @ 3.88800GTX (stock)7900gs (stock)4 Gb DDR2 ramMSI P35 Platinum MBWinXP SP2 Home (should have installed Pro...)FSX SP2I normally do not use Autogen...I can with some hit, but I often don't like the look40% Airliner traffic (no GA) and maybe 5% carsWater 2x lowI start FSX in 'windowed' mode, undock all of the panels, and drag them to the appropriate monitor where I want them. Save the flight. Go to 'full screen', tweak positions, go back to 'windowed mode', and save using the same file name. Close FSX.I name the file something like "MD-11 Start", and always open that flight to begin with, so that all of the panels (and there are a lot of them on the MD-11) are where I want them and I don't have to go setting them all up again. I just move the airplane to another airport, change the weather etc for what I want to do that particular flight. And I fly in 'full screen' mode.Overall system and FSX are tuned per NickN's sage advice (with some deviation based on local conditions and preference)Having said all of that, the system runs "smooth" in most places. When given a choice between eye candy and smooth, I go with smooth. Just my preference. I stay away from the large congested airports for the most part. I have my FPS locked at 40, and it's 30+ most of the time. In my experience, FSX is never smooth ALL of the time. For example, when the textures change at dusk, I'll see a burp. Also, with side screens (with TH2go), the sense of motion is increased markedly. But the jerkiness on the ground when turning say 90 degrees during taxiing, is more prominent as well.I've used multiple monitors for the last couple of years. I just could never see enough on one screen, and turning base to final was always annoying...using the POV control. I tried TrackIR but never got the hang of it. Mine is now an older version and I know they've made great strides. Many have had great success with that device. I only fly with 2D panels. And to me, there's nothing like having a wide open outside view.Oh, and I almost forgot. As a bonus, when using an exterior view, like 'Spot' or 'Flyby', the airplane is spread over three monitors. It appears huge if you're zoomed in close. Seeing the MD-11 fly by on three screens is quite impressive. And despite what some have to say about the MD-11 exterior model, I think it's very well done. Mind you, I spend most of my time inside looking out, so whatever compromises were made, I'm glad because the MD-11, as complex as it is, defies logic by being one of my smoothest addons. Forgive me for gushing here, but I can't get over how marvelous an addon, in total, PMDG's MD-11 is. A team of people slaves away for many hours over years, and I get to enjoy it all for the price of a nice dinner out. [OK, go ahead and say it. I know what you're thinking. "a really excited user". Hehe, well whatever. I read so much bickering and flaming...maybe this helps balance the scale. :-)]In summary, FPS is an elusive measurement in FSX, as has been discussed ad infinitum. "Smoothness" is subjective as well. But let me say, that last night after flying a 'proper' flight, I switched to a VFR hop at Sion, Switzerland at dusk. With the REX textures, the visuals were just stunning. Taking off towards the setting sun and flying through the mountains, things were as smooth as glass, absolutely fluid...spread across three screens with no instrument panels blocking my view. Sigh...makes all the tweaking worth it.*** Edit: Note that there are two photos...they ended up side by side, so scroll to the right. ***Good luckNoel WBrisbane

NickThank you for taking the time to respond. My sense after reading your input, is that I might end up with a mess...and end up doing a complete install anyway.One thing I wanted to clarify, as I guess I wasn't clear:"Next problem is your original is on the OS drive now meaning any references to the original install on C in addons may cause problems. I don

Hi NickFirst off, thank you very much for all of the advice you have penned on optimizing our OS's and FSX. I've made marked gains by employing your easy to follow advice. You've put a lot of work into not only working all of the technical details out, but then taking the trouble to craft the detailed steps for us...well..."thanks" feels a bit shallow, in light of this. I hope you know there are a lot of readers that appreciate what you've done.OK, that aside, I'm curious about installing FSX on a second drive. I had done it in the past, 'a system ago', but just took the easy way out when I loaded FSX on the new system a while back. I've not reloaded FSX since originally loaded, and have the usual menagerie of addons and tweaks. All of this makes reloading ominous.In anticipation of changing operating systems, if I load FSX on say 'Drive E:', with the WinXP OS on 'Drive C:', can I get away with replacing 'Drive C' with a different OS and run the existing FSX installation on 'Drive E:'?It seems like most Windows apps have to be installed by the OS itself to work, so I wouldn't think my suggestion would be successful. But, could I get away with: (This would take using several/extra HDD's)1. C: WinXP OS; Install and tweak FSX with addons on E:2. Replace C:, install (for example), Vista64; install basic FSX on *replacement* E: (Both HDD's have been replaced)3. Remove *replacement* E:, *re*install E: with customized FSX.My logic was that the OS would think it dutifully installed FSX on "E:", and the paths for the FSX installation shouldn't change...dunno, I'm just not that sharp on this stuff. Maybe I don't even need to try to trick the OS and FSX. (??)Is there a way to 'transport' an FSX installation to a new OS?I have both the 32 bit and 64 bit versions of Win7 that I'm experimenting with, but I know they will evaporate in August, provoking another reload. In short, I want to be able to swap OS's without reloading FSX each time, and all of the attendant addons, controller settings and so on. It sounded like this was how you had your system set up. If you've explained this in another post, my apologies, I did nose around but must have missed it.Incidentally, I'm currently running FSX on WinXP *Home*...I didn't know about the /3Gb switch at the time or I would have gotten 'Pro'. So I can't get the use of my 4 Gb of ram currently. And with a couple of addons, I think overall memory is becoming and issue.I think I want to be on a 64 bit system, but I'm not sure if all of 'my stuff' will work. My FSX system is a little quirky, in that I'm using an E6850 @ 3.8, with two graphics adapters (8800 GTX & 7900 GS...and occasionally add a PCI 5500), with TH2go running five monitors, soon to be adding a sixth touch screen. Plus, I've just gotten started using TouchBuddy over a network with another computer. I have CH Controllers. I'm concerned I'll run into not having working drivers for some of this stuff. I've just loaded Win7 64, so I'll find that out, though of course it's a beta, and driver issue should be expected. (I tried loading a Vista64 driver for my MB audio and it rudely pointed out that what I was trying to load was for another OS.)I am curious about XP64 and Vista64, since they have been finalized...are the driver issues worked out for those OS's?Are there known shortcomings in this regard? (Devices that are widely known not to work.)And advice on this matter would be greatly appreciated.Best Regards,Noel WBrisbane

TomThank you for that advice. Indeed editing the FSUIPC.ini file restored the autobrake function. It's odd though, the MD-11 section of the file, had no brake axis entry information, seemingly 'respecting' my disabling the brake axis for the MD-11 in the GUI. Several other aircraft still had the brake axis info. (??) Well, I deleted it from all locations in the *.ini file, and that cleared it up. Thank you for your advice. Goodness knows, having to apply *manual* brakes, like all those other slobs flying lesser equipped aircraft, is just too much work. :-)Ah well, just the same, it's nice when everything works.And Michael, thank you for the explanation on the behind the scenes change. From my perspective, if it works with the regular FSX Controls, there's no need for a FSUIPC axis assignment. FSUIPC, of course, is brilliant for many other items, but I wouldn't think it's necessary for PMDG or even FSUIPC to make any changes in this regard. (Perhaps there's some particular need for other users...dunno.)Thank you both again for clearing this up. What a great airplane. I still can't get over what a fantastic product this is.Noel WBrisbane

First off, many thanks for all of the tweaks and fixes in the patch for the MD-11X. It took a while to read through and digest it all!I was one that had difficulty getting the autobrakes to work on the original release version. I ended up solving it my using FSUIPC Full Version; deleting the brake axis assignments in FSX, and assigning and calibrating them in FSUIPC. I'm using CH Pro Pedals.Seeing that work had been done in this area, I deleted the FSUIPC settings, and reassigned the brake axis in FSX...but, the autobrakes are not working...again. The release notes say *not* to use FSUIPC...why is that?I did see a momentary flash of the red "Brake" and/or "Differential Brakes" messages in the lower left, I think, but it's as if they immediately disconnect. In the past I'd tested it on the ground, by doing an RTO. When I do this with the patch, I see no red "Brake" message at all. The spoiler handle is dutifully deploying appropriately, it's just that the autobrakes are not playing along. (??)I'll do some more testing and tweaking, but figured perhaps someone else has solved this and can point me in the right direction.Any advice is appreciated.Noel WBrisbaneC2D E6850 @3.88800 GTX7900 GS4 Mb RamWinXP SP2FSX Deluxe SP2CH Controllers

Dang...Avsim is costing me a fortune...gotta quit reading these forums.This MD-80 thread is a perfect example...oh, and the news item on the first page, almost forgot.If I hadn't read these, I wouldn't have just shelled out $50+ on yet another addon.Of course, I would have missed out on another spectacular simulated airplane...very, very nice. Very frame rate friendly, as has been pointed out.I've spent a bit of time up front in MD-80's, and the sounds from the Super80 Pro bring back memories. The boundary layer noise is an example...sounds like the real thing. Nice touch. Hmmm, maybe reading Avsim is not so bad. :-)Then again, looks like I've got more manuals to read....I don't know if it's just me, but it seems like there have been a lot of great addons coming out in the last several months, more so than usual. Perhaps that's expected leading up to Christmas. Whatever, I'm always amazed at what folks can put together for *relatively* very little money. I look at a piece of software and think, "How long would it take to put this together?" And my guess is usually many, many hours. Frankly, I can't see how anyone makes any money at it, though it appears that in many cases the passion to build it trumps the 'business case'. For us end users, addons like the this MD-80 seem like such a bargain when one considers what it takes to produce.Thanks for the positive posts on this product...add one more happy customer.Noel WBrisbane

Heck, not only do I fly the MD-11 on short 45 minute flights, for the fun of it I do round robin flights at local airports and touch and goes...the airplane is so much fun to fly. It's a masterpiece of a simulated aircraft. It's like using a sharp knife in the kitchen...just a pleasure to use. "Here Honey, let me slice the tomatoes."I know PMDG has received many accolades for this airplane - but not enough in my book. It's that good. And I would expect all of this magic will be leveraged for the NGX. Noel WBrisbane

BryanI just got through isolating the event and figured I'd give you the evidence...and just read your latest note. You are spot on...and...using the "Disconnect" button restores the ATC window!I noted that it happens when I'm running the "Before Start Flow" (as you noted) - I hear the F.O. say "Beacon On", and then what sounds like someone knocking on the door. I was wondering what that was. From your note I gather that the noise is the connecting of the towbar.In any event, you've solved the mystery and provided a solution so I"m a happy camper.Thank you very much!Noel W

Hi BryanIn answer to your question, no, I don't believe so. The ATC window was OK when I first loaded the flight, but by the time I tried to get my clearance, it was acting up.I'll get more details later when I get home from work. Perhaps I can at least narrow down the behavior. I've initially been suspicious of the window restriction I read about. Almost sounds logical that the last window opening might get locked out. I could be all wet here of course.Thank you for you interest in the matter. I'll have more info soon.Best Regards,Noel W in Brisbane

HiI'm new to the FS2Crew world, but very impressed with this product which is coupled so well with PMDG's outstanding MD-11. I'm using WidevieW with multiple CPU's and monitors.I've noticed that the FSX ATC window, the dialog box one uses to tune and 'talk', sort of disappears after running FS2Crew. I have a joystick button mapped to the"`" key, and normally open and close the dialog box as needed.When I press that button, or the key on the keyboard, the window appears momentarily (just flashes on screen) and then disappears. Holding the button will cause the dialog box to flicker on and off, but it always stays off.I tried remapping to a different key on the keyboard, and it behaves the same way. I have some more testing to do to try to figure this out, but figured I'd pulse you folks in case someone else has seen this.I wonder about the maximum number of windows limit referred to in the documentation...could this be an explanation?Any thoughts?Noel W