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.

Updated 737 Autopilot & settings file

Featured Replies

Hi All,I've been using FlightGear for about 5 months now and as a Software Engineer, I was interested in how it all worked. Also, during this time I noticed that some of the aircraft are not full implemented.I was unsure whether I could actually make a difference but it appears that I have been able to add functionality to the 737 autopilot that was documented as needing to be done.My questions now are:1. Who do I contact to discuss what I've done?2. How should I document the changes I've made?3. Can I freely distribute this to anyone who wants it?4. Who do I contact to discuss what else I can do?For those who want to know what I've done:1. Altered the autopilot panel so it is slightly smaller so it fits the autopilot enable and autopilot disable buttons.2. Altered the weather-radar.rgb graphic so it is slightly smaller and moved slightly left so I could fit more of the auotpilot panel in.3. Implemented the Vertical Speed Hold button. Added code to 747-autopilotV4.xml and altered autopilot-panel.xml 4. Altered the 737-set.xml file. Changed the initial target-speed-kt for the autothrottle to read 175 which I think is approx. V2+15. Added a setting for initial mach number (0.67) Before, everytime you switched to mach, it read 0.00 so the throttles would go to idle. Now it reads 0.67 initially which is the maximum speed from FL180 to FL240 which is the time to switch to mach mode (I'm lead to believe).IMPORTANT NOTE: These changes have been made to version 1.65 NOT 2.00 which is the latest. However, I downloaded the latest 2.0 version 737 files and I believe the autopilot files to be identical. So I hope the work I've done has been worth it. I found the latest release of the Concorde for version 2.0 had major problems compared to 1.65 that made it an unpleasant experience. And as the Concorde is my favorite, I'm going to stick with the 1.65 version until I've got another computer up and running, then put 2.0 it on that and see how it goes.Well, that's it. No doubt I've forgotten to document something important so I'm sorry in advance and very much look forward anyone's response.Happy Flying!

>Hi All,>>I've been using FlightGear for about 5 months now and as a>Software Engineer, I was interested in how it all worked. >Also, during this time I noticed that some of the aircraft are>not full implemented.make this, most of them.>I was unsure whether I could actually make a difference but it>appears that I have been able to add functionality to the 737>autopilot that was documented as needing to be done.>>My questions now are:>>1. Who do I contact to discuss what I've done?http://www.flightgear.org/mail.htmlSubscribe to the developer's list, there is currently an effort on going to develop a new 737 with more functionality, that way you should be able to get in touch with the 737 developers as well as people who are able to commit your changes to the 737-300 in FG CVS.>2. How should I document the changes I've made?usually, comments in the affected source files (i.e. XML, Nasal etc.) should be sufficient. However, if your changes are comprehensive, it shouldn't hurt to provide a separate ChangeLog file, or if appropriate you can also provide patches to the README files under $FG_ROOT/Docs.Apart from that, most changes should be obvious due to the preference to accept patches as unified diff's (possibly compressed if required).>3. Can I freely distribute this to anyone who wants it?If you modified work that's under the GPL, all of your work also falls under the GPL, so yes you can distribute your modifications directly as long as you comply with the details of the GPL.http://en.wikipedia.org/wiki/GNU_General_Public_Licensehttp://www.gnu.org/copyleft/gpl.htmlhttp://www.fsf.org/licensing/licenses/gpl.html>4. Who do I contact to discuss what else I can do?The FlightGear mailing list (devel) would seem like the most appropriate place, as mentioned already there is currently a group of people concentrating on an effort to revamp the 737 significantly.>For those who want to know what I've done:>>1. Altered the autopilot panel so it is slightly smaller so it>fits the autopilot enable and autopilot disable buttons.>>2. Altered the weather-radar.rgb graphic so it is slightly>smaller and moved slightly left so I could fit more of the>auotpilot panel in.>>3. Implemented the Vertical Speed Hold button. Added code to >747-autopilotV4.xml and altered autopilot-panel.xml >>4. Altered the 737-set.xml file. Changed the initial>target-speed-kt for the autothrottle to read 175 which I think>is approx. V2+15. Added a setting for initial mach number>(0.67) Before, everytime you switched to mach, it read 0.00>so the throttles would go to idle. Now it reads 0.67>initially which is the maximum speed from FL180 to FL240 which>is the time to switch to mach mode (I'm lead to believe).These modifications look as if they shouldn't cause any problems for redistribution, mainly because they seem to be your work exclusively, as well as due to the fact that these are modifications that require the modified sources, anyway.

Create an account or sign in to comment

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.