I just tested both the LD767 and the NGX with the exact same weather conditions from ground to 30,000ft were identical reading TAT.

Charles,

 

The following, while meant to be helpful, is written in my normal manner, which can often be taken different ways.

 

 

 

Previously I complained about performance of not being able to reach cruise altitude using VNAV and it was proclaimed to me that the excessive TAT (+50C and above at altitude) was a bug in FSX and could not be resolved.

 

This is because this is the truth (though, really with the FSX weather engine itself.)

 

 

 

... see graphic below:
 
https://www.dropbox....emRevisited.jpg

 

There's a problem with the scientific method here.  In order to be proven conclusive, you'd need to have the NGX and its TAT shown in the same weather.  So, yes, it's great to see Level D's just fine, but I can't see the evidence that the NGX is not.  This is particularly because mine did just fine all weekend (and with TAT at +50, there's no way I would've made it to these altitudes):

http://vataware.com/flight.cfm?id=12044837

http://vataware.com/flight.cfm?id=12047392

The above were using ASE in DWC.

 

 

 

Also, I'm flying the REX weather. 

 

This could be the problem.  Moreover, if you're flying online with FSInn, that is most likely the issue.

 

Try without weather entirely, just for one flight in the NGX, to see if you get the same result.

 

 

 

For the amount of money I'm spending with this company (737NGX, J41, 747 and soon to be released 777) I expect this problem to be resolved.

 

In order for it to be resolved, it would have to be a problem with the aircraft.  Remember, the aircraft isn't driving the weather settings; it merely reads the weather around it.  If the sim is being fed bad temperature data, and the aircraft is simply observing this, it's not really the problem of the developer of the aircraft - PMDG or otherwise.

 

I know this must be frustrating, and I see you've at least put in a little troubleshooting here, but keep in mind that it is always best to put across a neutral stance when troubleshooting.  This is particularly the case if requesting the help of others.  Placing blame on the developer sets the expectation that it's wholly their fault, when in reality it is more often the end user.  In the end, if it ends up being a user or software interaction issue, then it just makes the one placing blame in the wrong spot look a little foolish.

 

...and let's be honest:

That's my job  :wink:

If Charles claims the issue does not exist with other addons could it not be that his NGX install is corrupt in some way?

 

Also, if (like the fsinn bug) the weather program is the issue, perhaps a screenshot of the reported SAT by Rex and the reported SAT from the NG could help to see where the problem is?

 

Just a suggestion.

Honestly guys ... I too worship at the alter of the Gods that are PMDG ... but I'm coming from a unique position of installing the exact same software on three different rigs ... my original Duo Core 8400 Wolfdale at 3.0GHz, my i7 4700MQ at 2.4GHz software development laptop and my new rig ... an i7 4770K at 4.2 GHz ... and I experience that same problems throughout ... with and without weather. 

 

The last thing I want to hear is an allusion to my inattention to scientific detail ... no disrespect intended Mr. Rodgers.

 

C. T.

 

 

The last thing I want to hear is an allusion to my inattention to scientific detail ... no disrespect intended Mr. Rodgers.

 

If i may, i don't think that he was implying a lack of attention to detail, just that you use the scientific method to resolve the issue.

 

Personally i have experienced this in the MD11 but not once in the NGX or J41.  I have never seen this in the Aerosoft Airbus, Majestic Q400 or the Aerosoft Twotter...the only other non-PMDG aircraft i fly.

 

Using AS2012, i was under the impression that selecting Direct mode (at least in part) resolved this issue.

 

However, the approach given by Kyle above is correct and many other people have reported this issue.

 

 

The last thing I want to hear is an allusion to my inattention to scientific detail ... no disrespect intended Mr. Rodgers.

 

 

That's understandable.  I get it, but if you think about it, troubleshooting and pinning the actual issue down to a specific source is exactly that: scientific.  And I really didn't mean you lack an attention to detail.  Your lights thread from a few months back would prove that you have an attention to detail above most.

 

I'm very sure that you could easily pin it down on whatever seems obvious if you didn't look too scientifically at the problem.  If you're actually looking to solve the problem - which, as you mentioned earlier, no offense meant - then you have to acknowledge that this problem is not present on our machines.  As such, there's an existent data trend suggesting that it is not an issue of PMDG, rather an issue either on your machine, or with the programs you're using in combination with the NGX.

 

Again, I'm not trying to sideline the issue with a discussion on your scientific method except to point out that there's nothing that proves its not an issue on your own machine.  Again, in troubleshooting, it's more often that the issue is resolved by the user by a change on his or her own machine.

 

