Jump to content

Recommended Posts

Posted

Hello,

When Resume from Autosave and having FD on AP on the AP does not hold the assigned altitude only when switched to VS +0000.

LG-48GQ900-B 48"
AMD 9900X3D
ASUS TUF Gaming X870-PLUS Wi-Fi AMD AM5
AORUS GeForce RTX™ 5080 XTREME WATERFORCE
CORSAIR Vengeance DDR5 6000MHz CL30 AMD(2 x 32GB)
2X 2TB 970 EVO Gen 4 (FS 2024)
1X 1 TB 990 EVO Gen 5 (WIN 11)
3TB SSD (MOVIES/APP)
Marantz HD-DAC1
Beyerdynamic T1 Tesla (2nd Gen)
Thrustmeter TCA Captains Pack
Thrustmeter TFRP Rudder
MiniCockpit (miniFCU V2 + miniEFIS)
WinWing MCDU
FS2024 (FGX4) (120* FPS on ULTRA @4K) *locked

Posted

I just experienced this same issue, I loaded in from an autosave. Attempted a step climb from FL380 - FL400. The aircraft climbed through and descended through FL400 without capturing ALT CRZ.

Screenshot (43).jpg

autosaves.zip

  • 1 month later...
Posted

I have had this issue, and it seems like there is a temporary solution that will only reappear on the descent. I kept retrying the autosave until my MCP showed 3 dashes in the MACH, HDG and VS windows. I spawned slightly over- or under my CRZ ALT; however, the AP did capture the CRZ ALT. This was only temporary, however, as the AP would not capture any other altitudes once I left CRZ ALT, meaning that stepclimbs and descending/maintaining an altitude would not work. In addition, the autothrottle would not maintain the proper VAPP speed on approach, and I would end up either stalling or going into TOGA.LK fma mode. Please, if anyone can find a fix for this, let me know, as this issue pretty much defeats the purpose of the autosave feature.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...