Menu

#2208 Possible route manager bug breaking 777 A/T functionality

2019.2
NeedInfo
Medium
2020-08-06
2020-04-13
Sidi Liang
No

Possible route manager bug breaking 777 A/T functionality
Causing the speed dropping to 000 if cruising speed not entered in route manager

Could be fixed aircraft wise, but it would be good to take a look as it's possible that the 777 is not the only aircraft affected.

https://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/E8978A5E-CB28-400D-89F7-228082F19B47%40flightgear.org/#msg36459384

Related

Tickets: #2208

Discussion

  • James Turner

    James Turner - 2020-04-13
    • status: New --> NeedInfo
    • assigned_to: James Turner
     
  • James Turner

    James Turner - 2020-04-13

    Sidi, please add the following info:

    • does the problem occur in 2018.3.5?
    • does the problem occur with a nightly build?
    • exact steps to reproduce the problem, ideally with the UFO

    (If no possible with the UFO, specify the exact aircraft to use, command line options and every sequence to show the problem )

     
  • xDraconian

    xDraconian - 2020-08-06
    • labels: --> RouteManager
     
  • legoboyvdlp

    legoboyvdlp - 2020-08-06

    Actually, did it possibly (unintentionally) get fixed by https://sourceforge.net/p/flightgear/flightgear/merge-requests/221/?

    It rings a bell as a situation where cruise speed would be reset to zero.

    I'm not familiar with the 777 code, I wonder does it use the cloning API.

     
  • legoboyvdlp

    legoboyvdlp - 2020-08-06

    No, it doesn't seem to. Will check the VNAV code to see if it checks if the route manager speed is set. If its not set, the aircraft code should handle that, we can't provide sensible estimates of cruising speed on the C++ side without knowing what the aircraft type is.

     

Log in to post a comment.

MongoDB Logo MongoDB