richboy2307

Hi all, Firstly apologies for delayed response. I have shared your reports with our team for further investigation. Are you also experiencing this issue with other non-airbus aircraft when entering cursor mode? If so, I would also recommend posting the same on MS Forums as that would be something core-sim related rather than the aircraft itself in particular. On PC, I have tried 2 flights with the Xbox controller on the A320neo, using it exclusively for flight control and cursor mode (RB + L stick) interactions. Some observations I had: Cursor Control is not exclusive all the time. It appears whilst in cursor mode, the left stick will still occasionally register flight stick control inputs instead of exclusively controlling the cursor only whilst in this mode. This in turn has the effect of AP disconnection as stick input is detected. Equally the "A" and "B" buttons sometimes also register input on the Throttles, as such leading to its movement outside of or between detents. So for the time being, be wary of this, recenter the left stick and check throttle detent visually to confirm in the appropriate mode. Also verify the rudder trims are centered (value is seen near the flaps lever). Autoland issues mentioned above were not reproducible. I did not experience the issues of freeze or AP disconnection during autoland (both AP1 and AP2 connected). Tested at LPFR ILS Z 10 and LPPT ILS 02 on these 2 flights. In both instances the aircraft continued through the appropriate modes, getting into rollout and AP only disconnected after aircraft came to a complete stop on the runway. As such, I would appreciate if you could also include a video recording of just the approach and landing phase. You may upload these clips on youtube and share a link if its too bug to upload directly to the forums. We would like to get to the bottom of this issue as well and implement any fixes that are possible on our end to improve your flying experience. Thanks!

Hi, Yes thanks for the info. Our team is investigating as well. The only thing that has changed is the new AIRAC cycle that went live on 26th Dec 2024, so it is possible there is some conflict with this new navdata that is causing a WASM crash on spawn, affecting the A310 in both MSFS 2020 & 2024? Thanks!

Hi @LukeFF Thanks for the info but as mentioned in the first post, please record your in-sim FPS window in full, perhaps take screenshots at the various stages of flight and share here. The information about the fps on its own is not useful in diagnosing any potential issues. That window will provide additional data that may help in that regard. The sim FPS window is accessed via: - Settings > General > Advanced Options > Developer Mode - ON - Then on the [DevMode] bar > Options > Debug > Display FPS Thanks!

I believe normally it should only chime that warning for OIL TEMP below 50c. Noted, thanks.

This is likely due to the IGNITION knob not being returned to OFF position after engine start. The pack valves are closed in either START A or B position, as such the aircraft is probably not being pressurized properly. There is a difference between the certified maximum ceiling for the type and your MCDU computed current "MAX" cruise level. The latter is calculated by the onboard software and is the maximum altitude currently recommended based on a number of performance factors (e.g. OAT, Gross Weight etc). This value is dynamic and can change throughout your flight as the contributing factors change (temp or weights as you burn fuel). You can find your current computed MAX level on the PROG page. Thanks!

Hi @LtSnake Moved to a new topic as this is a separate issue to the one where you had initially posted. I was able to reproduce the WASM crash, reported. Thanks!

Hi @rexizam This is currently posted in the A300 (Premium) support section. I'm moving your post to the A310 section. This issue is noted, see this post for more details: Thanks!

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.