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.

Latest Asobo update has radically changed the a/p

Featured Replies

They should open-source the auto pilot algorithm. Or make it moddable for each plane.

I think Asobo should stop tweaking things they don't understand, and focus on SDK, seasons, scenery.

  • Replies 266
  • Views 41.5k
  • Created
  • Last Reply
2 minutes ago, cepact said:

They should open-source the auto pilot algorithm. Or make it moddable for each plane.

I think Asobo should stop tweaking things they don't understand, and focus on SDK, seasons, scenery.

I think what's really key is more testing,this stuff should be captured in the testing phase,any pilot would pick this up on a simple flight using autopilot, assuming this has been logged at zen desk

Wayne such

Asus Hero Z690, Gigabyte Aorus Master 5080, I914900K, Kraken 360 AIO CPU Cooled, 96 GIGS Corsair DDR5, 32 Inch 4K by 3

Perhaps post a short video so we can see what the issue is.

I'm not surprised at all that they botched the AP. They seem to break or make something worse at every update, but I'm grateful for the add-on content and their pursuit for the perfect sim. They have a ways to go.

MSFS

2 minutes ago, DJJose said:

I'm not surprised at all that they botched the AP. They seem to break or make something worse at every update, but I'm grateful for the add-on content and their pursuit for the perfect sim. They have a ways to go.

I'm sure it will get fixed just wish didn't take so long

Wayne such

Asus Hero Z690, Gigabyte Aorus Master 5080, I914900K, Kraken 360 AIO CPU Cooled, 96 GIGS Corsair DDR5, 32 Inch 4K by 3

13 minutes ago, Jetman67 said:

I think what's really key is more testing,this stuff should be captured in the testing phase,any pilot would pick this up on a simple flight using autopilot, assuming this has been logged at zen desk

Yep, it is what I am fearing, not enough testing or people without enough flying experience. It seems to be only tweaking in the hope it will eventually get better.

  • Author
36 minutes ago, Ricardo41 said:

Perhaps post a short video so we can see what the issue is.

Try it for yourself. Select a heading anywhere from 90 degrees to 180. No matter how large or small the turn, the current update starts rolling out of the turn up to a staggering 40 - 50 degrees to go in some cases. By the time the aircraft gets to within 10 degrees of the desired heading, it is PAINFULLY slow and takes another 30 seconds to a whole minute to settle on the correct heading.

This means that all ILS captures will have to be done from either a very shallow angle, or the capture will slowly miss the mark, or will slowly over-run then have to back track. It means that vectored approaches from ATC under autopilot will be ridiculously slow and continually be wide of the vectored heading. It means that it will be near impossible to follow a flight plan under Vnav that has any tightness to turns.

Edited by robert young

Robert Young - retired full time developer - see my Nexus Mod Page and my GitHub Mod page

I remember that with FS2004, FSX and P3D, the bank angle used to reach the AP target heading was the angular difference between the current heading and the target heading. For example, if you were heading 10° and set the AP to turn right to a 20° heading, the bank angle would be 10°, then 9, 8, 7, ... as long as you get closer to the target. This was very convenient and it worked very well, providing a quick and smooth behavior. In addition, it was very convenient for me, as a developer, to control the bank angle 🙂

I don't know why they didn't keep that part of the code. It was working perfect for years, why did they need to change this?
As cepact said, they should open the doors (= provide a comprehensive SDK) to let us, add-on developers and moders, do this part.

Make sure it's reported on the official forums and brought to their attention, so they can tweak it.

1 hour ago, cepact said:

I think Asobo should stop tweaking things they don't understand, and focus on SDK, seasons, scenery.

This is exactly my feeling.
Pity we have to rely on mods to make basic airplanes systems working correctly, on such a fantastic platform.

- PC Hardware: AMD Ryzen 9 9950X3D //  Asus ROG Crosshair X870E HERO //  2x32Gb Corsair Dominator Titanium DDR5 6000MT/s CL30 //  ASUS ROG Strix GeForce RTX 4090 OC Edition // 4Tb Corsair NVMe M.2 MP600  //  Corsair 1600W PSU
Samsung Odyssey Arc 55" curved 165 Hz monitor.
- Simulator Hardware: VIRPIL Constellation Alpha Prime + VIRPIL VPC Universal Control Panel - #3 + MOZA AY210 Force Feedback Yoke + WINWING URSA MINOR 32 Throttle & PAC Metal + WINWING SKYWALKER Metal Rudder Pedals + WINWING Airbus FCU & EFIS + WINWING Boeing 3N PAP + WINWING MCDU-32 + WINWING PFP-4 + WINWING PFP 3-N + WINWING PFP-7. 

   

 

 

  • Commercial Member
52 minutes ago, robert young said:

Try it for yourself. Select a heading anywhere from 90 degrees to 180. No matter how large or small the turn, the current update starts rolling out of the turn up to a staggering 40 - 50 degrees to go in some cases. By the time the aircraft gets to within 10 degrees of the desired heading, it is PAINFULLY slow and takes another 30 seconds to a whole minute to settle on the correct heading.

This means that all ILS captures will have to be done from either a very shallow angle, or the capture will slowly miss the mark, or will slowly over-run then have to back track. It means that vectored approaches from ATC under autopilot will be ridiculously slow and continually be wide of the vectored heading. It means that it will be near impossible to follow a flight plan under Vnav that has any tightness to turns.

Does it affect only the lateral captures or also the vertical ones? (ALT HOLD, VS MODE, FLC) 

4 hours ago, PuffeB said:

Yes - this change of the AP behaviour is extremely annoying.

Well, from my point of view, I have to disagree. I just downloaded the update and now the autopilot

 

WORKS!!!!!!!!!

 

Since the launch every time I tried to use the AP it basically tried to kill me! When it would actually engage it would, at some point, disconnect and immediately go into a vertical death dive. While it was still straight and level, I could not get the heading hold to engage at all. But in my first flight in the update, it worked quite well for about a half an hour and disconnected smoothly when I turned it off.

I'll take it!

Master Sergeant, U.S. Air Force, Retired

Former T-33A Crew Chief

Former B-1B Crew Chief / Flightline Maintenance Expediter

Former Learjet Corp. Quality Inspector

Formerly Young (😩)

  • Author
3 minutes ago, b1bmsgt said:

Well, from my point of view, I have to disagree. I just downloaded the update and now the autopilot

 

WORKS!!!!!!!!!

 

Since the launch every time I tried to use the AP it basically tried to kill me! When it would actually engage it would, at some point, disconnect and immediately go into a vertical death dive. While it was still straight and level, I could not get the heading hold to engage at all. But in my first flight in the update, it worked quite well for about a half an hour and disconnected smoothly when I turned it off.

I'll take it!

I think you are discussing a different issue. This thread is not about whether the a/p works or not. It is about the detail in how it works. But glad for you that it "works".

Robert Young - retired full time developer - see my Nexus Mod Page and my GitHub Mod page

Yes, I immediately noticed this. I’ve only been at the controls of an actual aircraft twice and never used the autopilot, so I figured I’d keep my mouth shut since I don’t have any relevant experience. Good to know I’m not crazy and that’s not how the real thing works. 

Archived

This topic is now archived and is closed to further replies.

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.