richboy2307

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!

Thanks, bug is logged.

Hi @meierblom In 'Legacy' interaction mode you can push/pull the knob based on the small arrow that shows up near the top and bottom of the knob. Left click on your mouse will move the knob in the direction of arrow shown (push for up arrow, pull for down arrow).

Thanks for the report, shared with the team.

Hi @Lars Erik Axgren Please see here:

Hi @WallyWalt What you are noticing on the plane is actually correct for this aircraft type, as you can see in this IRL power-up video from an A320. Thanks!

Hi @Henni100 / @Rudderduck It seems it was missed out in the last update and needs to be re-uploaded with the new version. In the meanwhile please find the file attached below. Thanks! ENKB_GSX Profile.zip

Thanks for the reports all. Next time this happens, could you guys go into developer mode and check if there is any WASM module crash? If yes, please copy-paste the message here so it could help to narrow down the faulting module. Instructions on how to access the console: Enable developer mode (Settings > General > Developers > Developer Mode - ON) Open the console (Press the ` key on your keyboard or from the top DevMode toolbar via Debug > Console) On the search bar type WASM, and look for error messages (marked with red crosses). YOu can use the filters on top (red box) to make it easier to find them. Look for error messages such as 'WASM: Exception...' or 'WASM: Module...'. You can click on it and hit the 'Details' button on the bottom to get more information. The WASM crashes related to the a300 will mention 'inibuilds-aircraft' or 'a300' in them. Press the 'Copy' button to copy the selected message to your clipboard, and then please share them here, such as example: WASM: Exception c0000005 in gauge Systems in module vfs://inibuilds-aircraft-a300-600/SimObjects/Airplanes/inibuilds-aircraft-a306f-pw/panel/inibuilds-A300.wasm As we haven't been able to reproduce this issue internally or via the testers as yet, we'd appreciate this information to help with the investigation. Thanks!

Thanks for the write-up. I've shared with the team for further investigation.