richboy2307

Hi, For more info see: Thanks!

Can you please share a screenshot (or preferably a video) of what you're seeing? Also please share your hardware (CPU/GPU/RAM) and sim graphics settings (Anti-aliasing mode used, resolution and cloud/texture/windshield settings). Thanks!

Please try loading into the aircraft now and see if you're still having the issues. Some of our testers reported the issue is no longer happening as of today. We believe it may have been related to the validity date format of this particular AIRAC cycle - the end date (23 Jan 2025) going into another year at the time this was initially reported (2024). However, now that we're in the same year, the issue is seemingly no longer occurring. We would appreciate if others could confirm the same. Thanks!

Yes that is an option, as long as both purchases are made via the same via the same account on inibuilds store (website or iniManager) or Simmarket respectively. For Marketplace customers (PC), as the FS 2024 Marketplace is not yet available, this is currently not possible unless you request a permanent order transfer of your purchase to the iniBuilds Store: https://inib.uk/order-transfer As for Marketplace purchases/upgrades to FS2024 for Compatible/Enhanced/Premium editions of products in general, please see quote from below linked post: Yes expect some delay due to the holidays. I've replied to your forum post here as well with additional info: Thanks!

Hi, Unfortunately as this process is not entirely in our hands, we cannot provide any ETA for update availability via the Marketplace. The transfer requests have to be processed by both parties (original store and ours) so can take some time. Ofcourse with holidays period in between, some delay is to be expected for both of the above. In case you do not hear back regarding your order transfer by end of next week (check your email spam folder), please reach out to Direct Support with your original transfer request info : https://inibuilds.com/pages/contact Thanks!

Hi all, As mentioned on discord: For PC users, the community suggested workaround to this issue is switching Texture Resolution to "High" or "Ultra" for now. Thanks!

Hi @Errandil It's a known sim issue we are tracking that looks to be on the MS/Asobo side. It is not limited to just streamed aircraft, but rather a rendering thing. There is a thread here on the MS forums that you should post to for maximum visibility on this topic. For clarity, nothing has changed build-wise between pre and post patch with our aircraft so we're looking deeper into why folks are seeing this from time to time. For PC users, the community suggested workaround to this issue is switching Texture Resolution to "High" for now. Thanks!

Hi @Powie I would start by looking for conflicting control bindings for brake axis, particularly right brake. Also check for any conflicting control bindings for rudder (yaw or trim) as well as nosewheel steering. Have not seen this at all during testing, nor reported elsewhere so chances of it being an aircraft bug are low. In fact just tried at LFMN (ILS Y 04L) and did not have any issues (well other than the LOC/GS misalignment with runway but thats likely a scenery/navdata issue) 2025-01-03 21-48-54(1).mp4 Thanks!

Hi @eschoyen Does this issue also happen when you spawn on runway? I have tried spawning in at the gates and airports mentioned with the DHL PW livery and did not notice this issue. I suspect the following On spawn your aircraft is somehow going into "pushback" state by default, likely due to some keybind. Check your control bindings perhaps? Alternatively, reversers are being toggled somehow initially before the aircraft resets to cold and dark on spawn. Have you calibrated your throttles from the aircraft EFB? Make sure you do that and select "Reverse on Axis = NO" Thanks!

Thanks reported.

Thanks, reported

Out now as of 1 Jan 2025: Thanks!

Yes that is what it seems like at the moment, especially for all the phases until cruise. Its possible the AI Pilot is taking over on final approach as well, but that is quite odd as I see the AP disconnect automatically. I haven't had such issues when I have tried. Also thanks for making the post on MS forums as well for their teams. I see you also mentioned the issue on this forum bug report, may I suggest adding the above videos there as well? https://forums.flightsimulator.com/t/ai-pilot-engages-in-cursor-mode-and-messes-up-flight/671715 As for the avionics freeze, can you please also make a video for that? Also please try to delete your StreamedPackages folder to see if you still have the issue after? Instructions here for console: https://flightsimulator.zendesk.com/hc/en-us/articles/17268168854044-Loading-issues Well, their teams have been away for the holidays, so expect some delay in response. I'd imagine most would be back in office starting next week. Thanks!

This is a new release, which offers all those things mentioned on the dedicated FS2024 version (v1.0.0 FS2024). What I meant was that in terms of the changelog, the "fixed" items are the same, i.e. the below bugs mentioned as fixed on v1.0.1 FS2020 are fixed on launch of v1.0.0 FS2024 as well. Thanks!

Thanks I've shared with the team, but unfortunately we weren't able to reproduce the visual artifacting on our end. Can you please add an additional video of what you're seeing on 2024? Thanks!

Hi @El_Comma English only please on the forums. Please only install one of the versions for FS2024 in your community folder: A300-600 Premium Edition (MSFS2024 Only) A300-600 Compatible Edition (FS20/24) 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 A300-600 Airliner Premium Edition Product page, you will see only 1 Install button which is for MSFS 2024 only. (Click to enlarge image) On the A300-600 Airliner Compatible Edition 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. (Click to enlarge image) Thanks!

Hi, @LucaMost English only please on the forums. It's a known issue we are tracking that looks to be on the MS/Asobo side. There is a thread here on the MS forums that you should post to for maximum visibility on this topic. For clarity, nothing has changed build-wise between pre and post patch with our aircraft so we're looking deeper into why folks are seeing this from time to time. For PC users, the community suggested workaround to this issue is switching Texture Resolution to "High" for now. Thanks!

No, it should work the same as far as the aircraft logic is concerned. There are differences in the flight dynamics (CFD) model between the two sims, but that should not affect autoland capabilities. From my observation the only difference I'm seeing is the way the cursor control mode works in FS2024 vs FS2020, wherein the cursor can disappear from the screen and when that happens the control inputs become active (even though the mode wasn't exited). So there can be residual control inputs which would be particularly noticeable on the PFD. For example in the below image you can see the "+" on the pfd (in the red box), the control input is not centered whilst in cursor control mode. Whilst moving the cursor, it appears to have detected some input on the flight control stick. (Click to enlarge image) Thanks!

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!