Jump to content

Matteo Spacca

Member
  • Posts

    66
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Matteo Spacca's Achievements

18

Reputation

  1. Any solution for this? N
  2. There are several topics on the navigraph forum. This has to do with 3rd pary airports not adhereing with new new packages prioritization introduced with MSFS2024. It’s not 100% clear to me but scenary developers need to update their airports to be compatible with the new sim otherwise you may find missing/wrong fixes in approaches and departures. No issues with aircraft having their own Airac database like the Fenix or the A350 but with default aircarft you may encounter issues
  3. Thanks. I figured it out this morning
  4. Is this related to one sim or happens on both? I had a few flights in 2020 and 2024 but did not experienced any issues with frozen display/WASM Matteo
  5. I believe it is just a matter of personal preferences. but for sure IRL you can here engine whine and nose gear bumps
  6. Good question. I can barely here them from the cockpit
  7. Unfortunately it doesn't work
  8. I'll try. Thanks
  9. God afternoon, Using Thrustmaster TCA Airbus. I calibrated multiple times but the thrust doesn't go into reverse. Reverse on axis is clicked and also tried multiple dead zones values. No issues with MS2024
  10. There are issues with addon airports and the LIDO/Navigraph database. I believe you are using a 3rd party VHHH. IN this case go to the community folder and add an "A" in front of the name of the scenery folder. This will solve your issue. Note that this trick doesn't work for all 3rd party airports SID/STARS Matteo
  11. This is because all HH fixxes in the sid/star are populated with longitude/latitude equal to 0N/0E
  12. I also had the issue with VHHH. The “A” trick solved the issue in this case. For example this trick doesn’t work for all the MC fixes in LIMC
  13. There are issues with Navigraph/MS/ASOBO/Lido at the moment. Fisrt workaround is to add an "A" in front of the scenery name in the community folder but it doesn't always work for me (at least not for every airport). Navigraph is aware of the issue and already opened a ticket with MS/Asobo Matteo
  14. You have it correctly installed but I believe the FMC is still showing/loading the stock LIDO data (AB49012001)
×
×
  • Create New...