richboy2307

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, 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!

Hi, We've tried again on 2 separate systems, spawn cold and dark on gate at LPFR Gate 323. 10 subsequent starts (5 with Engine #1 on first, 5 with Engine #2 on first). We made sure to force a re-download of the packages as well to ensure its streamed fresh between sim restarts. Unfortunately, the issue was still not reproducible in this test. We recommend affected users to try to re-download the package, or reach out to MS Support (MSFS Forums or Zendesk) for further support in case that does not resolve the issue for you. Thanks!

The Marketplace is currently not available for FS2024, as such not possible to push updates or content for FS2024 via the marketplace until then. The v1.0.4 update is only available for purchases made outside of Marketplace for the time being. Happy Holidays, Thanks!

Hi @SteveS Please ensure photogrammetry is enabled, and cross check that you have uninstalled the handcrafted EGSS that comes with the worldupdate? Please refer to below video (@1m20s) for how to disable default content via the Library in FS24: Thanks!

Hi thanks reported. Happy Holidays!

Hi, please rest assured that the correct version is being installed. v1.0.1 FS20 is same as v1.0.0 FS24. We've asked iniManager team to look into updating the respective changelogs. You need to manually disable the handcrafted streamed scenery version of those specific airports from your library. You can see the below video for guidance (@1m21s): Thanks!

Hi, Apologies for delay in response. Please note below items: The liveries are not cross-compatible across versions due differences in model structure. Liveries made for FS2020 will work for the Compatible Edition on either sim FS20/24. These liveries will not work on the Premium Edition (FS24). Liveries made for Premium Edition (FS24) will only work with that specific edition in FS24 due to the new 'modular simobject' structure used. These liveries will not work on the Compatible Edition (FS20/24) If you are downloading the liveries from the iniManager, please make sure you have installed the appropriate livery for the version of A300 you're using. This is an acknowledged core sim issue. As mentioned in the launch forum post: https://forum.inibuilds.com/topic/24363-lets-talk-inibuilds-a300-600r-airliner-updates-for-msfs2024-msfs2020/ Asobo is aware and have possibly fixed this already internally, however it is pending a public release: https://devsupport.flightsimulator.com/t/couldn-de-init-wasm-with-fsnetworkhttprequestget/11969/6 Can you please confirm that you see the ``inibuilds-aircraft-a300-600`` folder inside your custom community folder? Also ensure this custom community folder is being read as active by the sim. You can test by adding any other addon to this custom location and confirm its showing up in the sim. Thanks!

Hi, Apologies for delayed response. Please see the below and let us know the results. A) If you're using FSUIPC7 - Navigate to the fsuipc-lvar-module folder, installed into the Community folder by FSUIPC installer. - Edit the FSUIPC_WASM.ini file. Ensure it reads: - For some users this value defaults to ``-15`` which causes issues such as low fps, stuttering or crash on load. B) Run with empty community folder Please try this to rule out any other addon conflicts. To run with a blank community folder without losing your addons: Rename your existing community folder to ``_Community`` Create a new ``Community`` folder in its place. Copy only the ``inibuilds-aircraft-a300-600`` folder inside it. Empty your A300 Compatible WASM Folder: Run the sim and see if same problem persists. To restore your original folder as follows: Copy the ``inibuilds-aircraft-a300-600`` folder back to ``_Community`` Delete the new ``Community`` folder you made Rename the ``_Community`` folder to ``Community`` The liveries are not cross-compatible across versions due differences in model structure. Liveries made for FS2020 will work for the Compatible Edition on either sim FS20/24. These liveries will not work on the Premium Edition (FS24). Liveries made for Premium Edition (FS24) will only work with that specific edition in FS24 due to the new 'modular simobject' structure used. These liveries will not work on the Compatible Edition (FS20/24) If you are downloading the liveries from the iniManager, please make sure you have installed the appropriate livery for the version of A300 you're using. Thanks!

Hi, thanks. Reported and suggestion shared with the team. Happy Holidays!

Afraid not. Does seem like right brake axis was engaged for longer than the left. Please check control bindings across all connected devices and make sure to unbind the axis/button for brakes from other devices. Thanks!