Jump to content

Sign in to follow this  
Richdem

TBM ILS Issues

Recommended Posts

Since Tuesday’s update I am having issues capturing the localizer & glide slope in the TBM. It just seems to ignore them
 

I’ve tried with and without the current mods for the TBM. Anyone know a work around or know what changed ?

  • Like 1

 

 

My Rig: i5 9600K @ 5.0 Ghz Air Cooled (Noctua NH-D15S) | Asus Prime Z390 - A | 32 GB DDR4 3000 | ZOTAC GTX 1080 TI AMP Edition With Double Noctua NF-12 Mod | 1TB WD Blue NMVE (X-Plane 11 & MSFS 2020) | 2 X 250GB SSD | 4TB WD Black Conventional |, LG 42" LED TV

 

Share this post


Link to post
Share on other sites

Yep, Longitude is the same thing, not sure why, they broke something with the update I'm guessing..

  • Like 2

UPS123.png

 

 

Share this post


Link to post
Share on other sites

I noticed the same in the Longitude after the last patch. The LOC/GS guidance is there, but the Autopilot completely ignored it. Appr button pressed. 

Share this post


Link to post
Share on other sites

TBM fail to capture ILS for me as well.


| I9 10900K | 32Gb 3200MHz | RTX 2080 Ti | 1TB M.2 SSD | BenQ EX3501R | TM Hotas Warthog | VKB-SIM T-Rudder Pedals |

Share this post


Link to post
Share on other sites

Oh boy,

2 steps forward and 10 backwards 

  • Like 2

 

 

My Rig: i5 9600K @ 5.0 Ghz Air Cooled (Noctua NH-D15S) | Asus Prime Z390 - A | 32 GB DDR4 3000 | ZOTAC GTX 1080 TI AMP Edition With Double Noctua NF-12 Mod | 1TB WD Blue NMVE (X-Plane 11 & MSFS 2020) | 2 X 250GB SSD | 4TB WD Black Conventional |, LG 42" LED TV

 

Share this post


Link to post
Share on other sites

Yep AP is messed up since last update. 

I could capture ILS in the PA44 Seminole, but it's too slow to turn so it overshoots the localizer. 

I think Asobo gets a bit harsh treatment on these forums, but the ILS is such an integral part of the AP system, it seems very strange to me that they didn't check this when adjusting the autopilot.

Edited by Republic3D

R9 5900X | RTX 3090 | 64 GB 3600 | 3440x1440 G-Sync | TrackIR 5 | Oculus Rift S

Share this post


Link to post
Share on other sites
24 minutes ago, Republic3D said:

Yep AP is messed up since last update. 

I could capture ILS in the PA44 Seminole, but it's too slow to turn so it overshoots the localizer. 

I think Asobo gets a bit harsh treatment on these forums, but the ILS is such an integral part of the AP system, it seems very strange to me that they didn't check this when adjusting the autopilot.

The ILS failure is a direct consequence of slowing down the heading function in the last update. Because the heading capture now slows down to a crawl for the last 30 degrees, this also has a direct impact on ILS LOC capture, as the LOC function uses the heading and roll modes to calibrate its own ILS function. 30 degrees is the most important area where the ILS autopilot is most active. So with the last update, if you are not already dead straight on an approach, but to one side, the LOC function will not capture the ILS because the same heading slowdown will make the Localiser adjustment also slow to a crawl.

Ironically you might have better luck capturing an ILS from outside a 30 degree angle as only 30 degrees and greater triggers the needed bank. If you are capturing from say 10-20 degrees offset, the a/p will not turn quickly enough.

Asobo failed to realise that neutering the heading mode also neuters the localiser mode. This is a classic case of tweaking something without thinking or testing the consequences. I am flabbergasted that Asobo has not issued an immediate apology and also immediately reversed this with an instant patch.

Edited by robert young
  • Like 4
  • Upvote 2

Robert Young - retired full time developer - see my nexus mod page and my GitHub Mod page

Share this post


Link to post
Share on other sites
On 11/28/2020 at 11:02 PM, robert young said:

The ILS failure is a direct consequence of slowing down the heading function in the last update. Because the heading capture now slows down to a crawl for the last 30 degrees, this also has a direct impact on ILS LOC capture, as the LOC function uses the heading and roll modes to calibrate its own ILS function. 30 degrees is the most important area where the ILS autopilot is most active. So with the last update, if you are not already dead straight on an approach, but to one side, the LOC function will not capture the ILS because the same heading slowdown will make the Localiser adjustment also slow to a crawl.

Ironically you might have better luck capturing an ILS from outside a 30 degree angle as only 30 degrees and greater triggers the needed bank. If you are capturing from say 10-20 degrees offset, the a/p will not turn quickly enough.

Asobo failed to realise that neutering the heading mode also neuters the localiser mode. This is a classic case of tweaking something without thinking or testing the consequences. I am flabbergasted that Asobo has not issued an immediate apology and also immediately reversed this with an instant patch.

Thank you for the detailed explanation,

It is such a shame ASOBO do not fully test the updates before releasing them, it really is ruining their credibility. It would be nice if you could get a choice to perform the update or ignore it as you do in X-Plane 11 


 

 

My Rig: i5 9600K @ 5.0 Ghz Air Cooled (Noctua NH-D15S) | Asus Prime Z390 - A | 32 GB DDR4 3000 | ZOTAC GTX 1080 TI AMP Edition With Double Noctua NF-12 Mod | 1TB WD Blue NMVE (X-Plane 11 & MSFS 2020) | 2 X 250GB SSD | 4TB WD Black Conventional |, LG 42" LED TV

 

Share this post


Link to post
Share on other sites

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
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    41%
    $10,300.00 of $25,000.00 Donate Now
×
×
  • Create New...