richboy2307

Thanks for the bug report. We'll look into it. Unfortunately not, because normally the auto tiller disconnect should take care of it. Thanks!

Hi @Henni100 Once the LDDU is in your community folder, open the iniManager and click on your name on the top-left corner. Then make sure the MSFS library is correctly defined, and hit the 'SCAN NOW' button. That will force the iniManager to rebuild the library and it may appear after. Thanks, will share with the team. Might have been missed. Apologies for inconvenience caused.

Thanks we'll look into it. Meanwhile if you have any other instances, please continue to report and try to include the screenshots as well where possible.

Thanks. If the issue happens occasionally, and is not reliably reproduced by following the same actions, then it is most likely a WASM Crash caused by the "memory allocation" bug. These seemingly "random" memory allocation WASM crashes happen when the sim tries to reserve memory it does not have access to, and as a result crashes WASM. This is a core sim issue and can affect any addon using WASM. I have personally done over 11 flights a300 flights in total, into and out of inibuilds and default EGGW, with and without navigraph navdata during testing without any reliable crashes. So I doubt it is related to that. However if you are getting any crash that is reliably reproduced by doing the same actions each time, then please report below along with those actions so we can investigate further. Otherwise, its likely a random WASM crash owing to memory allocation bug which we cannot address unfortunately. Thanks!

No the import functions for the default planner are only available on pc. For Xbox you have to enter the flightplans manually i'm afraid.

No that is the only one with any meaningful items in it. No news at this time, however do note the entire team was Out of Office since last Thursday owing to the company meet-up in London. As everyone returns to their corners of their world, work is steadily resuming into bug-fixing throughout the week. Thanks!

Hi @Turnkey Maybe not soon but team's already working on WU17 compatibility updates for some of the other sceneries currently, and assessing the compatibility issues across our catalogue. We'll incorporate improvements wherever possible. Thanks!

Awesome! We're delighted to hear that as a lot of effort has been put in to squeezing every ounce of performance we can out of every aspect of this aircraft - art, sound, code etc. Thanks!

Thanks for the update. Clearing your work folder should reset the maintenance items. In case it happens again, try to "REPLACE TIRES" maintenance option from the EFB menu. If that doesn't work, then maybe also try the "REPLACE BRAKES" option from the same menu. Thanks!

Thanks for the report @mlb406, we'll look into it.

Hmm that is quite strange. Haven't ever had that in the countless flights I've done with the A300 so far. Just to confirm, you're running the latest version (1.1.2)? There was a bug with one of the previous versions related to a null value in the fuel system that was already resolved. If yes, please also try to clear the contents of this folder, to ensure there are no leftover files from previous updates. These will regenerate next time you launch the A300. NOTE - this may reset your EFB settings, especially the throttle calibration so make sure to run them again after. Steam: MS Store: I'll share with the team for further investigation. Thanks!

@FRASP We believe the GS ultimately is not exactly in the right place, even with Navigraph Navdata. Its alot less wrong than what the default navdata was, but still not where it ought to be. We have added a custom ILS for all the runways which will overwrite the default navdata. So for those users it will work best. However Navigraph's navdata will always supersede any custom scenery data. After going through multiple builds and extensive testing, there was no way to get it to perfectly align without some unrealistic placement of the PAPI lights at a point down the runway where it wouldn't make sense. Navigraph is also aware and we may look into it again in the future, however for now this is the best implementation possible. You can read more on their forums here: https://forum.navigraph.com/t/omdb-ils-30l-misplaced/16398 Thanks!

Thanks we'll look into it. This is an issue with the Asobo's interaction system in LEGACY interaction mode. As of v1.1.2, we rewrote the XML interactions for all switches from the ground up their template in order to optimize performance. However the issue is that it causes the interaction to be reversed in LEGACY vs LOCKED interaction system, specifically an issue with 3-way switches. There's not much we can do about it at the moment, however whenever possible we'll implement a fix in future updates. The movement is modelled based on observations and data from movements in full-motion simulators and real world counter part of this aircraft. If you find this to be an issue you may click the base of the yoke to hide it completely from view. Thanks!

Hi @UA124567 There have been changes implemented to the VNAV based on feedback provided by IRL operators of the type. The computed VNAV infamously imperfect and "quirky" on the A300 so it may be what you are noticing. However please submit specific examples of where you are facing this issue. In your report please include Full route including runways, SID/STAR/APP used CI, Weights (ZFW/Fuel), Cruise Alt Navdata source - Navigraph or Default Screenshots of your PFD/ND & MCDU F-PLN page & PROG PAGE (showing VDEV) in instances where you notice this issue This will allow us to reproduce the scenario and make refinements if it is not working as intended. Thanks!

