Jump to content

Rodolfo Becerra Vargas

Member
  • Posts

    4
  • Joined

  • Last visited

Rodolfo Becerra Vargas's Achievements

1

Reputation

  1. Yeah... good luck solving your issue
  2. @C. Schaffhausen Thank you, I have tried clearing the WASM folder multiple times and even a clean install of Windows very recently (24th of March, 2026), it hasn't worked. About the package reorder tool, I don't use the package reorder tool for any of my addons, including the A350, I allow the respective installer to put everything in my Community folder as it defaults on most installers. Also, before the issue and during the issue, I have never had a Navigraph subscription or any Navigraph software besides Simbrief. When the issue began I uninstalled Simbrief and any software that interacted with MSFS (except the installers) and still the issue has not gone away. And in my new clean install of Windows, I do not have any other software besides the installers that interact with MSFS. The addons I have install besides the Inibuilds A350 (From iniManager), are: Aerosoft Paderborn Airport (From MSFS Marketplace) Drzewicki Design Radom (From MSFS Marketplace) Everything included in my Microsoft Flight Simulator license and additional free Asobo and Microsoft Aircrafts, Missions and World updates (except the Dune and Halo aircraft) FlybyWire A32NX (From the FlybyWire Installer) 4 flightsim.to airports Microsoft ATR Inibuilds Milwakee (From the iniManager) I have tried the ini A350 with all of these addons not installed right after my clean installation of Windows and the issue is present no matter at what airport I spawn the A350.
  3. The remaining photos, confirming the default MSFS is current and different to what the ini A350 is using
  4. As the title says, I am unable to use the "Sim Default" Nav Data or at least confirm I am using it. On the OIS I have the "Sim Default" Nav Data selected, and on the FMS is saying I am using SJ6192002 which is ARINC 2303 revision 1. I can confirm this because on my WASM file fo NAVDATA and OIS part of settings at 3RD party says "Cycle:2303R1". This was not the case a couple of months ago, and it isn't on other planes (Default MSFS 2020 A320 neo v2 and Flybywire A32NX). I have cleared my WASM folder multiple times (in fact, 3 times just today), and nothing has resolved this issue. This error begun when I wanted to see what would happened if I switched the Nav Data from "Sim Default" to Navigraph, as I was thinking of buying a Navigraph subscription. Ever since then this issue has not disappeared. I have even re-install Windows 11 from scratch 2 weeks ago, nothing has fixed the issue. I need your help in the following way: 1. I need to know if this is a visual bug or a bug that is preventing me from using the default msfs 2020 Nav Data. 2. I wish to know how to fix it. Below I am attaching: 1. A screenshot of how the problem is looking (A350 FMS and OIS 3RD Party section selected) 2. My WASM folder through a link to my Google Drive (https://drive.google.com/file/d/1FgFJZd7fqgmlQ0X6dgqWOyYdmaDsi-TK/view?usp=sharing) On the following post: 3. A screenshot of the MCDU of the default a320 neo v2 MCDU confirming ARINC 2603 is current in my sim 4. A screenshot of the MCDU of the FlyByWire A32NX MCDU confirming the default sim ARINC is the one provided by Microsoft and it is ARINC 2603
×
×
  • Create New...