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.

Jonesmann

Member
  • Joined

  • Last visited

Everything posted by Jonesmann

  1. Hello, I'm experiencing an issue with idle reverse thrust in the iniBuilds A380 when using my Honeycomb Bravo throttle quadrant. I would appreciate your help in identifying whether this is expected behavior, a configuration issue, or a potential bug. Hardware and configurationThrottle quadrant: Honeycomb Bravo Reversers on axis: Off Keybind: Hold Throttle Reverse Thrust (as officially recommended) Calibration: My throttle has been calibrated accordingly Issue descriptionThe reverse thrust functionality generally works as expected, but I'm experiencing an issue specifically with idle reverse thrust. With the thrust levers at idle, activating the Hold Throttle Reverse Thrust keybind does not immediately engage reverse thrust. Reverse thrust only activates once I move the thrust levers slightly forward, introducing a small amount of thrust. When reverse thrust is already active, pulling the thrust levers back to idle while keeping the reverse thrust keybind activated causes reverse thrust to disengage. Expected behaviorI would expect idle reverse thrust to engage immediately when activating the Hold Throttle Reverse Thrust keybind with the thrust levers at idle. Additionally, when reverse thrust is engaged, pulling the thrust levers back to idle should result in idle reverse thrust rather than disengaging reverse thrust entirely, provided the reverse thrust keybind remains active. Additional informationI have verified that my Honeycomb Bravo is calibrated according to the iniBuilds recommendations. The same hardware and general control setup work correctly with the Fenix A320 for example. This makes me wonder whether the issue could be specific to the iniBuilds A380 or its reverse thrust implementation. QuestionsIs this behavior expected with the Honeycomb Bravo, or could there be an additional setting required to enable proper idle reverse thrust? Is there a recommended configuration or workaround for this issue? Could this potentially be a bug with the A380's reverse thrust logic? Thank you for your time and assistance. I'm happy to provide additional information or screenshots of my control settings if needed.

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.