richboy2307

Hi @Bald kelp There is no such issue on the plane currently, nor been reported by anyone else before. After landing, you need to tap on your brakes to disabled the AUTOBRAKE. Please confirm you have disabled all AI Assists (Options > Assistance Options > Piloting). Also ensure you do not have any conflicting keybinds for parking brake/brake that may be causing issues. Additionally, ensure the chocks are not enabled from the EFB. If you are still having issues, please share a short video clip/screenshot of when you have the problem showing your entire cockpit (Overhead, Front Panel, Center Pedestal) Thanks!

Hi @rem31, English only please on the forums here. You simple hover your cursor over the SPEED SELECTOR or HDG SELECTOR knob, and press A button to interact with it. Then follow the on-screen instructions to adjust, and finally press B to quit. Also as mentioned above, you must have filled in the require information on the MCDU for MANAGED mode to work. Otherwise the AP will only work in SELECTED mode. Thanks!

Hi @Trane For your example of Runway29 at CYYC, if you look at the approach plate you'll note that ILS (IAQ 110.9) does not have any DME associated with it. This is why you see 0.0 on your PFD. Instead the approach uses a separate source for DME (IGY 110.55), and you can see that mentioned as the distance read-out for all the corresponding waypoints as well. So in this scenario, you'd tune the RADNAV page on the MCDU as follows: - IAQ/110.90 in the ILS/FREQ section - IGY/110.55 (enter it as /110.55) in either VOR1/VOR2 section on the top (as you prefer) Once you see that, enable VOR on the Glareshield and you will use that DME on the bottom left/right of your ND instead. I am not noticing this issue, just tested at CYYC RWY 29. Please ensure your RADNAV page is setup properly, that you arm APPR and intercept the glide from below the glideslope (it won't capture if you're already above it). Are you using Default or Navigraph Navdata? Also are you using any sceneries for the airports where you notice this issue? Also ensure your sceneries are up to date and do not have any add-on affecting all the airports, that may be causing conflicts. Thanks!

Hi @danlee957 Try again with the latest update. In case you see this again, please share a screenshot of it, along with where it happened (which gate number/Terminal) Thanks!

Noted. Thanks for the suggestion.

Hi, Are you using any addons like FSRealistic? That is known to cause issues for manual entry sometimes, the only fix being to exit to main menu and restart the flight. If you are having this issue on every flight, then please try with an empty community folder: rename your existing one to '_Community' whilst testing. When finished testing, delete the new 'Community' folder and rename your old one back to 'Community' If you do not have this issue with an empty community folder, then it is likely some addon that is causing conflict. Most likely culprits are outdated liveries or outdated version of Horizon Simulations 787 addon. Thanks!

Hi @goodmanp Its up to the vendors themselves to send over their latest products/updates to the different stores they sell their products through. But I'll check with the team and get back to you. Thanks!

Hi @BillM Are you using Navigraph or default navdata? Also can you specify which Airport + Runway + SID/STAR/APPROACH combination you had problems with? It is the correct behaviour to receive a NOT ALLOWED warning when trying to remove a F=PLN DISCONTUNUITY which has MANUAL entry above it. So you need to erase the MANUAL entry first . Once you have CLR on your scratchpad, clicking the L LSK next to the MANUAL waypoint should get rid of it. I'm not noticing any such issues on my end. Below is a video of KJFK DEEZZ5 SID out of RWY 04R with Navigraph Navdata: 2024-07-09 22-43-06(1).mp4 Also if you're on PC, please ensure your A320Neo V2 is updated to the latest version (1.0.17) in the Content Manager: Also lastly, if that doesn't work. Please try to delete the contents of this folder, as that will force the plane to re-compile the WASM next time you load it. Just to ensure it wasn't corrupted on initial launch: Steam Version %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store Version %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Thanks!

