richboy2307

Hi, I believe it is currently mapped to the "TOGGLE" commands for those lights, same as on FS2020, but thanks for feedback, shared with the team. In the meanwhile however, you can also use external tools like Mobiflight (Free) or FSUIPC/Axis&Ohs/ SPAD.Next (Paid) to manipulate the respective LVARs directly. You can find the relevant LVARs listed on this handy mobiflight site here: https://hubhop.mobiflight.com/presets/?aircraft=A300&system=Lights Thanks!

Please see from above post, Include your specs as well. It is difficult to say anything without such data. Thanks!

Hi all, The team is aware and investigating the issue. It appears to be effecting both MSFS2020 and 2024 versions of the A310. For the moment we suspect its related to the latest AIRAC cycle that went live on 26th Dec, as that is the only variable that changed in this time. Thanks!

There has been no change on the A310 package (version). However as these packages are streamed first party content, please reach out to MS Support via their Forums or Zendesk for further support in this regard. Thanks!

Thanks for confirming, noted.

Hi @steve007 Apologies for delayed response. The iniManager can not change your sim's community folder. You need to do that in the sim itself first: https://flightsimulator.zendesk.com/hc/en-us/articles/17046732768796-3rd-party-add-ons-and-Community-folder After you have done that, you can then go to iniManager settings and click the "..." button to select the new community folder path you set above. The iniManager will then install addons to that folder itself starting from next install. Thanks!

Hi The team is working on a FS2024 native version of FAOR that should be available via iniManager soon. Thanks!

You can still download GSX profiles via the iniManager. All you need is an iniStore account, and then you can access the GSX Profiles section on the iniManager Thanks!

Please share screenshots of your cockpit (PFD/ND, FCU and overhead) just before takeoff so that we can see how you've setup and offer better guidance. Alternatively you can watch the series of video here for guidance. While this is from the A310, the process is similar: Thanks!

Hi This issue should be resolved as of v1.1.3 update. Changelog here: Thanks!

Hi, Thanks for your report. Are you still experiencing these issues as of v1.1.4? Thanks!

Hi, V1.1.3 & 1.1.4 have pushed updates with regards to speed control in VNAV. Please confirm if you're still having such issues on the latest version. Changelogs here: https://forum.inibuilds.com/forum/398-updates/ Thanks!

Fixes have been pushed as part of v1.1.3 update. Changelog here: However you may still experience WASM crashes in some instances due to a core-sim issue with regards to memory allocation. For more info see: In case you are experiencing any other reproducible crashes, please make a separate post along with reproduction steps such that the team can investigate the cause and push fixes where feasible. Thanks!

Resolved as of v1.1.4 update. Thanks!

This issue has been resolved as of v1.1.3 update. Thanks!

That sounds like a WASM crash. Please let us know if you're able to reproduce this issue consistently. If so, tell us the steps to reproduce (e.g. what interactions you had just prior to crash). If not, then its likely a random WASM crash caused by memory allocation bug (wherein the sim tries to store data in memory it does not have access to, and thereby crashes the WASM and any system that uses it). Thanks!

Hi Thanks noted. Unfortunately the content of such pages are cached by the sim itself but as of this moment we're not sure of where exactly. Thanks!

Hi Thanks for your reports. Noted.

Make sure you're using the latest version of the iniManager (v2.4.2). You can grab the installer from here and run it to manually update the app: https://inibuilds.com/pages/inimanager-v2 The latest version adds support for MSFS2024 by allowing you to define your MSFS2024 Community folder in the settings (top left corner, click your name to access). Press the 'Scan Now' button to populate the field automatically. Alternatively, you may use the '...' button to define this path manually. FS24 Default Community Folder Paths All addons installed via the iniManager are placed into these defined paths for MSFS 2024 and 2020 respectively. As long as this Community folder is recognized by your sim, the addons here should show up in your aircraft selection window. On the T-33 Product page, you will see 2 separate Install buttons for MSFS 2024 and 2020. They will each have their own Uninstall and Update buttons respectively. Yes, unfortunately as the marketplace is not yet available for MSFS 2024 (PC or Xbox), it is not yet possible to push content or updates via the Marketplace for this sim until that happens. Thanks!

Hi @ALBERTO You need to use the red AP Disconnect button on the Yoke (A300) or Sidestick (A330) to disarm the autopilot. Press twice to disengage the function and appropriate aural/visual warnings. If you are using a keybind, that button is mapped to the AUTOPILOT OFF command in MSFS control settings. Also note, this forum section is for the A300 premium. For A330 related issues please report on the MS Forums or seek community support here: https://forum.inibuilds.com/forum/520-a330-200-300-300p2f/ Thanks!

Please confirm you have installed only 1 of the two versions (Compatible or Premium) into your FS2024 community folder at any given time. This is an issue with WASM initialization. So you should clear your A300 WASM folders, and then on next sim launch spawn directly on the runway. Wait 1-2 minutes to allow time for all the systems to initialize and then report back in case you're still having issues. Note there are 2 different WASM folders in FS2024, depending on whether the addon is native to FS2024 (i.e. Premium Edition) or a FS2020 port (i.e. Compatible Edition). You may have both in case you have tried to load the FS2020 version into FS2024 in the past. For Premium Edition: For Compatible Edition: Thanks!

Thanks reported.

Thanks, the difference in totals appears to be equal to the sum of fuel in the Additional Center Tanks (ACT)( i.e. 5.78+5.78=11.56t KG). Seems like it is not being taken into account on the CTR/TT readout on the overhead Fuel Quantity Indicators. Reported. Thanks!

Thanks noted.

Hi, I'm not able to reproduce this issue of a 0 reading, however do note that the gauge is not matching the SD ENGINE page quantities. Thanks!