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.

richboy2307

Staff
  • Joined

  • Last visited

Everything posted by richboy2307

  1. That sounds like a control bindings issue, potentially conflicting inputs. Try to recycle your control profiles, and if you have other controls assigned with axis, ensure that the rudder axis is disabled on them. Alternatively it could be the auto-rudder fighting you, so please check the Assistance options and ensure all are disabled as suggested here: As for the nosewheel steering, if you're only using the rudder axis, please ensure the option is enabled on the aircraft EFB: As for rudder sensitivity, it will depend on individual hardware and you should adjust the curves/sensitivity to your liking. Thanks!
  2. Hi @Norwenkel On the A330 there are effectively 2 switches for Dome Lights control: CTL Switch turns the Dome Lights ON or OFF. STORM / BRT / DIM controls the various brightness levels of Dome Lights when the CTL switch is ON. The lights are confirmed working on all the planes. However in some instances they may not show because of streaming issues. You may try to reload the aircraft, or force a re-download of the package by following these steps: Thanks!
  3. As long as the "twist" is assigned to "RUDDER AXIS" in the MSFS control settings, then you should set the EFB option 'RUDDER CONTROLS TILLER' to YES. This will ensure that when you twist, it moves both the rudder and tiller together. When 'RUDDER CONTROLS TILLER' is NO then the "twist" only controls rudder, not the nose-wheel. Thanks!
  4. richboy2307 replied to Swagger897's topic in Systems
    Hi @Swagger897 Thanks for the feedback. Shared with the team.
  5. Yes on airbus aircraft it is a pre-requisite for a lot of the AP modes, especially managed. Thanks!
  6. For this use the Rudder Axis, and ensure the EFB setting is enabled. Please see guide here: All of these again sound like issues caused because the plane hasn't initialized properly as the necessary components haven't streamed in full yet. Please try the suggestions in the first reply to try and remedy that. Thanks!
  7. richboy2307 replied to johna320's topic in Sounds
    Hi @johna320, please try: Thanks!
  8. Hi @flying_dude Thanks for the feedback, but unfortunately at the moment not possible to define a fixed size for co-pilot avatars as they change dynamically. Moving it any lower would cause the co-pilot to simply clip into the seat. You can however disable the co-pilot if you wish. To do so: On the Main Menu, click your Username on top right corner to access the Pilot Profile page. Here, select 'Customize Identity' > 'Co-Pilot' and select the first option (/). Hit 'Save and Back' to confirm the setting. Thanks!
  9. Duplicate post, for answer see:
  10. Hi @ozzy s Thanks for the feedback, however that is not currently possible as the SDK documentation for integration of its features outside of the default EFB is not available. In any case, the decision for such feature implantations on A320Neo and the other Microsoft Airbus aircraft rests solely with them. So please post on the MS Forums for such requests. Thanks!
  11. Hi @ffortin Unfortunately no as the model itself is different, not just the file structure. Thanks!
  12. Hi @knich Are you still having the issue? If so please try the following: Clear the WASM Folder: Re-download the streamed package: If all else fails, reinstall the sim as some core files may not have installed properly. We're not able to reproduce such CTDs on our end. Thanks!
  13. Hi @Dave Mass Its hard to say what may the issue without any screenshots or videos as to what you were seeing in the cockpit. Can you confirm you're using LOCKED or LEGACY interaction? Also what was your phase of flight? When you're stuck as such, try a direct to another waypoint in the MCDU and see what happens. Thanks!
  14. Hi, the sidestick AP disconnect is mapped to the 'AUTPILOT OFF' keybind. Please assign a key to that in order to operate the switch. Thanks!
  15. Hi @vschwarz504 Thanks for your report. I've passed it on to our team to see if there's anything to do on our end. However at a glance, to me it does seem like possibly some conflict in the navigraph navdata itself. Can you please also report the same on the Navigraph forums? Thanks!
  16. Please follow the guidance here to disable AI Assists: Let us know if you're still experiencing the problems mentioned after. Thanks!
  17. Hi @Nillerg0d The AP can disconnect for a variety of reasons, the most common being due to a constant control input (noisy axis) or due to the MSFS AI Pilot assistances causing a conflict. For the former, check your controller axis and add a relevant "deadzone" in the middle that covers the noisy area. For the latter, please ensure the assists mentioned here are disabled: Other than that, please provide screenshots/videos of the instances where you're noticing this issue so we can have a better idea of potential causes. Thanks!
  18. Hi, The TERR is INOP on all the Airbus/WASM aircraft for the moment pending the resolution of simulator-level bug. For further reports/enquiries on this matter please post directly on the MS Forums. Thanks!
  19. Hi, this system is not currently implemented. We can disable the clickspot meanwhile to avoid confusion. For both the feature request and documentation, its entirely up to MS as these are their products. So please make a post on the MS forums for this. Thanks!
  20. Hi @stef Thanks for your report, it is noted.
  21. Hi, Thanks for your reports. Unfortunately I'm not seeing this on our end. This may be related to an improperly streamed package? Please try both of the following: Thanks!
  22. Hi @MalevolentKiwi That is a question best asked on the MS Forums. As these are Microsoft products, the distribution and delivery of content for them is solely up to them. Thanks!
  23. Close the simulator if it is running. Navigate to your your FS24 WASM Folder: Steam: MS Store: Delete the 'microsoft-aircraft-belugaxl' folder. This folder and its contents will be re-generated next time you load into a flight with the aircraft. Note: This will reset your EFB Throttle Calibration and EFB Settings so they should re-done the next time you load into the aircraft.
  24. Close the simulator if it is running. Navigate to your your FS24 WASM Folder: Steam: MS Store: Delete the 'microsoft-aircraft-a330' folder. This folder and its contents will be re-generated next time you load into a flight with the aircraft. Note: This will reset your EFB Throttle Calibration and EFB Settings so they should re-done the next time you load into the aircraft.
  25. Close the simulator if it is running. Navigate to your your FS24 WASM Folder: Steam: MS Store: Delete the 'microsoft-aircraft-a321' folder. This folder and its contents will be re-generated next time you load into a flight with the aircraft. Note: This will reset your EFB Throttle Calibration and EFB Settings so they should re-done the next time you load into the aircraft.

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.