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.
Sidi, please add the following info:
(If no possible with the UFO, specify the exact aircraft to use, command line options and every sequence to show the problem )
@sidi762 Can you give a bit more more information on this : especial,y Isaak said it might be fixed with 'next' - and does it occurn in other versions?
Hi James,
I'm afraid that I really don't have time to test now, sorry. I will
definitely do it as soon as I got any spare time. I've forward your message
to the forum where there are some others reporting this and asking them for
information but haven't got any reply yet.
Kind regards,
Sidi
James Turner jmturner@users.sourceforge.net 于2020年4月19日周日 下午4:49写道:
--
Sidi Liang
Related
Tickets: #2208
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.
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.