[SOLVED] 1.4.2 DCT gives CTD

[docromano]

FMS Bug: Enroute LIPX-LFLS after enabling a STAR and performing a DCT to a point within it, CTD. A crash_log was not created, Ill attach the log.txt

/edit

Again CTD when performing DCT. Im using AIRAC 1201 vasFMC native, copied as recommended. I will do a re-install and keep the included navdata...maybe that helps.

Log.rar

Edited January 31, 2012 by docromano

[Cameron]

From Philipp:

Docromano: Your report lacks important information:

Which STAR are you using and where are you when you try to select which waypoint as a direct-to.

Please keep in mind that dependent waypoints may not be used on the DIR-TO page. This is not a limitation I made up, but it is how the real unit works. Quote from the Rockwell Collins FMS4200 training guide:

Many SIDs and STARs contain conditional waypoints that have no fixed geographical location, such as a heading to an altitude leg or a vectors leg. Although these types of waypoints show on the ACT DIRECT TO page, they cannot be selected for DIRECT-TO navigation.

[docromano]

I just had another CTD using 1.4.2

Route was

LFLS SOPLO N871 OMASI UQ224 GAMSA UN871 BADVI UL725 LEDRI UM985 NIT A42 SLC R53 EPEDA LZTT

Shortly after GAMSA the controller gave me DCT XEBIX at FL330.

I pushed the DCT button, then XEBIX and doing that I got the CTD. Again, no crash log, just cycle dump and log. Navdata not changed or updated, just raw CRJ-1.4.2

Since all my CTDs were associated with DCTs I will stop using that function for now.

[docromano]

...and again. This is starting to suck a little

I was enroute the same route posted above. Shortly before ABLOM I got the direct to EPEDA. I didn´t want to use the DCT function so I did what usually works. Enter the waypoint and click on the current one to get it exchanged with the new one. Worked a few minutes earlier with another direct from controller. This time - CTD. After almost 90min of flight for my VA which was ended by a CTD for the third time. I`m thinking of going back to vasFMC because at the moment it´s really "dangerous" to fly a longer route online since there are controllers and modifications to the route...

For now its only a feeling but I think I had less CTDs with the last version 1.4.1.

Edited February 1, 2012 by docromano

[Cameron]

Hi, Docromano,

Can you please share a screenshot of your Resources/Plugins directory?

Can you also do the same for: X-Plane/Aircraft/X-Aviation/CRJ-200/Plugins/ ?

Thanks!

[docromano]

Sure thing !

The navdata Folder is empty, seems to be a remain of an older version.

[Japo32]

Please delete everything of old plugins, and to test the plane with same plan you had, remove all plugins possible in your resource/ plugins area. Also I see a frameworks. That has something to do with the old plane?

Please stay clean of plugins until we find the culprit if your ctd. Others seem they fixed their CRS with this 1.4.2 version.

[philipp]

Docromano: I tested your flightplan, and flew the exact route as you, introducing the directs, both on LEGS page and on DIR INTC page (the only difference is I used 8x time compression to test, but that shouldn't make any difference). I wasn't able to get a crash with the exact instructions you gave, which leads me to believe we are looking at a faulty installation. Also, the folder "navdata" in your plugins/ folder isn't supposed to be there. Please run the uninstaller and proceed as Javier suggested, looking for any remaining debris the uninstaller didn't delete. Perform a reinstall, and you should be okay.

Philipp

[docromano]

Javier,

the frameworks stuff belongs to XP10 as it seems. If I remove them, I get a message they are missing and XP refuses to start. Removing Xacars and XSB is pointless for me but maybe I will try it out later. For now I´m downloading the current NVIDIA driver (see PFD black topic) and did a clean re-install. I´ll report back .

[Japo32]

For testing purposes maybe is good if you test over a clean installed demo.

[docromano]

I know that. The thing is that this CTD comes randomly and I don´t have the time for flying hours with the demo just to see if a DCT leads to a crash.

Just had another crash after a DCT to one of the first waypoints (keeping in mind what Phillip said).

I removed everything but saitek panels, XSB and pushback and XACARS now. Testing again.

[docromano]

Ok, now I got something reproducible.

I go to LFLS, rwy 27. Then I load the flightplan as posted above. Then I insert the SID SOPLO2H. Then I go to the DCT page and click NAVLA. Just pushing the button beneath NAVLA results in the immediate CTD. I will try again with NO plugins.

[docromano]

...and again, with no plugins at all. I think I have to go back to VasFMC for this flight :/

[docromano]

I tried it with the new AIRAC 1201, vasfmc native data. Removed the contents of navdata folder and put the new data in. Same CTD.

[philipp]

Can you please create the flightplan that produces the problem, and fly it to the point just before you are going to make the "fatal" change.

Then, just before you try to crash it, do the following:

Enter a name for the flightplan in the scratchpad, and press LLSK5 (< COPY ACTIVE) on the FPLN 1 page. Then post the file (it will be saved under CRJ-200/plugins/CRJAvionics/routes/) here, and tell me what you are doing to crash it. This way I can load your situation and perhaps get a clue what the problem is.

Philipp

[docromano]

No problem

Go to LFLS, rwy 27, load the flightplan. Then insert the SID SOPLO2H. Then go to the DCT page and click NAVLA.

[philipp]

Seems you forgot to attach the file, at least I can't see it...

Philipp

[docromano]

Oops !

LFLSLZTT.zip

[Stefan]

Hi Philipp,

i've a similar dct-problem, well reproduceable at LGSM.

Departure is LGSM, arrival LGAV, SID is ORMOS2B.09.

After the visual right turn, establish SAM 174, right turn back to SAM VOR, enter DCT ORMOS -> crash – every time!

If you need more diagnostic info, please let me know.

Another little problem with the DCT-Key: on my 1.4.2 the key seems to work ONLY in the "popup"-CDU. On the builtin CDU in the panel and the remote-CDU the key is inoperable.

[philipp]

Romano, Stefan,

I tried both your flightplans and was unable to recreate a crash on my side. I tried on Mac and Windows.

Perhaps I'm doing something differently. Could you perhaps make a video of what you are doing? Because I tried really hard both in Grenoble and in Samos with Direct-Tos and couldn't get a crash no matter what I did.

Philipp

[Stefan]

Philipp,

unfortunately the video is unreadable after the crash, but i found out one possible reason for the crashes:

when the waypoint which i want to fly direct to, becomes the active next waypoint (magenta), when or before (?) pressing the lsk for copy the name, the crash happens.

it makes no sense to direct to the next active waypoint intentionally, but the situation may occure under several circumstances (and then the sim should not crash anyway).

when i find out more, i let you know.

...not very senseful, but good to reproduce the problem:

departure lowg, arrival lowk, sid abiri1g.17, after takeoff dct grz lsk1 exec, then dct grz (now magenta) -> crash

Edited February 7, 2012 by stefanpi

[philipp]

stefan, would you please check your private messages?