Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

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.

Question: Prioritize flight model, GPS turn control, and VNAV pitch control fixes?

Featured Replies

After nearly three months, the TriStar still has flight model and autopilot issues that make it unrealistic at best, and less than flyable at worst. The issue of the GPS turn commands coming in late at higher speeds annoys me to the point where I use the INS for everything, including SIDs and STARs. The issues of unrealistic vertical speed in the climb, unrealistic deck angle during cruise and approach, and autopilot VNAV pitch commands coming in late during the climb annoy me to the point where I don't even want to fly the aircraft until they're fixed.

To expand:

  • The GPS seems to issue turn commands too late at higher airspeeds, which causes the aircraft to consistently overshoot turns when using the GPS - I've seen this at any airspeed above ~180-190 knots.

  • The vertical speed in the climb seems to be nearly constant above ~10,000ft, suddenly drops off when the PMS switches from CLB1 to CLB2 around 20,000ft, then stays almost constant again until the switch to Mach hold. Vertical speed should simply gradually decrease with altitude. This has been reported previously by others.

  • The aircraft's deck angle should be a couple of degrees lower during cruise and at least a couple of degrees higher during approach. This was also reported previously.

  • In VNAV mode, the autopilot commands pitch increases too late and too gradually during the acceleration phases of the climb, which results in the aircraft overshooting the set speeds by a minimum of 10-20 knots, and consistently ending up breaking the 250-knots-below-10,000-ft speed limit by at least 20 knots. The autopilot seems to currently be commanding the pitch increases just as the aircraft reaches the set speed - it should start commanding the increases sometime before reaching the set speed - and the pitch increase is also far too gradual to successfully capture the set speed.

My question to the iniBuilds team: is it unreasonable to request that solutions to these issues be prioritized over everything else with this aircraft at this time? The visual and systems fixes you've made so far are much appreciated, and overall, I like the TriStar, and I want to be able to fly this rendition of it realistically... but I don't feel I can fly it realistically as long as such fundamental issues as these exist - hence, I don't fly it at all except to test fixes released in updates.

Thank you for reading.

Create an account or sign in to comment

Account

Navigation

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.