philipp

The first waypoint goes in to the RLSK4 position on the FPLN1 page, or is introduced with the SID. Philipp

Stefano: Products bought at x-plane.org are supported at the org forum: http://forums.x-plane.org/index.php?showforum=121 Philipp

I've looked it up in the database: GEELA4.25L goes over MNSTR to GATWA, from where you have to expect ATC vectors to the final approach (which begins at FIXAR) GEELA4.07R goes over PUNNT to CAGOR, from where you have to expect ATC vectors to the final apporach (which begins at ALLIS). So by choosing the destination runway 25L vs 07R you choose whether the STAR continues with MNSTR or with PUNNT after GEELA. In my database, BLH transition to GEELA goes over SCOLE-SNNRA-LZIRD to HYDRR, SPINK is not in the route - perhaps it was added in a newer cycle. The chart you posted is effective with 1112, the database shipped with the CRJ is older. If you want newer data, you can buy it at http://www.navigraph.com Philipp EDIT: Checked with cycle 1201 - SPINK is in there.

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: @Kyle: Looks like you selected only the procedures, but missed to activate the transitions. On the MOD ARRIVAL page, make sure to review the available transitions for each procedure, and press the PREV/NEXT PAGE keys as necessary to review the list. Philipp

About the XSquawkbox issue (TOBS): I tested the CRJ with XSquawkbox on each and every of my X-Plane installations which are -On Windows 7 32bit -On windows 7 64bit -On Suse Linux -On Ubuntu Linux -On Mac OSX 10.7.2 -On Mac OSX 10.6.8 each with X-Plane9 and 10. Every single combination worked for me, leading to the assumption we are looking at a driver/openGL problem, especially because of the fact I have nvidia cards in every of my machines, while you are using ATI. I also asked Wade (author of XSquawkbox) for a debug build a week ago, which he promised to send me when he finds the time (rememeber Wade does XSquawkbox as freeware in his spare time). That's unfortunately all I can do right now. Philipp

Yep, that was a particularly stupid bug over which I now owe Jörg Hermann a bottle of wine. Long story short: There once was some code written in FORTRAN, with some limitations, some guy ported it to C, another one to C++, finally some young enthusiast CRJ programmer incorporated it in the FMS and overlooked a little limitation still there from the FORTRAN days... This is fixed with the 1.4.2 update, which should be up in a couple of hours. Then you can move X-Plane back to wherever you like. Philipp

Good find! There exist various navaids with the identifier LAR. So the FMS tries to bring up the WPT SEL page. In that particular case there exist navaids of type DME with that Id, that don't belong to the VOR with that id (they have the same id, but are in different countries). The WPT SEL page got confused by that, because I was making an assumption I shouldn't have made. Anyway, fixed in 1.4.2 which should be up in a couple of hours. Philipp

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

Thanks for the report. These issues have been fixed in 1.4.2, which I hope to pump out shortly. Philipp

You are using the X-Plane.org version. The X-Plane.org version is supported on the .org forums: http://forums.x-plane.org/index.php?showforum=121

The problem is: No one really knows. Sometimes something just doesn't work as expected. You try to debug it, and you run in a coalesce free somewhere in Carbon. I reported this to Laminar months ago, and they say they also cannot fix it, because Apple doesn't update or fix Carbon any longer. They are now switching to Cocoa for going 64bit (Carbon is available in 32bit only). Philipp

The display frames are now under Aircraft/CRJ-200/plugins/CRJAvionics/Resources

Wait, you are the one whose SIDs/STARs started working as soon as you removed the Air Navigator (iPad) plugin? Have you had the PFD problems before?

Please post your Log.txt. And the crash report (from Applications/Utilities/Console.app User diagnostic reports). Philipp

Thanks, got it! It seems it is the old Carbon bug... Nothing we can do about it, neither the Airnavigation guy nor me. We wil have to wait for X-Plane to go 64bit for this one to work. Philipp

schrader501, you missed the all-important step: you just quitted without doing the "bt" before. Philipp

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

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.

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

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

Where can I get air navigator? Because when I can see the problem on my own computer, chances are good that I can fix it. Philipp

@shrader: On Linux, there is no crash log, but you would be my hero of the day if you could post me a gdb trace: http://forums.x-plan...showtopic=29916 @tobs: Which GPU switch exactly? There is the EXT AC power connect button in the overhead, and the GPU power selector in the CDU

bonfiki, check your private messages

Could you try removing the airport navigator and check if it works then? Philipp

That's normal, because Plugin Admin itself is a plugin, and it counts as number 1. Muskoka, check your private messages. Philipp