Hi @markoxley No firm ETA but I wouldn't anticipate a release until next week at the latest. The team is out-of-office this weekend for the 'iniBuilds Summer Social' event. Thanks for your patience and understanding!

Just as mentioned, it is hard to say at this time. We do intend to support time accelerations, however the specifics of it, and what form it takes eventually can only discussed at a later time in future development updates. Thanks!

Hi @Dani18391 This is often a bug with the default navdata itself. However can you please list which routes / airways/waypoints you had these issues with? Example: On VHHH/25L N0486F330 OCEA2B OCEAN V3 ENVAR M750 TONGA TONG1B RCTP/23L I had issues entering OCEAN V3 ENVAR leg. Thanks!

Hi @orlando011124 While I can't speak for the fidelity of the "original" Asobo A320neo, the Cost Index certainly factors into all stages of flight in determining things like speed, rate of climb/descent and ultimately the time taken/fuel burned to complete the flight. Could you please share a video of this happening? Please note that for Managed mode to work properly, the INIT A/B pages need to be filled in with all the required data pertaining to Weights, Fuel on Board and CG. Additionally you should fill in the PERF pages as well for both TakeOff and Approach. Typically while you are in managed mode, all you need to do is dial in a lower altitude and PRESS IN the ALT SELECTOR KNOB to revert to a managed descent/climb mode. On descent, it will initially target 1000fpm vertical speed until it can intercept the calculated vertical profile and then descend accordingly on it. There are certainly improvements to be made with regards to the LNAV/VNAV which we have already incorporated into the A300, and intend to similarly work out for the A320Neo v2. However the currently implemented solution is still more than adequate and has been pretty good at observing constraints from experience. There may be rare instances of deviation, for which we appreciate screenshots/videos highlighting the issue which we can fix. So, a screenshot of scenarios where you're noticing this would be appreciated. Showing both the MCDU as well as the PFD/ND in all these instances. This is not an issue I've particularly seen in the many hours of flying this aircraft. Yes, the sequencing of next waypoint is a bit too early currently and this will be fixed in a future update to LNAV/VNAV. I'm not entirely certain what could have happened, but this is not an issue we can reproduce on our end. Nor has been reported by anyone yet in the many hours of testing internally, externally and finally publicly via the SU15 beta and since release. Thanks!

Hi @DeMBaSs The current focus is to release on PC first, same as with the A300. At later stages of development we'll also look into bringing these to Xbox. Ultimately it will come down to whether the hardware can still provide a great user experience that we'd like to provide via these complex simulations of the A350, and later A380. Thanks!

Hi @Kiwiviator As of right now, you need to point the iniManager directly to your community folder for the downloaded scenery to work automatically. If you install them to any external library/folder, then you will need to use a tool like MSFS Addon Linker to setup a symlink for them into your community folder. We will be adding the ability to define custom library/folder locations in the future with "V3" of the iniManager. For now however, having those sceneries in the community folder (directly via iniManager or through a symlink via MSFS Addon Linker) is the only way. Thanks!

Hi @Dani0100 Yes. As mentioned in the accompanying post, 3D Art Focus: Immersive Details & Dynamic Wear & Tear section, here: Also please take a look at the A350 Development FAQ here: Thanks!

Yes this Z-fighting issue is known and will be addressed next update. Thanks!

Hi @Adel Haiba That sounds like a WASM crash. Can you please share a screenshot of the page where it happens? DES FORECAST? Also is this happening consistently, every time you go to this page or only once in a while Thanks!

Thanks, will share with the team.

Hi @chaser911 There are no reported issue with steering on the A300, either internally or through the 50+ tester's systems it has gone through in testing. Common causes for steering issue include: Control Bindings Issues - Rudder/Steering Axis: Either of the two have been been bound to controls not intended. Please check your controller settings to ensure it is only assigned to buttons/hardware you want to control rudder/steering. Differential Thrust Input - In case you are using multiple axis to control each engine independently, please ensure that the thrust is being applied uniformally across both engines. Any difference in N1% between the engines can cause you to veer to the left/right. Differential Brake input - Brakes Axis/Buttons: Either of the two have been been bound to controls not intended. If you are using Rudder Pedals with toe brakes axis, please check their deadzones as erroneous triggering of brakes can also cause you to veer left/right. Noisy Control Inputs - Please check all your axis are properly calibrated and there is no "noise" in those controls that may be adding unintended control inputs. AI Assists - Please ensure all assists are disabled in the Assistance Options. These can cause conflicts with flight controls and AP functions on our planes. Thanks!