Hallo Liebes Forum,   leider bin ich gerade total verunsichert, da simheaven X-World manchmal komisch aussieht. meine reihenfolge von simheaven ist doch richtig oder muss die simHeaven_X-World_Vegetation_Library am ende von Xworld kommt, also ganz unten?   so ist doch eigentlich richtig oder: CENERY_PACK Custom Scenery/simHeaven_X-World_Europe-1-vfr/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-2-regions/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-3-details/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-4-extras/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-5-footprints/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-6-scenery/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-7-forests/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Europe-8-network/ SCENERY_PACK Custom Scenery/simHeaven_X-World_Vegetation_Library/          <--- ist doch richtig oder? RY_PACK D:\base folder\XPME_Europe/   danke an alle

The TOD is now showing in the MFD like it should on the upper right side of the screen.

Please login to display this image.

  I know the TOD is being calculated correctly as it's indeed shown in the MFD Data page:

Please login to display this image.

    Anyone know how to get the VNAV profile shown in the MFD (it's selected in the MFD menu)?

das steht im Forum von "flightsimulator.com", 

Please login to display this image.

+ neue NavData am 10.07.25 für beide Simulatoren veröffentlicht: https://forums.flightsimulator.com/t/airac-cycle-update-2507-msfs-2020-2024/729220?u=nadine19759630   Jetzt verstehe ich das Ganze nicht mehr, sorry. 

I'm turning the knob for both cockpit and cabin temps but they are set at 22 and won't move. Which switch do I need to flip to take manual control? My cockpit is best at 19c. 

In my FMS I selected just a runway for my approach and the FMS added it into my route but assigned an altitude of FL350 instead of the actual airport elevation. This causes an issue when I remove the discontinuity above it because it jacks up all the automatically assigned altitudes.    Here are the previous waypoints with correct altitudes followed by discontinuity followed by runway 13 with incorrect elevation:

Please login to display this image.

    When I remove the discontinuity, it turns all waypoint altitudes to FL350. How can I have the FMS properly assign my final runway waypoint with the correct altitude?