richboy2307

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 @Deer-in-Motionwas this in external view (spot camera) or via Drone Cam? Also Pax or Freighter variant? 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!

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).

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.

Thanks, yeah this is an issue with the GSX profile as the location defined in them doesn't match the 3D model of the VDGS. Bug is logged, thanks!

Hi @ricardo Thanks for the suggestion. Will share with the team. In the meanwhile you could try to use the flood lights/dome lights to help combat this to some extent, as that helps to reduce the contrast and thereby lessen the "Eye Adaption" effect that MSFS has. Thanks!

Hi @RedBenny Could you attach a screenshot or short video clip of when you notice this issue? Can't say we've seen this internally or reported by other users. Such media will better assist to find clues as to what is going on. Thanks!

Hi @diogocec, The ''Rudder Controls Tiller'' is bound to 'Rudder Axis' itself (red box), and not the yawing commands (green box) which is what is used by default sim keybinds. You could also try to assign buttons to the tiller itself, such as 'INCREASE STEERING' and 'DECREASE STEERING' keybinds if you want to control it separately to the rudder. Thanks!

Hi @falcon71 Thanks, this is a reported bug and will be addressed in next update. Thanks!

Hi @falcon71 It depends on the charts, some are pre-programmed on TRUE courses in the database, but as a general rule of thumb it is calculated with MAGNETIC courses as default. The drawing on ND is equally done on MAGNETIC course, however the AP will make corrections taking into account things like wind. However it does seem like there may be some discrepancy here based on the MAGVAR, so I've shared with the team for further investigation. Thanks!

Hmm. @Superdraco2 Can you please confirm what was your FPS at the time you noticed this LNAV tracking issue? You can check your FPS in the sim by enabling Developer Mode. Then from the Devmode Toolbar on top, select Debug > Display FPS. Please share a screenshot of the FPS window during the time you have this issue. Thanks!

Yes, the stuttering can be caused by bad/missing Bing data. MS were temporarily having a Bing Data Outage at the time, but should be resolved now. Thanks!