As an example, a few weeks ago I ran into an issue where the NGX suddenly decided not to initialize.  Up until that point, I could load the NGX right off of the Create a Flight screen (default flight being the MS Default.)  I now have to load the Cessna into a flight, and then change aircraft to the NGX.  So, clearly it worked before, and then randomly stopped.  100% of the time this happens with the NGX, while 0% of the time does it happen with my Carenado aircraft.  That doesn't necessarily mean it's not a problem with my own machine/setup, however.

 

So, if we're to help you pin this down, we have to eliminate this methodically, and scientifically.  So far, 6 of the lab rats in here have made it through the maze without sweating.

 

Several have mentioned taking a stab at a no-weather scenario, but in none of your posts have I seen the results of that suggestion.  It's a valid suggestion given the evidence at hand.  It would greatly assist us in helping you solve the problem.

i've had this problem in the concorde where AS2012 decided not to input the right temperatures in at high alt. Restarting AS2012 fixed it, the only other time i had problems with it was when i was silly enough to use FSINN weather

Hi Charles,

 

For a test I would cut back to minimum and no tweaks. Try a default FSX cfg, set up a minimal dll.xml and exe.xml. It could be resources run out and this blows a hole In the weather landscape somehow, and then there are lots of ways weather addons can do it by accident, try stock FSX themes.

 

Regards

Steve

Only problem I have seen like this is when using FSInn. In that case you need to shut off it's weather. There are threads about it in the VATSIM forum(when it comes back up). Otherwise I can tell you no issue on my end using AS2012.

If using fsinn, disable weather

 

 

In order for it to be resolved, it would have to be a problem with the aircraft. Remember, the aircraft isn't driving the weather settings; it merely reads the weather around it. If the sim is being fed bad temperature data, and the aircraft is simply observing this, it's not really the problem of the developer of the aircraft - PMDG or otherwise.



I know this must be frustrating, and I see you've at least put in a little troubleshooting here, but keep in mind that it is always best to put across a neutral stance when troubleshooting. This is particularly the case if requesting the help of others. Placing blame on the developer sets the expectation that it's wholly their fault, when in reality it is more often the end user. In the end, if it ends up being a user or software interaction issue, then it just makes the one placing blame in the wrong spot look a little foolish.

 

 

Well that about sums it up. If using a weather engine, placing blame entirely on the developer (in this case PMDG), does not exactly help your cause in receiving support. Kyle was actually a little more polite than I expected (no offense, Kyle haha. Must've had a good day haha) when he said "placing blame in the wrong spot looks a little foolish".

I have flown the 737ngx over 2000 hours.  Use Active sky for weather.  I have never seen 50 deg TAT..  the TAT is usually negative at altitude.

Good luck.

Cheers,

Don Emerson

N570TT.

This is not something we could cause even if we wanted to. We read these types of values straight out of FSX via SimConnect - the airplane cannot write weather values to the sim in any way, shape or form. TAT is a really basic thing, it's not some complicated calculation/function there could be a bug in. Our engines are directly responding to the environment too - if the thrust is maxed and the plane can't climb, that's because of a real (in the sim at least) environmental issue affecting them - not because a temperature number is displayed on the DU. If it were a calculation/display problem on our end then the number would display wrong but the plane would still fly correctly because the actual environment outside the aircraft would be correct. It's the same idea as the S-turn/turbulence stuff that can happen too - people sometimes say we should "just filter it out" or "don't have the plane respond to it", but those are real forces hitting and affecting the airplane - you can't just "filter out" what the actual sim environment is doing to the airplane any more than you could "filter out" windshear and turbulence in a real life airplane.

 

As I said in the earlier thread about this, we went over this with the Opus developers a few months back when I started seeing it with their program. They showed me conclusively how when this happens the app is commanding a certain temp but FSX just goes nuts and starts generating bogus values that are way higher. Any station based weather app including REX, AS2012's station mode, FS Global etc and so on will do this. The only thing that will stop the problem if you're getting it constantly is using a weather addon that can do global writes like AS2012 in DWC mode does. I saw this multiple times - I'd get the super high temp in Opus (which uses the station weather mode) and then go load AS2012 in DWC without doing anything else - the problem would instantly clear up, the TAT would be back to normal and I could climb again. The fact that I can do that without touching a single thing in the airplane means the source of the problem has to be external to us.

 

 

Kyle was actually a little more polite than I expected (no offense, Kyle haha. Must've had a good day haha)

 

Haha - no offense taken.  Given my normal demeanor, I'm right there with ya.

 

This was my yesterday, so that might have had something to do with it:

Cool pic Kyle, where is that?

 

Here is my today

 

 

Here in Norway it has been around 27-30c degrees during the last weeks, so finally my boat get to earn its keep. Rare event for us Scandahoovians, as I am sure you know from when you were here.

 

Cheers,