Jump to content

richboy2307

Moderator
  • Posts

    1511
  • Joined

  • Last visited

  • Days Won

    79

Posts posted by richboy2307

  1. 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!

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

  3. Hi @agardezani

    Thats the Aerodynamic Visualization (CFD). You can disable it under Options > Assistance Options > User Experience:

    image.png.de4d703e756634993057a958ddb45ab8.png

    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.

    image.png.dbd7e50ef0ca46c2c73e5e0f59b2bb37.png

    Thanks!

    • Like 1
  4. 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!

  5. 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)
      image.png.859e3b9bf59934b073595049b84fc198.png

    Thanks!

  6. On 6/11/2024 at 3:18 PM, Bazz said:

    So wondering if you can let me know what you entered on the arrival page, because that changed a lot which makes sense.

    The only thing I had done was select RNAV-W 14 via VAPMU transition.

     

    On 6/11/2024 at 3:18 PM, Bazz said:

    However it also dropped IRPOD of the FPLAN page, interesting, it seems it should be where "LIM" is

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

    image.png

    On 6/11/2024 at 3:18 PM, Bazz said:

    It also wanted to change the cruise altitude to FL10 so I went in and changed it back to FL4

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

    image.png.b04244527fbb229080e936f29d5dc4c3.png

     

  7. 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)
      image.png.8cc898bf32a908286eafaa778f7cff40.png
       
    •  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.
      image.png.b8cdcdd40aa8ce64690768ca87783784.png
       
    • 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!

    • Like 1
×
×
  • Create New...