Sartanius

Recently retired from Lockheed Martin after 35 years in the aircraft sustainment business. For much of my career I managed the Customer Training business area where we developed and delivered world class training systems (including training facilities, Level-D full flight simulators, maintenance training devices and courseware) for all of our C-130 Hercules customers, both domestic and international. Was an amazing career.

Great words, Paul. I agree wholeheartedly!

Just a quick comment, Steve. You ultimately want an odd number of monitors for a 180* cockpit view so that the forward pilot's view will not be disturbed by monitor bezels. With 4 monitors, and assuming they were arranged with the normal forward pilot view stretched across the middle two monitors, I don't believe you'd be pleased with the monitor bezels dividing the view. Just a thought for your consideration.

Jordan - Just a word of caution here. Stretching the view across two monitors puts the two adjacent monitor bezels right in the center of your forward pilot view, which may not be the most pleasant experience. Stretching across three monitors gives a better visual experience since the center monitor in that case is your standard forward view with no obstructing bezels. I use two 27" monitors with my flight sim on the one (Prepar3d v3.3.5 in my case) and the second for charts, AS16, Avsim, etc. I will be going to three monitors after I retire in August.

Not scientific, but you might consider a larger PSU in the event you want to add a second GeForce card for SLI down the road. You'd have to do the math to see what might be necessary. Just a thought off the top off my head.

+1

Hands down, ASN. And it works like a charm with the PMDG 737NGX and B777 weather radar displays. Truly impressive.

I'll throw in my $0.02 as well. Upgraded a system with FSX Gold, FSX-SE, and P3Dv2x and everything worked just fine afterwards. As Doug says above, one cannot be 100% sure, so make that system back-up first. I did, and fortunately didn't need it. Have fun!

Stefan, I assume you know about the "Logbook" that is already part of P3D which tracks Date, Aircraft Type, Registration Number, Origin, Destination, Category, Multi-Engine (y/n), Total Time, Night Time, Instrument Time, Number of Landings, and Remarks. Since the built-in P3D Logbook interface is sluggish and unwieldy, there is an excellent utility developed by our own Dan Downs here at Avsim and available for free in the Avsim Library. It is named "LogEditv2-0" and it makes using the P3D logbook much, much easier. Check it out.

Ok, done deal. Trip booked to DFW with a stay at the airport Hyatt. Thanks for the responses.

I didn't mention this, but I live in the Atlanta area, so will be flying out of KATL. I'll check into the KIAH suggestion, though. Thanks, Glenn.

Thanks for the excellent suggestion, @cmpbellsjc. I'll check that out.

I need to bump up my frequent flyer miles balance so I can have enough for two tickets later this fall. Thinking of taking a short, inexpensive round-trip flight to an airport in the SE or South Central USA where there's an onsite hotel affording excellent aircraft spotting access. I will need to take this short trip in April so the few extra miles I need can be credited to my account in time to secure frequent flyer tickets for my wife and I to the west coast in the mid-fall time frame. Thanks in advance for any suggestions you might have.

Angelo, Here's the one I use (link). Fits nicely on a single, double-sided page.

I have searched all over Pete's forum and can't locate the elusive "i" version. The normal download location still has the "h" version. Can someone please post a link to the "i" download? Update: Never mind... found it. Didn't see it buried in the text above.

Here's a link. This is a payware application. Suggest you read the documentation since you're not familiar with this very important software for FSX/P3D.

I just used it again and had it eliminate 70% of the traffic at KATL, and it worked as advertised. Good suggestions from David above. Hope you get it sorted.

It works just fine in my setup. What isn't working?

Love your products! Looking forward to this welcomed improvement.

The CAPS-LOCK key trick has worked flawlessly for me, so very grateful to Tom (aka tf51d) for passing it along. Back to GSX fulltime for pushback.

Glad to hear things have recovered for you, Klause. The developer appears to have resumed working on EZDOC and I hope he implements updates that make installation easier and more foolproof.

Klaus - It sounds like you reran the config tool after you had EZDOC running well in post #5, but maybe I'm inferring that incorrectly from post #6. The config tool only needs to be run once following installation. In any event, suggest you completely uninstall EZDOC and start over. Remember to disable UAC and turn Windows Defender off in Window 10 before starting (this is critical). After you install v1.15 from the store, do not run the v1.15 config tool. Instead head to the EZDOC forum (here) and download v1.18.7. The update is not installed by running an .exe file, instead you simply replace the older v1.15 files in the main ECZA folder with the new v1.18.7 files. After replacing the files, run the new config tool. After that's done (and wait for the config tool to completely finish), then install the simconnect version supplied with the new EZDOC version you downloaded. You should then be good to go. Once you've verified its working, be sure to go back and re-enable UAC and Windows Defender.

Thanks for that suggestion, Tom. I'll give it a try. Update: I reloaded GSX and gave the Cap-Lock key a try... so far, so good. I'll report back here after I take a couple flights to see if this has done the trick.

I may give ProATC a try, Bob. Thanks again for contributing.

Thanks, Phil. I was aware of that "trick" from reading the forums, but unfortunately it only works some of the time. Hopefully one or the other developer will make the necessary changes to eliminate the conflict. Thanks for that tip, Bob. I'll definitely give it a check after reinstalling GSX. And one additional note based on your comment above, "because this is when it happens" - The issue I experience seems to be connected to use of the FSX/P3D ATC window and/or the GSX window. For example, when taking a high speed taxiway off an active after landing I contact ATC for the gate assignment, and after closing the ATC window, EZDOC has quit working. No matter how many times I then cycle the GSX window or ATC window after that, EZDOC remains failed. Perplexing and frustrating for sure, but I am confident a fix will come along.