Jump to content

[CLOSED] CRJ 200 1.4.1 crash


mutestyles

Recommended Posts

  • Replies 75
  • Created
  • Last Reply

Top Posters In This Topic

Unfortunately, I have to ask the experts for help. Can't get 1.4.1 to load without crashing XP. Attached are the crash report when I try to load the CRJ and the log.txt from the main XP folder. Hopefully Phillip, or someone can offer some help. I'm down to one more download off the X-Aviation site :(

Note that it was working at one point, but the SID/STARs where not loading into the flight plan. I removed my UFMC plug-in thinking that might be the reason and from then on haven't been able to get the CRJ loaded.

My system does load other aircraft and runs fine.

I've removed all my plug-ins except those noted in this and other threads. Hopefully my crash report and log with help.

Thank You,

Nano

Crash Report.txt

Log.txt

Link to comment
Share on other sites

An update on my situation:

I recovered my X-Aviation aircraft folder and my XP plugins folder from time machine from this morning which was that last time I got the CRJ to load and run properly with the exception of the FMS SID/STAR waypoints.

I can now get the CRJ to load and fly fine. Except I still can't get the SID or STAR waypoints to load in the FMS. I'm using a flight from KGEG to KSEA trying the load the GLASR8 arrival for ILS 16C at KSEA.

Link to comment
Share on other sites

Thank you Javier,

And thank you for your awesome aircraft. I have both the Javelin and the CRJ and enjoy them both. Here is a screen shot of my issue. Please notice the point listing on the MFD. It has KSEA listed three times multiplying the distance. In this case, I'm really only about 150 miles from KSEA.

post-7862-0-17171300-1327700553_thumb.pn

Link to comment
Share on other sites

I can now get the CRJ to load and fly fine. Except I still can't get the SID or STAR waypoints to load in the FMS. I'm using a flight from KGEG to KSEA trying the load the GLASR8 arrival for ILS 16C at KSEA.

We'll investigate this.

It has KSEA listed three times multiplying the distance. In this case, I'm really only about 150 miles from KSEA.

Open your LEGS page on the FMS and verify that those three are not listed at the end of your flight plan.

Link to comment
Share on other sites

They were not listed on the legs page. The flight plan ended with only one KSEA. Strange, but definitely repeatable behavior.

I tried the to load a SID out of SKBO and KMIA with the same results. The SID is listed and ACTivated using DEP/ARR key, but the actual waypoints of the SID/STAR are not in the flight plan.

Nano

Link to comment
Share on other sites

Unfortunately, I have to ask the experts for help. Can't get 1.4.1 to load without crashing XP. Attached are the crash report when I try to load the CRJ and the log.txt from the main XP folder.

Nano, the crash report shows there was some problem recovering the navdata from the cache. You can just clear the cache by deleting the files inside CRJ-200/plugins/CRJAvionics/cache

Philipp

Link to comment
Share on other sites

An update on my situation:

I recovered my X-Aviation aircraft folder and my XP plugins folder from time machine from this morning which was that last time I got the CRJ to load and run properly with the exception of the FMS SID/STAR waypoints.

I can now get the CRJ to load and fly fine. Except I still can't get the SID or STAR waypoints to load in the FMS. I'm using a flight from KGEG to KSEA trying the load the GLASR8 arrival for ILS 16C at KSEA.

Please, when X-Plane crashes when trying to load the SID or STAR, there must be a crash report generated. You find it in the Console Applications/Utilities/Console.app under "User diagnostic reports". Post it here!

Philipp

Link to comment
Share on other sites

Here is a screen shot of my issue. Please notice the point listing on the MFD. It has KSEA listed three times multiplying the distance. In this case, I'm really only about 150 miles from KSEA.

This is because you have no waypoints on the way to KSEA.

If KSEA is both the active, the next and the final waypoint, you will see it three times. When you get the STAR and approach loaded correctly, this issue will solve itself.

Link to comment
Share on other sites

I tried the to load a SID out of SKBO and KMIA with the same results. The SID is listed and ACTivated using DEP/ARR key, but the actual waypoints of the SID/STAR are not in the flight plan.

Did you make sure you have selected the correct transitions?

Because if you select only STAR or APP without a transition, it won't be inserted. If you don't see any transitions, make sure you can press "PREV PAGE" to get to the beginning of the list.

Philipp

Link to comment
Share on other sites

I too experience crashes when loading certain SIDs. This happens both with default 1.4.1 navdata (cyle 1109) and with the latest cycle (cycle 1201).

I'm on Win XP 32, X-plane 9.70.

To reproduce

Departure airport: EKBI

Destination airport: EKCH

Enter route: DCT ABINO T56 TESPI [EXEC]

Now, depending on which SID I select, either X-Plane crashes or not (appropiate RWY is selected using the right softkey first, then, when pressing left softkey to select SID, X-Plane crashes immediately):

ABIN4A: Works OK.

ABIN4B: Crash!

ALS3A: Works OK.

BAMP2A: Works OK.

RADI3A: Works OK.

MIKR2A: Crash!

The crash seems to be fully reproducible depending on which SID I select.

Now this may not be significant, but when I look inside the EKBI.xml file, the two SIDs that cause a crash have one thing in common: Waypoints of type = ConstHdgToAlt. The SIDs that work OK do not have this waypoint type (I'm just guessing here...).

It is very strange, but there is no crash_log.txt produced in the X-Plane 9 directory. Only Data.txt, Cycle Dump.txt and Log.txt are produced.

Hope this information can be of help. I'll be happy to do further testing on my system, just advise what to test.

Regards,

Per

Edited by per.ekhall
Link to comment
Share on other sites

Folks,

thanks to a report from Muskoka and a long telephone call with my debugging mentor Jörg Hermann (hat tip) I finally found what is causing the SID/STAR crashes.

I'm wrapping up a patch right now and send it to few users to test, then I hope we can put 1.4.2 out to all customers by Monday.

Philipp

Link to comment
Share on other sites

That one was a really ugly bug!!! when Philipp explained to me I couldn't believe it... but that is normal in programming.

Well.. I hope that fix can solve all the problems people are having around.

You maybe think why so many bugs when 1.3 was stable enough "these guys are going backwards" Well.. lot of programming was redone to introduce new features that were not supported in vascore, and also to increase performance. So 1.4 is something like a new plugin.. so something like a 1.0 version.

When everything is smooth you all people will have a really incredible plane with good performance and lot of systems to play with.

Of course there are people that already have it without any problem... and any that wish to fly "now" can do it in the 1.3.1 version... but the wait will worth it for sure.

In this 1.4 version sure Philipp and I we have some more white hair!!! (me sure!!!) XD

Edited by Japo32
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...