Flightsim Phil

When you are on the Doors page of the FMC, hit the "Next Page" button. The cargo doors are on Page 2....Phil

I don't use the iFly 737, so please don't start with the flaming responses, but I noticed this online and I must admit I thought it was pretty cool.....http://www.flight1.com/products.asp?product=FL1-IFE-001A special edition of the software geared for home cockpit builders.... I suspect that once the SDK comes out for the PMDG NGX, there will be alot more hardware compatibilty, but I would love to see PMDG do something like this too... I think the 737 is the most popular choice for home cockpit builders and I believe that PMDG's product is the premier version for the FSX. From what I saw, the iFly "Pro" edition makes it really easy to set up multiple windows on networked computers and to interface with most of the popular hardware options (VRInsight, Engravity, etc...).Food for thought PMDG....Phil

PMDG swag!!! Bring it on!! That is an excellent suggestion.....I know alot of companies use Cafepress for this kinda stuff....Put me down for a t-shirt and a coffee mug!!!Phil

If you can build me a Flightdeck Solutions overhead panel that will work with the NGX for less than the cost of the VR Insight unit, I will wire you the money this afternoon!!!Phil

Has anybody seen this yet???http://www.simw.com/hardware/v737-overhead.htmlLooks awesome!!! Could be the belated Christmas present I need to buy myself! Need that SDK though PMDG!! Let's hope the lawyers work this out soon....Phil

I guess I'm a little late to the party here, but thanks again to Robert for an excellent, well written, and totally depressing assessment of what we all feared would be the case with MS Flight. Makes sense given the reasons they dropped Flightsim from further development a few years ago. Business is business and they make tons of $$ from console games..... While I anxiously await the arrival of the PMDG 777, its pains me to know that we are really pushing the limits of what is possible given the software limitations of FSX..... Maybe the entire add-on software community will ultimately choose to port their products to something else, whether it's XPlane or something similar so that we can finally take advantage of the numerous hardware upgrades in CPU's and video cards that are available today.Phil

+1

I have no interest in debating the validity of my "claims" since I don't think that is what this venue is for. While I agree with you that personal attacks are easy (and often enjoyable), the point I was hoping to make was that, as stated previously in this thread, anyone with a bad word or a word in anger about PMDG seems to be labelled a "whiner". I bought the product, I use it and I enjoy it. I agree with you... the SDK will come out eventually once it's out of legal limbo. Enough said....Phil"The first thing we do, let's kill all the lawyers." -William ShakespeareHenry VI (Part 2) - Act IV Scene II

Trevor:The posts in this forum which promised what I have referenced are long since gone.... since this isn't a "legal level" conversation (sorry, no fees on this one counselor) I wasn't planning on having to provide exhibits. That said, we know what was promised. That's why the ######ing and moaning exists. People are asking for what was promised, not simply making things up for no good reason. Can't you just feel the love in this forum???? :)Phil

Excellent response.....As many people as there are that are upset over the "SDK" issue, there are as many if not more &@($*-kissing sycophants. As a response to the gentlemen above who indicated that PMDG's only responsibility was to deliver the NGX, I think you need to re-take the bar exam. PMDG stated many times in many pre-release items that the NGX would specifically allow third party developers and home cockpit builders to make use of this package and that it would intereface with most "popular" hardware out today. That requires the release of an SDK. I don't want to get into a debate about how many purchasers that may be an issue for.... the point is that it was promised as part of the purchase many times.I do believe the SDK will be released. I'm not pleased with the wait but I know it's in PMDG's best interest to get it out there.... it would only serve to increase sales for them.My problem is with the lack of communication. How about an New Years update from Robert?Phil

I think that's a very valid point.... I suspect there may in fact be a number of people who have put off purchasing the NGX until the SDK is out and there are drivers available for the various hardware configurations that they may have or software that they wish to use in conjunction with the NGX. I do believe it is in PMDG's interest to release the SDK as that certainly would create an opportunity for additional sales. I do find it odd that it has taken this long.... I don't recall this being an issue with other PMDG products.What was it again that Shakespeare said about lawyers??? I don't recall that it was very complimentary...Phil

Paul:Do you mind letting us know exactly where you took the sim ride?? I travel down to southern Florida quite a bit on business and might be interested in taking a Level D ride one of these trips!!Thanks,Phil

"This weekend I will update this post with a list of items that we have currently corrected in SP1. It is around 150+ specific items and another 50 or so that are non-specific fixes. (I'll explain what I mean by that in the update.)" Did I miss that or are we still waiting on that?? Phil

Tick..... tick..... tick..... tick....... Anyone? Anyone? Bueller? Bueller? Anyone?

This question is not necessarily specific to the NGX...... I typically use FSBuild or Fltplan.com to plan flights and I fly almost exclusively in the continental US. The approach to many US airports (MCO, DFW, ATL etc...) have variations such as crossing restrictions, speed, etc. depending on which runway you are landing on (e.g. north vs. south landing). My experience with FSX is that I typically pick up the ATIS anywhere from 60-80 miles from the airport. This distance is way too close to program the correct approach procedure into the FMC. Many times I end up with the message "DESCENT PATH UNABLE" because I am way too high for the approach once I enter the runway in use based on the ATIS. In the real world pilots know which runway to expect hundreds of miles out (unless winds change at the last minute) so it is easy for them to program the approach and ILS in advance and have no VNAV or descent-related issues. Any suggestions/advice would be appreciated. I'm tired of having to enter a holding pattern in order to reduce altitude on approach.... Phil