A LOT of us have found out that LAX, ONT, and other surrounding area airports, that once you enter in the rwy in the FMC departing out of one of these airports it freezes the entire plane.
" So after a bit of testing I can confirm if I stay on the default navigraph db all goes normally. If you update the ifly airac with the navigraph hub, the fmc freezes as soon as you press DEP/ARR out of KLAX."
Hi,
Thank you very much for your report. iFly, and we are still in contact with this issue. We are currently analyzing the situation and the delta between the default and current cycles. We do our best to support iFly and vice versa, so please be patient. We will inform you here, when there is an update. Thank you!
Hi,
Just an update to this. We have tried to analyze this issue but without success. The procedures are different yes, but I haven’t seen any wrong coding in the data, which could be cause of this issue.
But we are still in contact with iFly and I’m sure we will find the culprit. Just to know you that we are still working on it.
I have the same but not with KLAX but with DTTJ as departure. Using the AIRAC which comes with the Aircraft however works, but than I use an outdated NAVDATA.
The NAVDATA which came with the IFLY, does not get me any errors, while I try to depart out of DTTJ.
The Updated Navdata, I get a constant freez after hit the Activate button after entering DTTJ as Departure airport and EBBR as DEST.
Using EBBR as Dest and selecting another Departure Airport works fine aswell. So at least something is wrong with DTTJ.
Maybe it helps you to find it with DTTJ as this aiport is quite small compared to KLAX and maybe much easier. However, meanwhile I go back to the old Navdata.
Further investigation:
Just tested it with default DTTJ. Crash aswell. I also copied the DTTJ (SID, STAR and SUPP] 4files out of the stock NAVDATA and replaced it on the newer AIRAC so that I get the actual AIRAC but with the old DTTJ files. Crash aswell. This means, I can use DTTJ ONLY if I use the default Dateabase which came with the plane and is more than 1 year old. Pretty sure there are other Airports not working beside DTTJ and KLAX.
Hi,
Thank you. The problem seems to be in the WPNAVAPT.txt file (here the file from the default cycle). All other files are okay. When you copy and paste the file from the default 2309 cycle, you will see that you can enter the dep/arr page on KLAX, DTTJ, … without any issue.
We are still analyzing this issue, but it´s definitely in this file.
so heres a question what file does it grab to display SID/STARs? ive gotten it to enter KLAX, then the RWY then after i press DEP/ARR thats where it freezes
WASM: Exception c0000005 in gauge System in module vfs://ifly-aircraft-737max8/SimObjects/Airplanes/iFly 737-MAX8/panel/iFly737-MAX.wasm
@NAVData so 2 questions what is the difference between KLAX.sid and KLAX.sidtrs files? and do you have the 2309 .sid and sidtrs files to upload as well. im wondering if it something to do with those files. specifically if 2309 doesnt have sidtrs file. its hanging almost trying to either figure out which file to pull or there is data that doesnt match, or it may be trying to pull both files too. thats what i personally think, because you can enter in the airport then any of the runways manaully, it hangs when trying to fetch the SID
the only problem with that theory is that DTTJ only has DTTJ.sid so it kinda brings us back a step…
it also could be that the ifly plugin is creating the airport maps from the sims databases via bgl and your guys navigraph nav dat vs the one for the specific plane but i also have no idea why they have it create airport maps and for what purpose. if im guessing here is a .map file that i think the plane generates, KLAX.map (7.9 MB)
as for example, it reads my PHX addon airport
bglFile=C:\Users[USER]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packages\Community\bmworldamsim-kphx-phoenix\Scenery\bmwamsim\KPHX_SCN.bgl
so @Swisspilot do you have an addon airport for DTTJ?
here is the relative path i am finding this at
“C:\Users\[USER]\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\ifly-aircraft-737max8\work\navdata\MAP”
Thank’s for your update. Indeed I can confirm that replaceing the WPNAVAPT.txt file is solving the issue. I also tried with the current DTTJ.SID DTTJ.STAR DTTJ.Supp and ONLY replaced the WPNAVAPT.txt with the old one. Even this works. So it seems as the culprit must be somewhere in that txt file? Kind Regards Patrick
okay awesome ill start to dig around a lot… thank god fo VSC. the odd part is that the airports we are having trouble with have no changes.
so i ran around the whole LAX basin area airports and the only airport who had any changes in 2410 was PSP. this is a very pesky culprit to find. almost like a needle in a haystack, because how can there not be any differences from 2309 and 2410 for LAX but 2410 will freeze the plane but 2309 wont at LAX. with the same 2410 SID/STARs files, and the rest of the nav 2410 data.
The only thing i can think of is an access violation like c0000005 suggests that the FMC might be trying to access a memory address that either doesn’t exist or is out of bounds, highly possibly due to bad data (e.g., an invalid waypoint or procedure), and or the aircraft itself doesn’t have the permission to access the 2410 LAX data. Somehow, which is oxymoronic, but looking at it that way it could be bugs in the code that can lead to improper memory access, which works with 2309 but changes in the 2410 data could make it fault
Hi Patrick,
Yes, the issue is somewhere an this file and we have identified what it could be but the tracing is very time consuming and therefore the progress is slow here but we are on the right way. We will continue with our work here and I hope we find a positive answer in the next couple of hours, possible days …
I have an idea to speed this up a little bit.
Crossing the fingers
Have a nice day and thanks for the confirmation. That helps a lot and it shows us that we are on the right track.
Ok gents, sorry but I must play back the ball to iFly. We have tested a lot in the last three days but without success. The database is working as expected. We have developed a validator to check all files and fields, it looks all correct from our side.
Further, we have tested the scenario in the iFly737-Max for P3Dv5 with the same AIRAC 2410, the P3Dv5 version uses exact the same data. No issue, no freeze, no CTD - so it looks, a implementation issue somewhere in MSFS but not a navdata issue.
Sorry for this news. I will inform iFly about our findings (or not findings) and I hope they can fix it.
Richard
its all good! thats why i opened this post. with what i found out yesterday of all day testing, having that memory fault code plus your findings should give IFLY plenty to work with and find out why
Thanks for that, Richard. The iFly MAX P3D version also scans default and addon airports using the same kind tool as the MSFS2020 prerelease version. So as you say, MSFS is most likely a suspect.
