Exactly, and I have no idea what it causes. It also climbed with 6500-7500fpm and I don't think that is correct either?

I don't know what your weight is, so that one's debatable. If you're very light and you're doing a full-thrust take-off and climb, you might very well be able to climb at those rates.

Looks like your TAT is +29C. Don't know if you're still flying, but what happens if you try clearing all weather?

Hans!

 

Do I see +23 or +29 (2nd pic) TAT at FL380? I also note that your GS and IAS is the same. Should not be.

Something in your WX is screwing your flight up.

 

Hope it helps,

Flying lightweight should give me a better fuel consumption though.

Where are you flying and which WX program are you using? In the Middle East I encounted many temperature issues in the NGX caused by Active Sky. A simple restart of AS2012 fixed that issue. Yet to see it in the 777 though and also since switching to Direct Weather Control mode.

 

Which panel state did you use if any also?

Just cleared all weather but nothing changed. Everything stays the same.

 

 

Crappy photos I made attached.

 

You do know that if you press the 'V' key, it automatically creates a screenshot in BMP format, right?

Just cleared all weather but nothing changed. Everything stays the same.

 

Then I hate to say it, but there's a problem with your sim.

I followed the tutorial, disabled weather in OpusFSX, no other WX apps. Location is just left Male, Maledives enroute to Dubai. Just closed OpusFSX completely and loaded the clear skies preset in FSX. Still the same.

You do know that if you press the 'V' key, it automatically creates a screenshot in BMP format, right?

 

 

Then I hate to say it, but there's a problem with your sim.

I know that, but I think I was too lazy to convert them to jpg.

 

I don't like that last sentence, worked perfectly with the NGX

 

 

I don't like that last sentence, worked perfectly with the NGX

 

Well, like it or not, the 777 doesn't "create" temperatures like that, so it must be coming from your sim.  As such, it's a problem with your sim and not with the plane.  The plane only reads the temps the sim gives to it.

 

Fact.

 

Whether you like that fact or you don't has no bearing on the fact that there's a problem with your sim (or some program you're running with the sim).

I'm sorry for the late reply, had to sleep as well  ^_^

 

The weird fact is that I do not have this issue in the same simulator with the 737NGX. I do believe you when you say that the plane gets this data directly from the simulator, but then I wonder why it doesn't happen with the 777.

 

Gotta give it a try again tonight, maybe with a reinstall of the 777 first. Will keep you posted.

 

 

Gotta give it a try again tonight, maybe with a reinstall of the 777 first.

 

That should be a last resort.  At all times.  I hate that this forum is so quick to put that out as an option.  With a sim as complicated as this, it can cause more issues than you're trying to solve.

 

Screenshots of your FMS setup would be very helpful.  Please also show the EICAS in these shots.

 

...only after troubleshooting should you try a reinstall, and if you do that, make sure you use the steps outlined on the PMDG Support site.

I don't know if you have solved your problem yet, but check your realism settings. There is an option there to show TAS instead of IAS on the airspeed indicator. Check and see if you have that option on.

 

 

EDIT: I see that you don't have that problem in 737, so that might not be the solution then.

The high TAT is the problem. It explains the low mach and I am surprised he got that high with that warm air. I don't use it but isn't this a problem with FSINN? Basically, if you have 100-deg F TAT at fl380 it's not a simulator anymore.

 

 

Basically, if you have 100-deg F TAT at fl380 it's not a simulator anymore.

 

Well, not an earth-based simulator. Venus maybe.

 

 

 

That should be a last resort.  At all times.  I hate that this forum is so quick to put that out as an option.  With a sim as complicated as this, it can cause more issues than you're trying to solve.
 
Screenshots of your FMS setup would be very helpful.  Please also show the EICAS in these shots.
 
...only after troubleshooting should you try a reinstall, and if you do that, make sure you use the steps outlined on the PMDG Support site.

 

Holy crap, thank you. It seems that there's this massive trend of people finding something "odd" (sometimes not even wrong) that they didn't expect in a T7 and immediately doing a re-installation. And I have a hard time believing that every person is performing a full and complete (read: proper) re-installation, whether or not its on accident or due to impatience and a "I want it fixed NOW" mentality.  

 

 

Holy crap, thank you. It seems that there's this massive trend of people finding something "odd" (sometimes not even wrong) that they didn't expect in a T7 and immediately doing a re-installation. And I have a hard time believing that every person is performing a full and complete (read: proper) re-installation, whether or not its on accident or due to impatience and a "I want it fixed NOW" mentality.  

 

haha - you're welcome!

 

I think most of my issue is that people immediately blame the computer or the code, when in my experience, it's the human element to blame.