icemarkom

It should have been installed with your PMDG 777.

Yeah sorry, I misspoke, I wrote stratosphere, but meant troposphere. Now, my 5" comment comes back from OP: 32000 vs. 37000, which is 5000ft, or close to 5" pressure difference.

I was curious about that after I spent some time plane spotting at the local airport, but other than the cosmetic effect, what would your expectation of that feature in the flight simulator be? I suspect that the only perceived thing would be slightly lower (virtual) fuel burn, and nothing else.

Slow Saturday, indeed! Yeah, that is plausible, and as you said non-linear. Still, that's very close to the expected 1" for 1000ft. However, 32k-35k difference of almost 5" is dramatic. The temperature at that altitude is not a factor, as you are likely already in the stratosphere where there is no temperature lapse rate as on the lower altitudes.

This is to a large extent working as intended. SID and STAR stand for *standard* instrument departure, and *standard* terminal arrival. The key word there being: *standard*. These work perfectly well for controlling the traffic flow and control in the real world, since there are multiple controllers that you interact in a space of a 50-100 nautical miles that SID/STAR often cover. For example of where I fly in Northern California, taking off from San Jose International, going to Las Vegas, you would speak to at least 4 controllers before you reach 1000ft of altitude. By the time you are done with the SID, you are likely to interact with at least 3-4 more (3x NorCal, 1xCenter). Handing off "some weird" procedure between this many controllers, and maintaining steady uninterrupted flow of aircraft is simply not scalable. However, on VATSIM, flying the same route, you may interact with 2 controllers (for example Oakland Center, Los Angeles Center). Those two are handling usually less than a 20 aircraft each. In those circumstances, and to not make the experience *utterly boring* for everyone, controllers usually vector aircraft a little more. So, having that in mind, when you are given the initial clearance, you can always say something along the lines of: "Nxxxx would like to practice flying the filed SID, if able". Or even better put "SID/STAR strongly preferred" in your flight plan. Myself, I usually put "No SID. No STAR" when flying on VATSIM, because the only reason I fly online is because I enjoy the interaction. Otherwise, I may as well fly offline.

That's a good point, but instinctively, 5000' difference still strikes me as significant. In any case, all this is a purely academic musing, as the original problem was fixed :-)

Old topic, but for the difference of almost 5000 ft, the pressure argument probably isn't the most accurate one. That's almost 5" of pressure difference between standard and actual pressure at that altitude. That's very unlikely (impossible?) in the actual atmosphere at that altitude.

My 2c on this topic, as someone who has worked in small companies like PMDG is, and as someone who has (and still is) working for one of the largest and most successful software/service companies in the world. Interestingly enough, there are striking similarities between the two. Users are everything. They take note of how they are treated, and make choices based on that, more often than a mere quality of the product. The decision to purchase A or B, often comes down to how the user has been treated in the past, if the business relationship existed. When evaluating a purchase that may require ongoing support, users will very often evaluate not only the product, but the perceived interaction of their future business partner with their users. Rudeness never goes a long way in the face of competition. That said, there are valid user concerns, and there are essentially invalid ones. This whole thread I find a little disappointing from both sides: as a paying PMDG customer, but also as someone who sells their "brain product". As a PMDG customer, the arrogance displayed by some PMDG representatives is quite frankly infuriating, and disheartening. It's as if the users' existence is merely for their amusement, and not survival. In the long run, this tends to destroy even the strongest players on the market when faced with competition. This has nothing to do with the quality of their product, or the support privately provided via the tickets, rather their public communication style. From the other side, the complaints about the *unknown* future price of a potential significant, or insignificant upgrade are, quite frankly, ridiculous. The price will be what PMDG deems necessary to support their future business growth. They may deem that to be $0, or $1,000. When they set the price, we, the users, will respond with our wallets. We may be happy, or unhappy. I am pretty sure that at this point in time, I have *no data* to evaluate whether I will care about future P3D, or PMDG paid update. When I made the conscientious transition from FSX to P3D for my personal simulation needs, my understanding was that anything I purchased on FSX will probably *not* work on the new platform, and I made a willing decision to transition, because I saw merit in doing so. When a new P3D comes out, and requires a similar upgrade cost, I will make my evaluation at that point, because I believe that only at that point I will have enough data to perform a thoughtful cost-benefit analysis. Now forgive me while I go and make an impulse buy of NGX 600-700 expansion for P3D, because I actually quite like PMDG's products, and am an avid supporter of wallet-voting to ensure continued support and development.

If you want a challenging and fun approach next, try doing one to BIIS :-).

Also keep in mind that there are displaced thresholds, and displaced thresholds. Some cannot be used even for takeoffs. In the FAA world, large yellow chevrons mean don't; white arrows on the centerline mean it's ok :-)

Indeed, I *believe* it was the IF that was missing as a transition (which is perfectly fine to do). I can't recall the actual approach, but will take a look. Regarding the PT, I believe you repeated pretty much all I said, I was just curious whether this is something we can expect to see once, and if, the update arrives. Using modes other than VNAV/LNAV is fine, but it's also fine to have those two. I like to have the automation available to help in all its glory.

It has been a while since I posted here and about the same since I last spent some time with wonderful PMDG 737, but recently I started enjoying it again, so please forgive me if I'm asking something already answered, but my quick search for past topics did not fully answer all my questions on this topic. These are really two questions. A few days ago I was flying on the route that ended with the ILS approach that required a procedure turn. I figured out during the flight that the PT was not programmed, and just used the HDG/VS to fly it, and it actually worked fine. It's my understanding that PMDG did not implement this in their code, but there is the proverbial SP2 coming up at some point in the future. Is this something that's perhaps on the list of deliverables? I totally understand that chances of an airline flying this in a controlled space are slim to none, but nevertheless... ATC could be on strike ;-) Another question is only somewhat related. I'm sad to say that I don't *quite* remember what approach this was, but I noticed a little discrepancy between the chart (latest FAA 2016-07-21 print) and FMC that for a particular approach not all IAF/IF were available in FMC. I.e. I didn't have an option to fly the approach as I would've selected to fly it. Is this the Navigraph (which I also have the latest cycle), or some other issue? Thanks a lot for reading through.

What's the outside temperature? If you are using VATSIM's FSINN, disable weather - it's known to cause incorrect temperatures at high altitudes.

That usually means that VNAV can't complete the programmed path and that you need to employ other modes to descend. Also, crosscheck the charts and the FMC as sometimes there is error in the data that you can easily correct.

Well, if that's the case, fire him and get one who can fix the issue :-) Joking aside - screenshot of the AC panel would help.