2505 BLV Sim Freeze

Navigation Data General MSFS Data
1

Hi all,

Issue I’ve noticed with the latest cycle, is when I’m heading towards the BLV VOR (Bilbao) my sim freezes and I have to force close via task manager.

This happens after passing the DGO (Domingo) VOR, heading north towards BLV.

After the first time this happened, I tried again, an the sim hung in the same place.

I did a fresh sim install (all addons uninstalled then FS20 uninstalled and all remaining files deleted).

Attempted the flight again today, and had a different flight plan generated, but still passed the BLV VOR, where my sim yet again hung, leaving me to force close via task manager.

This happens in the iFly MAX, flying the following route.

LEMG/13 BLN5H BLN N865 VTB N867 BLV P87 BELEN DCT DIDIG UP87 MOKOR UN873 OLEBA DCT ROGPU DCT DIKRO UM185 TELTU TELT1N EGGW/25.

2

Hi,
Have you tried the route in any other a/c to eliminate that this is a core sim issue?

Thanks for your report and feedback
Richard

3

Hi,

I’m not sure if this is the issue, but I’ve just tried this fight in the INI A350

Nav Data for the INI A350 is downloaded direct to the aircraft, yes?
It currently has Navigraph Selected in the OIS, and is showing 2505 as the in use database

However, trying to fly the route posted above, for some reason it wants me to fly back on myself, which doesn’t reflect what SimBrief displays.

Ignore is discontinuity as this is because I was trouble shooting the plan, to make sure i entered it correctly, and every time I enter BLN N865 VTB N867 BLV, i get that weird routing.

NUVUXWZ
NUVUXWZ2560×1440 367 KB

However, with the iFly MAX, it reflects the route displayed in SimBrief, with no odd routing, but my sim crashes every time when nearing BLV.

Ive used the Navigraph hub to update my sim data to 2505, and the iFly MAX to 2505, whereas the INI A350 is updated via the OIS, yet both aircraft display entirely different routes when entering the exact some route.

For some reason your data (2505) for the INI A350 as an additional two waypoints, IDEVU & ANZAN on airways N867, whereas 2505 on the MAX, as installed directly from Navigraph Hub, doesn’t.

Maybe its this disparity between the same data, but for separate addons, thats causing the crash?

mX4WZt1
mX4WZt11468×1107 357 KB

pFT7iA0
pFT7iA01473×1100 319 KB

As you can see, entering the exact same route into the iFly, produces a different set of points, which reflects SimBrief.

lbzOpgV
lbzOpgV2560×1440 436 KB

4

Further adding to this:

As you can see in the images, one has sim default selected (which as far as i am aware, is 2505r1 as i updated the sim base package via navigraph hub) and the other has navigraph selected, yet both produce entirely different routes.

Imgur

Imgur

Imgur

5

I’m not sure if i should create a different topic for this, but I do believe there’s an integration issue between Navigraph and the INI A350, as on some occasions, when entering data into the FMC, such as Departure and Arrival, the data vanishes

It would explain the disparity in nav data and the inability to enter data

As mentioned here

6

Sorry, when I haven’t explained it clear enough …

I have tested thhe route with the in-game A320 (default stock aircraft) and here, I haven’t seen any CTD or freeze at this point. I have now tested this with the iFly last night and also here, no issue, no freeze somewhere …

I don’t use any 3rd party sceneries or mods sonewhere. Only the 3rd party aircrafts, our apps and our data.

Thats my testing result … I don’t see any issue sorry.

Cheers
Richard

7

Ok no worries.

But as you can see in my screenshots, there’s an issue between the data packages you provide for the default sim + iFly, and the one provided for inibuilds a350.

Its a separate issue that needs addressing

8

Hi,
When you mean the strange routing on the ND in the Inibuilds A350, please inform Inibuilds about this behavior because they “draw” the segments we offer. You see in the iFly that the segments are correct and interpreted correctly from iFly, so it is an A350 interpretation issue that can only be fixed by Inibuilds, not by us; sorry.

Cheers
Richard

PS: next time, please avoid mixing issues - it is easier for all other users and also for us to understand and possibly find a solution for such issues - thank you very much

9

I’ll post on ini forum about the weird drawing, but I’m concerned they’ll refer me back to here.

Only because the nav data that is drawing the odd flight path, is Navigraph data that is downloaded directly to the A350 via the onboard OIS.

And the reason that it is drawn weird, is because it contains incorrect waypoints.

10

No, we don’t draw anything; we offer only the procedure sequences in the database. The add-on developers will draw/interpret these sequences.

Further, you see conditional waypoints and not real waypoints, which means these waypoints will be calculated by previous and/or next waypoints, precisely the Interpretation.

When we would offer the wrong waypoints, you would also see this in the iFly because all datasets use the same source behind them.

Don’t get me wrong; I will not pass the responsibility to Inibuilds, but that is a clear issue on their side, sorry.

Cheers
Richard

11

Hi,
Just an update on this. I have flown the exact flightplan in the iFly, and I have no freeze nor CTD on the way to Luton.

Used no 3rd party scenery, the latest iFly version, AIRAC 2505, and live weather.

So, at least I can’t reproduce it, sorry.

Cheers
Richard

12

I’ll give it another shot in the ini a350 using the sim default data which is also updated to 2505, and see how it goes.

It’s just odd that the sim crashed 3 times at the same location, and one of which was after a fresh sim install, whilst flying the ifly MAX.

The only addons I have for FS2020 are;
GSX Pro
INI Builds Luton
Macco Manchester
iFly MAX
INI Builds A350
Navigraph subscription.