Leaderboard

Hi all, changes have been made to the beta build to eliminate this behaviour. This will be included in the next release.

I'm having difficulty getting the ILS to acquire the G/S or Loc with APP mode. I've tried many times and cannot get this to operate as I would expect. I have attached a video. I must be doing something wrong, but I cannot identify what that could be. This happens at multiple airports. I have the correct ILS frequency, I'm established under the glide slope altitude and approach heading at the point I should join and thereafter. I have the correct course set, A/T, CMD A, FMC is set up for the flight situation, I'm close to Vref. So don't know what else to do. The video is pretty short given the file size, so this show a brief segment but you can get the general idea. I was established much sooner than this of course. 1122069429_X-Plane2022_04.03-11_19_01_10.mp4

Thank you. If they can come up with the reason why it happens only with my sim, I could try to fix it before the next update.

Thanks! Rich

Hello, I spent forty minutes testing this extensively with 1.5.2 and ran into no issues. Tests were: Failure, no CAS message, HDG to NAV Failure, no CAS message, NAV to HDG to NAV Failure, CAS message, HDG to NAV Failure, CAS message, NAV to HDG to NAV All of the above with new directs Engine failure, HDG to NAV, HDG to APPR Looking at your log it's definitely the Challenger crashing but it's just the same as last time. I will refer this back to the developer.

Yes. I was having this issue on regular flights when AP was engaged the whole time, and engaging APP as I intercepted the ILS at what I believe was a valid altitude. I'm going to go back and do the arrival segments to intercept the ILS and see how those do. I was having a lot of issues with those, which is why I switched to using the map function and shorter approach - just to save time. Now that I can pretty regularly get APP going I'm going back to the arrival phase and see what gives.

BTW I was using the XP Map function you told me about to do some of the testing so that I could do it repeatedly. I believe that when xp pause goes off after setting up the map flight parameters if the actual aircraft flight status/configuration doesn't match up in some ways, this problem is likely to occur.

I did a new install of XP and the 737. I still had similar problems. I discovered that if I engaged the APP mode too early sometimes the G/S would never lock on, and less frequently the VOR LOC wouldn't lock on. That only took 100 tries to figure out over the last two weeks. It works the same way on the old install. So the AP is very particular about the circumstances in which it will engage, and when the APP mode works.

Hello everyone. I am just posting here to say that I have a similar problem getting random stutters (I will check the log to see if this happens when dsf loading.) Most probably that's the cause. Usually I have 60-70 fps on a non populated area and 40-50 on populated like TE GB and some other addons. Randomly fps drops to 5-15 making flying unusable for some seconds , especially on approach or landing is very frustrating or when xpilot disconnects. I also hear the CPU Fan maximizing the RPM when this happens (Noctua, temps stay under 80C when full load) I have tried the shortcut thread fix and also tried to remove some plugins and scenery files and still occurs. (Didn't test removing the orthos and True earth products but that's not the case, any other plane flies good) Now I installed the 6gb or less VRam setting to see if anything changes. My specs 11700K - 3070 - 32 RAM - non OC and x plane settings are safe mid to high. Cl65 is by far my favorite one, can't easily go back to any other plane so wishing for a fix or workaround Nick

I'm somewhat dismayed that this was neglected in the 1.5.2 update. Bob

AFM limitations on A/P use

I'm assuming all your questions have been answered in the discord.

Here is something to try: Open the IXEG_user_prefs.txt file with a text editor (it is in the aircraft main folder). Change this line: disable_mainmenu_popout = 0 to disable_mainmenu_popout = 1 Now start X-Plane and assign a button or keypress to the command: ixeg/733/toggles main menu ON/OFF Now when you run the 737, you should be able to pop that menu with that button/key. Maybe you need to adjust the position of the window (where it pops up), you should be able to do that with changing the mainMenuX and mainMenuY values in that preference file. Cheers, Jan