richboy2307

Hi @mrmike1979 You can go to the EFB and disable the automatic door arming features. (Settings > Real Door Arming - OFF) Also once deployed, you can reset it via the maintenance menu ( EFB > Aircraft Maintenance > Reset Slides) If none of those work, you can also try to delete the contents of this folder. Next time you restart the sim and load into the A300 it will recompile the WASM module, just in case it was not properly compiled on initial load. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 Thanks!

Hi @B747-8f both work, as we monitor support tickets and these forums to look for reported issues. Just post them in the appropriate category (Systems / Model & Texturing / Sounds / Other) here: https://forum.inibuilds.com/forum/391-support/ Thanks!

Hi @Geno63can't say i've noticed this. Is this happening only in the A300 for you? Also are you using any additional addons that may affect ATC services?

Thanks, i'll pass your feedback onto the team.

Hi @MitchellAA300Can you confirm you're having this issue on v1.1.1 of the A300 as well? There was previously an issue where the lights could not be seen on certain LOD levels, but a fix was pushed for this in that version. Please let us know, thanks!

Thanks for the report, this is noted.

Hi, thanks for the feedback. I'll pass it on to the team.

Hi @mjc2407 sorry can you please provide a screenshot or video of the issue? I'm not quite sure I understand what you're seeing. Thanks!

Hi thanks for the report, needs further investigation but we'll look into it.

Hmm, are you using any assists or auto rudder that could be causing issues? Or is there some imbalance in between left and right thrust/fuel load that could be causing constant correction? The only other report we've received of this issue in the past the user claimed the issue "fixed" itself after a reinstall. While I'm not certain that is the issue here, it wouldn't hurt to try? Thanks!

Hi We are not able to reproduce these issues on our end with v1.1.1, even with Navigraph navdata. Could you please try troubleshooting such as : Do a flight without any other addons, only the A300 in your community folder, to see if there are other addon conflicts. Delete the contents of your "work" folder after a fresh re-install to ensure no corrupted data: Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 Make these flights in default "White" or "Inibuilds House" liveries to eliminate any "bad" livery files causing conflict And when you do encounter the issue, report with: Screenshots/Videos of the failed systems or anomalies you notice Write-up of the things you did just prior to the crash (e.g. what you clicked, what you interacted with, what control inputs you gave etc) Cirtcuit route information & navdata used (E.g. Navigraph data - KMKE/01L YOUNT KMKE/01L ILS) Any extra things you noticed just before to the crash (e.g. momentary sim-freeze, abrupt winds change, sudden weather update etc.) Thanks!

Hi this was removed from xbox version due to performance issues reported by users. Thanks!

Hi @Trevor can you please provide a screenshot of this issue? I have just loaded up at a gate (B25) in FACT, on A300 v1.1.1, and selected RWY01 for departure, and selected same on the EFB, yet I am not seeing this issue.

There had been interim issues with Simbrief import on Xbox, which should be resolved as of SU15 public release. Please let us know if you still experience such issues since, on v1.1.1. Thanks!

Please report if anyone has had this issue on v1.1.1 and SU15 update. Thanks!

Hi as mentioned above, there have been changes made to account for the new ground physics model brought by in SU15 which allows for better friction and inertia modelling, so you need to be slow enough (Below ~10 Kts) whilst also providing enough power and using differential braking where necessary to make turns, especially 90 degree ones. As for the steering controls, with the EFB rudder till option enabled, the tiller should be controllable by the same axis assigned to your rudder. To troubleshoot, you can disable this option, un-assign your rudder axis, and assign that hardware axis to 'Nose Wheel Steering Axis' instead in MSFS Control Options. See if you are able to turn the nosewheel and taxi using that. If yes, then it is a case of the rudder steering axis not connecting to tiller properly. There are no issues seen regarding this in our internal testing or via the beta testers. However you may try instead to close the sim, clear the contents of this folder, then reload the sim and load into plane, reconfigure the settings and try again. It will regenerate the files and re-compile the module, to eliminate any faulty compilation on initial loading. Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a300-600 MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a300-600 Thanks!

Hi, thanks for the rerport. As stated before, we have not been able to reproduce crash-on-load issues on our end or via our testers. As such we need users who are facing such issues to engage in additional troubleshooting on their end to help us resolve this issue. Please refer to the steps mentioned in this post : Thanks!

Yes feedback/requests regarding this are noted internally. Something we may look into in the future, but no guarantees. Thanks!

Hi what was the route used when you noticed this? I am not able to induce any WASM crashes by simply adding a STAR/APPROACH proc to an ALTN airport on the MCDU FPLN page. Also please provide the Navdata source used (Navigraph or Default). See attached bits from FCTM. Thanks!

Thanks for the report. We would certainly like to fix all the sources of WASM crashes. In order to tackle this better, we need more details so we can try to recreate the circumstances that lead to your crashes, and try to identify the root cause. So can you please provide more details such as: - Is this issue specific to any engine type/variant? - Is this issue happening after SU15 release? - What was the route, and what specific action lead to a crash (what did you click or input you gave prior to noticing the crash)? Thanks!

Thanks for the report. Can you confirm the navdata you are using?

Thanks for the report, logged.

Hi, Thanks for the the report. Sounds like a WASM crash. Can you please detail how you changed the destination? Was it by entry KSDF/KSFO in the FROM/TO field on INIT page? Also please share what navdata source (Navigraph or Default) and the original flightplan (e.g. VHHH/25L BEKO2B BEKOL A461 IDUMA IDUM3B ZGGG/20R) Thanks!

@Erik Thanks again for your post. The team has spent a load of time testing different combinations to make it available to no avail. It used to be straightforward (anything without a jetway) but now it seems something has changed since about SU14. In short, the ramp system is bugged. We're aware of the issue but don't have a solution at this time. The issue occurs whether the parking is set to GATE or RAMP of any size.

Hi, Just checked in MSFS v1.1.1, I am able to define a new waypoint using below method, and able to recall/use the newly defined custom waypoint on FPLN page using the defined identifier With regards to direct entry of LAT/LON WPTs on FPLN page, this is currently not implemented and results in 'RUNWAY NOT IN DATABASE' error message instead of the LLXX WPT entry (similar to PBD WPTs). The feedback is noted and we'll look into it. Thanks!