Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Problem with Transition Alt.

Featured Replies

Hi,

 

I Set manually the standart TA to 5000ft, but there is still the 18000ft TA at the Desc. Forcast page and at the CLB page.

Have the same Problem with the NGX.

 

So if anyone could help to solve this i would appreciate.

(sry for bad english ;) )

 

Dennis Wüstefeld

There are two TAs actually, your destination TA is set on the DESCENT FORECAST page. As mentioned in the introduction, you may also change the default 18000 in the PMDG OPTIONS menu.

Dan Downs KCRP

  • Author

There are two TAs actually, your destination TA is set on the DESCENT FORECAST page. As mentioned in the introduction, you may also change the default 18000 in the PMDG OPTIONS menu.

 

Of course. But 18000ft still remains.

Dennis Wüstefeld

I am probably not understanding the problem.

Dan Downs KCRP

  • Author

Maybe this helps.

 

h7fcg6k7.jpg

Dennis Wüstefeld

Hi,

 

I Set manually the standart TA to 5000ft, but there is still the 18000ft TA at the Desc. Forcast page and at the CLB page.

Have the same Problem with the NGX.

 

So if anyone could help to solve this i would appreciate.

(sry for bad english ;) )

I was just reading through the manual....it is a bit confusing.

But you can change those values (as I think you have tried) under equipment options page 3/9

 

Now the important thing is (if I understand correctly) that these values are stored only for your current panel state (if you save "panel state") or current flight (if you save the flight).

So if you save TA to 5000ft and then next time you fly you choose another 777 livery....then it will be at 18000ft again.

Because that is what the panel state of that livery looks like.

 

If you select your changed and saved panel state....then you should have 5000 again though....I think.

Rob Robson

Rob is right. It's the difference between tail number specific options and panel state options. However, it is a bug if you cannot ever make the TA change to 5000 and to ensure it gets fixed we would appreciate a detail description of each step down to the keystroke to allow the problem to be reproduced. Thanks.

Dan Downs KCRP

Rob is right. It's the difference between tail number specific options and panel state options. However, it is a bug if you cannot ever make the TA change to 5000 and to ensure it gets fixed we would appreciate a detail description of each step down to the keystroke to allow the problem to be reproduced. Thanks.

I think he is doing something wrong cause he had the problem on the 737 as well

Rob Robson

Just tried it and it worked as expected.

 

Here's what I did.

1) Changed default TA to 10,000 - Was originally set at 18,000 for Delta livery.

2) Restarted FSX - The TA option isn't a change on the fly option like some of the other ones, you need to restart FSX for it to save properly. Are you possibly skipping this step?

3) Took the picture below. 10,000 on the VNAV CLB page.

 

 

 

image.jpg

Chaos81, I think the OP may be flying outside the US, where transition altitudes are different at different places and not set to FL180 as in the FAA world. For those situations, these can be set for individual flights and are not PMDG-specific.

 

I have never had the problem with this, even though vast majority of my flights are US-based, so I don;'t have to worry about this.

 

Could you provide detailed step-by-step procedure of how you're setting the trans altitude and the flight level, so we could try to reproduce it in our planes? Thanks!

Marko Milivojević

  • Author

Just tried it and it worked as expected.

 

Here's what I did.

1) Changed default TA to 10,000 - Was originally set at 18,000 for Delta livery.

2) Restarted FSX - The TA option isn't a change on the fly option like some of the other ones, you need to restart FSX for it to save properly. Are you possibly skipping this step?

3) Took the picture below. 10,000 on the VNAV CLB page.

 

Didnt work. Possible its a problem with my Software Settings outside FSX.

 

Installed the 777x and NGX again, Problem still exists.

Removed Liverys and installed agian, Problem still exists.

 

I loaded the AeroLogic Livery. The Aircraft Specific Settings contains the default TA 5000ft but you see in my posted Picture above the VNAV TA is still 18000ft.

I Saved the "Panel State Short" where i have changed manually the Forcast and CLB TA. That works....

Dennis Wüstefeld

Didnt work. Possible its a problem with my Software Settings outside FSX.

 

Installed the 777x and NGX again, Problem still exists.

Removed Liverys and installed agian, Problem still exists.

 

I loaded the AeroLogic Livery. The Aircraft Specific Settings contains the default TA 5000ft but you see in my posted Picture above the VNAV TA is still 18000ft.

I Saved the "Panel State Short" where i have changed manually the Forcast and CLB TA. That works....

 

Are you restarting FSX after making the change? or reload a panel state?

Bryan Richards

 

"People depend so much on automation that they forget how to get the automation to work." B.W.

  • Author

Are you restarting FSX after making the change? or reload a panel state?

 

 

The Question is, why is the TA 18000ft although in the downloaded Aircraft Settings the TA is 5000ft?

Dennis Wüstefeld

The Question is, why is the TA 18000ft although in the downloaded Aircraft Settings the TA is 5000ft?

 

I think the answer to this is as Rob and Dan described above. This gets saved with the panel state, and from what you posted, it seems like you were loading the PMDG short turn panel state, which had 18K set as the TA when saved. The reason it worked for me, is because I didn't load a panel state, I was doing it straight from the default engines running.

 

This seems to be proper behavior going off what the intro manual states, but it's possible I've completely misunderstood things.

 

Page 72:

 

 

It’s important to understand that these values will be overridden by what’s saved in a panel state or saved flight due to the way the FMC is initialized. If you wish to have these values in a panel state, load the panel state first, adjust the values, then save the state with a new name such as “(livery name)_CLDDRK” or whatever you’d like.

It doesnt change real time, you probably have to power down the aircraft completely (i.e. cold and dark state) thereby "resetting" the FMC or reload a new panel state for it to take effect, 

Bryan Richards

 

"People depend so much on automation that they forget how to get the automation to work." B.W.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.