philipp

Glen, thanks for the screenshot, but it doesn't fit my theory. So there. It's still possible we are looking at a plugin conflict. In the past side-effects of other plugins have caused all kinds of trouble. You would be the first where it affects SID loading though. But this is definitely worth a try, to temporarily move out other plugins and check if it has any effect. If it works, put back the plugins one-by-one and continue trying until you found the one that causes the error. Then please tell me which it was - so we can contact the author if necessary. Philipp

Perfectly okay. The LevelD_proc folder contains an .xml file for every airport. It was not clear to me: Did you try to remove all plugins, except for Gizmo and shrink-wrap, yet? Because above you say you "deactivated" them. Deactivation in the plugin admin is not the same as moving them out of the plugins folder. Did you try this? Philipp

Glen, I have a dim idea... Could you make me screenshot (in Explorer) of what your CRJ.200/plugins/CRJAvionics/Resources folder looks like ? Philipp

@schrader501 , @retiree_caf: I need _specific_ descriptions of what you are trying to do, and what you are pressing at the moment it crashes. "When I press some knobs", or "When using SID and STARs" are not descriptive of what your problem is. A problem description should include -the operating system you are using -the navdata cycle used -the departure and destination airport -the planned routing between those -the SID, Transition, STAR, Transition and Approach at each airport -the sequence of your entering (do you first enter the route, then the SID, or first the SID, then the route, etc.) -after the crash, the crash report (crash_log.txt on Windows, crash report from Console.app on Mac) Philipp

I'm glad to inform you that I found the underlying issue - the FMC was recalculating the total distance constantly, but updating the remaining distance to the MFD only at a waypoint - so everytime you just crossed a waypoint (or were sitting on the departure runway) the distance was momentarily shown correct, and with increasing distance into the leg, the error would grow. I fixed this now, and it will make it into another small update that will correct this along with some other little annoyances. Philipp

Daniel, I can see nothing that looks immediately wrong. Only thing I see is that you have lots of plugins installed - in the past side-effects of other plugins have caused all kinds of trouble. You would be the first where it affects SID loading though. But this is definitely worth a try, to temporarily move out other plugins and check if it has any effect. If it works, put back the plugins one-by-one and contine trying until you found the one that causes the error. Then please tell me which it was - so we can contact the author if necessary. Philipp

I hate to say this, but this sounds like a user error - did you put the IRS 1 and 2 into align mode before entering the coordinates? This sounds exactly like the copy protection kicking in. Cameron, your turn

I had no problem at all - you register on the forum, wait a few days until your account is activated (it took two days in my case, because I registered on a Saturday), and then you eventually get an email that you can start posting. If you created 6 accounts in a row, it is very possible that you ended up on a black list for spamming. Philipp

Okay, in your clean installation, what do you see in CRJ-200/plugins/CRJAvionics/navdata? Can you post a screenshot? Your Log.txt would be very helpfull, too.

I still have no clear picture of your problem. Please post your Log.txt and a screenshot. Philipp

You can ignore the folders SID and STAR. Important is the folder LevelD_proc. Please try with a clean install first. If that works, proceed by installing new navdata. PFD and MFD not lighting up points to an issue with the copy protection, on which Cameron will assist. Philipp

Did you install any navdata after the original install? Please try with a clean install first. If that works, please proceed with new navdata according to these instructions:

Yep. Dual-Core users should see an increase in framerate, quad-core users a slight decrease in CPU load. The reason is simple: More work done on the GPU. The CPU has 2, 4 or 8 cores I can use, with the GPU I have up to 400. Philipp

@Daniel, regarding SIDs and navdata: regarding the first waypoint : If you still have a JRollonPlanes folder, you can safely delete it now. Philipp

No departure runway selected = no threshold elevation altitude for the departure runway = no performance calculation

@bonfiki: Your method of entry is perfectly valid. I just tried your flightplan. No problem at all with the navdata that we ship. I see the picture you are seeing (all the lines going down infinitely) momentarily before the FMS recalculates the dependent waypoints. After less than half a second, they jump into position. Are you by any means programming in pause mode? Can you try to post me the saved flightplan ? Philipp

Hey Anders, have you checked this: ?

Did you enter the flightplan before? The FMS must know the destination aiport (actually, the elevation of the departure runway) to calculate the performance figures. As for the others, I will take a closer look once I'm back at my development computer. Philipp

@deltapilot90: All crash logs show the Xsquawkbox plugin is crashing. Could you please try removing the Xsquawkbox plugin and tell me if it works then? I wonder if this has anything to do with it, because I'm using XSquawkbox myself, but all your crash log.txt indicate so. @bonfiki: Could you please post - the navdata cycle you are using - the exact sequence in which you entered the flightplan, and of course the flightplan itself An additional plus would be: -try to recreate the fault situation -exec the flightplan -save the flightplan -post the saved flightplan here (you find the file under CRJ-200/plugins/CRJAvionics/routes/) Philipp

1) Where did you try to insert the fix, if you say it was not to replace the current waypoint? Where you trying to append it to the flightplan? 2) changing the destination airport is done by entering a new dest on the RLSK1 on FPLN1 page. 3) This is because you didn't select a departure runway and a SID (standard instrument departure). The flightplan must be active before you see anything. You see this as the departure airport in the flighplan being replaced with the departure runway.

Tristan, of course I have various manuals, otherwise I would not be able to program anything. I will come back to this posting once the dust of 1.4 has settled, probably after the X-Plane developer conference. Philipp

Nononono! You are not supposed to delete PluginAdmin/win.xpl ! Because this is part of X-Plane which makes all other plugins work! You just destroyed your X-Plane installation. Run the X-Plane updater to bring PLuginAdmin back. I am talking about the win.xpl that is in Resources/plugins/ in NO SUBFOLDER. Philipp

Hang on, this is not 1.4.1 You have 1.4.0 ! I will ask Cameron. Philipp

With the new version you have to enter the first To WPT on the FPLN1 page (this is correct as the real training documentation says it is done this way). You have to put the first waypoint in the RLSK4 position on FPLN1 page, before you can proceed with your flightplan on the next page.

For the sake of other users, please stick to English. The "backend" I'm talking about is some libraries that are under $HOME/Library/Frameworks on Mac. Theoretically, it might work with both plugins - but given the amount of compatibility workarounds we have to do anyway, we decided it is best to start clean all over. Philipp