I’m new to MSFS2024 and simming. I experience the inability of the CJ4 and BBJ (default aircraft) to follow the GS properly. A/C is properly configured, on speed, captured from below. Things start out normally but eventually progress to full scale GS deviation to the low(er) side. Is there any fix or something I can do (other that manual take over and GA or make a very sloppy salvage job) to fix this? Do similar issues apply to A/C such as the PMDG 737’s? (I have their 777 and it seems to work quite well). Any suggestions or advise is appreciated.
Hi @Abxflyr ,
I have moved out your post from a bug report to its own topic since you are requesting assistance. The User Support Hub > Aircraft & Systems is the appropriate category.
You know, this was never a problem for me in either A/C until just yesterday. In the passenger version of the default 737 the PFD said I captured the glideslope on an ILS approach just fine but the AP kept a static descent rate of 1,000 fpm, nearly running me into the ground before the runway well below the actual glideslope. Might need some more testing to figure out if it’s reproducible then we can maybe doc as a bug. Has it happened to you in either jet more than once? Can you share the ILS approach you were trying so we can try to replicate?
I’ll try a few places late tomorrow and post results. Today is was the KIND ILS 23L (737) and KLEX ILS 22 (CJ4). I have experienced better luck in the recent past, so it may be something new.
I did the “update” by MSFS, don’t think that had anything to do with it. I had same troubles for a bit, decided to look at my bindings and settings (which I have not changed). I use some keyboard bindings for MCP speed, hgd, and altitude. They were previously clean, meaning I had nothing else assigned to them. I use a specific profile modified from generics and (dup/rename). It appears that alot of generic msfs bindings are now in my specific profile. Ends up I think when I was keyboard adjusting heading, I was also rapidly introducing full aileron trim.
A little clean up work later and I performed a 737 autoland, and a CJ4 ILS with no problem (other than sensitivity on elevator that I’m trying to vet out). So I don’t think the system is anymore messed up prior to update. I do not know why my profiles would be changed in many aspects; I’m unfamiliar if I should be keeping some level of backup to their cloudbased stuff. The current solution is to lock the profile(s); they were not previously. Hopefully that will prevent this issue with me.
Please let me know if anyone else continues to experience issue with AP of FD/Hud not following ILS signals.