Ensure all the AI Assists are disabled (Options > Assistance Options > Piloting) as they will affect the AP functions. Also do note that the A320neo V2 uses the new Computational Fluid Dynamics (CFD) aerodynamics model in MSFS, so it generally will be less "stable" compared to other planes as it interacts with the environment better and takes lot more factors into account. You may also want to reduce the Turbulence to MEDIUM or LOW if you feel it is too much for your liking. Me and countless other users are using this plane with the Thrustmaster Airbus Stick and Throttle Quadrant without any such issues. Please ensure again your AI assist are disabled as shown above. Also please ensure you have calibrated your throttles properly in the EFB Options page using this guide: This is normal for a de-rated take-off, as our EFB Take-off Calculator is designed to calculate for a greater second-segment climb rate, rather then get off the runway as quickly as possible. Thanks!

Thanks, feedback is noted.

Yes they are factored into VNAV and EFOB/ETA calculations.

On the top left corner, select your Name to access the iniManager settings. From there make sure the paths are all correct, and then hit the SCAN NOW button for the desired sim. That will force the iniManager to scan the defined folders to see what is installed and should update their status accordingly. Thanks!

Should be good again now @WernerAir

It was working for a bit. But we're messing with stuff to see whats up. Team's on it. Standby!

Should be resolved now. Try again.

Thanks, the team is already notified. However, due to timezone differences it may take some time to resolve. Will rectify ASAP.

Hi @Green97 Not supported currently. Under consideration, but no timeline/guarantee of this. Known bug. Already fixed for next update. Also already addressed. Improvements to this coming in the next update. Thanks!

Yeah that is just a WebASsembly Module (WASM) crash on load. When the WASM crashes, all code that uses it will basically stop working - end result being that systems freeze/stop responding. Anything NOT using WASM will still continue to function. This was designed by MS/Asobo such that if the code crashes, it will only be contained to things within the WASM, and not CTD the whole sim itself (like in previous simulators). However not all WASM crashes are due to the aircraft's code itself, as sometimes its to do with how the sim interacts with WASM, and where it stores that data specifically on memory. These are hardest to fix as they are difficult to reproduce, and are specific to each client's memory. Anyways, based on testing so far, next A300 update should have some workarounds/fixes that improve WASM stability. However, whenever a WASM Crash happens, only way to resolve is to restart the flight as that resets the WASM. Thanks!

SAT is the Static Air Temperature, OAT is the Outside Air Temperature, and both are basically the same thing. This is the temp that will be shown on your OFP's WIND INFORMATION section, and also what you enter into the MCDU. So using the same example from above: If I was entering the info for waypoint TUDEP, and cruising at FL330, I'd input -50c as temp, and winds 218/80 as shown in red. Thanks!

Have you tried with an empty community folder (nothing but the A300 in it)? Just to rule out some conflict with another add-on or lighting mod? Also perhaps try to use this lighting mod? https://flightsim.to/file/66466/inibuilds-a300-external-lighting-fix

Hi, Unfortunately that is a sim limitation. MSFS only allows one operational jetway per gate, no matter GSX or otherwise. The others are simply static models. Thanks!

INIT B page is only accessible when engines are off. It is important as that is where you set the information about your Weights and Fuel Onboard. So I would try starting from an ON APU panel state, fill in the information, then start your engines.

Glad its resolved. Thanks for reporting back. 👍

Its hard to say what happened without actually seeing a video, as it may have been the right mode wasn't armed, or the intercept angle was too much etc. The proper way to Go Around is to hit the TOGA button, which would kick off LAND on the FCU. So if your LAND mode remained engaged, thats probably where the problem happened. Only A/THR should remain when you hit TOGA or executing a go-around: On the FMA you would see is: On the MCDU, it remains in APPROACH mode, and remains so for the rest of the attempt: Here is me re-establishing, still on APPROACH mode on MCDU, and LAND re-armed: Thanks!

Hi @SimPilot7091 Please ensure you do not have any conflicting bindings. I am also using this with the BravoTQ, with below assignments and not noticing any issues with the gear. Also ensure you do not have any AI Assists enabled (Options > Assistance Options > Piloting). If you are still having problems, please record a video clip of the issue and share here. Both internally showing your ECAM and Gear lever, and also external showing how it extends/retracts. Also provide a screenshot of your bindings. Thanks!