richboy2307

Hi @Manchild Please try to adjust the volume of 'Warnings', as well as play around with the 'Headphone Simulation' setting to your preference. Thanks!

Hi @SimPilot7091, can you confirm the weather conditions at the time? Was there any excessive/sever crosswind? Also ensure that your rudder trim is centered, and that there is no conflicting bindings for either Rudder or Rudder Trim that could be causing issues. Also ensure your thrust is not asymmetric (i.e. one engine having thrust than the other). Lastly ensure you do not have any AI Assists enabled (such as autorudder) in the Assistance options. Thanks!

No estimates but the team is working on an update, which is currently under testing. Primary focus is improving stability and performance, but will also include a slew of other fixes. Thanks!

Thanks, logged for further investigation!

Hi @Phantom Pherret Thanks for your purchase! You can contact the developer directly via email: Tienvip26842@gmail.com with your suggestions and feedback.

Hi @Farish H Can you please elaborate when you had this issue? What did you click/do before the MCDU got stuck? We need more information to understand what triggered the MCDU to crash/get stuck so that we can fix it.Thanks!

Hi @Nimrod Team's aware and working on this. If all goes well these fixes might make it to next public build. Thanks!

Hi @flyer23 We do have a new update for the A300 which will hopefully address the issues you are facing. Enclosed is a post shared on our discord. Please try that update (once available) and do report back if you still face such issues. Thanks!

Team's still working on it. Thanks!

Thanks, taxiway sign bugs are logged.

Hi @BottleCap LAT/LONG waypoint entry is not yet possible on the FPLN page in the current public build but will be added in the future. It is also a customer option IRL, meaning not all a320neos would be able to do it. The definitive way is to do it via the "Waypoints" menu. Thanks!

Hi @akloz Please try to delete the contents of this folder. On next launch it will regenerate these files: Steam: %APPDATA%\Microsoft Flight Simulator\Packages\microsoft-aircraft-a320neo MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\microsoft-aircraft-a320neo Thanks!

Ah my bad. We'll take a look, thanks!

Yes, and i've written above how it works in legacy interaction mode. There are no known reports of not being able to interact with the plane in this mode, and we do not see any issues with it on our end either. Thanks!

Hi @MarcusVT Turn on brake fans, delay takeoff in case of hot brakes.

Hi @Airtours Can you please share a screenshot of when you are having this issue? Please also share your full flightplan, including the SID you were selecting. Also please confirm are you using default or navigraph navdata? Thanks!

Hi @achelous, from your screenshot I can see on the right side MCDU that you have activated APPROACH mode on the PERF page? That is why if you look on the bottom left of your PFD, you'll see the '121' in pink, as the AutoThrhust is targeting the landing speed (which is 121 in this case). You do not need press "ACTIVATE APPR PHASE", normally it will reach that mode automatically closer to your destination.

Hi @agardezani Thats the Aerodynamic Visualization (CFD). You can disable it under Options > Assistance Options > User Experience: Also in the weather settings from the toolbar, make sure the "SHOW 3D THERMAL" is disabled. There is an MSFS bug that automatically enables 'Aerodynamic Visualization (CFD)' on its own when this option is enabled. Thanks!

Hi @Deer-in-Motionwas this in external view (spot camera) or via Drone Cam? Also Pax or Freighter variant? Thanks!

Sorry, it is not for sale anymore. Thanks!

Hi @achelous / @Joshua Welton What you're experiencing is called Avionics Black Out (ABO). This is a feature of the Xbox version of MSFS2020 that turns off glass avionic displays when the Xbox is running out of memory (RAM), in order to keep the other parts of the sim running. While all efforts have been made to optimise the A320Neo V2 for its memory footprint, at the end of the day this is an issue with Xbox's limited memory and largely for MS/Asobo to improve upon. Thanks!

Hi @Rick1486 I suppose this is the "STOP" sign you are referring to. This isn't tied into GSX or any other VDGS system, but is simply a static asset, the light on which comes on whenever night-lighting is activated. 2024-06-20 23-17-40(1).mp4 Thanks!

Hey @Rocket18 As you can see in this video, the jetways are certainly animated and functional normally. Are you able to request the jetway using the EFB controls on any aircraft? Ensure you do not have any conflicting GSX profile for KMIA(Folder location: %APPDATA%\Virtuali\GSX\MSFS). Try to disable the KMIA Jetways config from the FSDT Installer as below (remember to hit apply after making changes) Thanks!

The only thing I had done was select RNAV-W 14 via VAPMU transition. The waypoint IRPOD was already in my flightplan as the last enroute waypoint (as seen on simbrief screenshot). Selecting a procedure simply adds the points starting from VAPMU after it. IRPOD remains as a waypoint before it. (Ignore the EFOB - that is just because I was not at the departure airport when I took this screenshot). As Azlog mentioned above, this is likely because you dialed 10,000ft on the FCU and pushed in the knob at some point. As the new managed altitude was higher than previously planned CRZ Alt, it will update to the new CRZ FL as entered on the FCU (10,000ft in this case).

Please use this link: https://discord.gg/jE8neVcUZr It is as shown on their website: https://www.rwprofiles.com/ Thanks!