clrCoda wrote in Sun Aug 16, 2015 5:39 pm:I'm not quite familure with looking at sourceforge for the file and dialing controls.nas back to a version when all of the keyboard commands still worked for a comparison.
Johan G wrote in Sun Aug 16, 2015 6:20 pm:It seems we are straying a bit from the topic though.
clrCoda wrote in Mon Aug 17, 2015 1:23 am:@Johan G
Can we move posts from here downward in this current thread:
http://forum.flightgear.org/posting.php?mode=reply&f=24&t=27090#pr254122
to the end of this conversation at
Paper Cut Bugs?
clrCoda wrote in Thu Oct 08, 2015 11:23 am:Or we fix the real problem which is to return the commit that broke everything just to fix the bravo and fix the bravo with a switch that switches the passive mode, such as a hooking passive mode to the flight director where I think it belongs.
Gitorious.org is migrating all the repositories to Internet Archive.
The repositories will soon be available for read-only access, with original clone URLs preserved.
clrCoda wrote in Tue Oct 13, 2015 4:30 am:I'm sorry that this appears to be taking me longer that we might have hoped.
Current reasonable excuse for delay is that some of the information I require to build the accurate history is at gitorious and according to them for the last week or more :Gitorious.org is migrating all the repositories to Internet Archive.
The repositories will soon be available for read-only access, with original clone URLs preserved.
clrCoda wrote in Tue Oct 13, 2015 6:34 am:I forgot to mention that the other suggestion for this is to just add the toggle to any plane like the Bravo to toggle the Flight Director passive-mode, and revert the commit that broke the keyboard years ago, and worry about any other plane that was like the bravo that now needs to be fixed.
Possibly the best over all solution, but potentially the most upsetting for untold, undisclosed aircraft.
Users browsing this forum: No registered users and 11 guests