philipp

"HDG_CRS is 0 in an Intc waypoint" is a diagnostic message of the navdata parser, nothing to be concerned about. I tried LGTS FSK3E here and it works fine for me. The stacktrace looks astonishingly similar to a long-solved 1.2 bug - perhaps something went wrong in the update process, which a clean reinstall might solve.

Hi Owen, for the STAR selection to work, you must select a transition (the old FMS didn't support this). So after selecting the STAR itself, press PREV PAGE until you see the transitions beneath the selected STAR. Select a transition, then you can select an approach. Again, watch out for the transitions beneath the selected approach and select one. Philipp

I guess that's a joke you have to be Aussie to get it ...

If you want to change the destination: Enter a new destination to the RLSK1 field of the ACTIVE flightplan. If you want to enter a completely new flightplan: Enter a new departure to the LLK1 field of the ACTIVE flightplan. As you found out, the flightplan must have been executed at least once, because otherwise there simply is no ACTIVE flightplan, it is empty, as all changes initially go to the MOD flightplan. You can't enter departure or destination airport on the LEGS page - you must do it on the FPLN page. Take a look at how it is done in the tutorial! Entering airports on the LEGS page only works on Airbus-style FMS like the Honeywell Pegasus or the Thales 2. Not on the Rockwell Collins FMS of the CRJ, at least that's what the original training document says. Also, you can't enter a VIA airway directly from a runway. You have to have either a SID or a DIRECT leg inbetween. Both those LEGS (an airway after the SID or a DIRECT), require that the destination airport is entered beforehand. Again, the tutorial is your friend. Philipp

LOL, now that is the english language... Both devices with warm water and cold air are called radiator, the one in the front of your car, and the one hanging from the wall in your house. In German, we have two different words for it. So of course our cat stays on the window ledge above the "heater" radiator. I don't think it would fit in the engine compartment, because our cat is HUGE.... It's a '94 Opel Omega, in the U.S. it was sold under the name "Cadillac Catera", in AUS also called "Holden Commodore". It has 190.000 km on the clock and recently begins to show a bit of rust on the right door, so buy more CRJs so I can replace it Philipp

Just driving home from the monthly Frankfurt fligth sim enthusiast gathering, I saw this indication on my Dashoard: (10°F for the Americans). Nothing unusual for guys operating from CYZF, but I would rather swap with our cat and stay on the radiator the whole day Philipp

The autopilot logic is unchanged since 1.1. No programming or procedures regarding VOR/LOC/ILS changed in 1.4. Philipp

These folders are not really needed, but it doesn't hurt if they are there. The CRJ only uses the LevelD_proc folder, the SID/STAR folders were a fallback for vasfmc - the CRJ doesn't really need it. Philipp

stefan, would you please check your private messages?

I don't believe that. It may have required admin privileges for installing, sure, but once it is installed what reason should there be to still require admin privileges? Have you tried running X-Plane as a normal user? Philipp

Why are you running X-Plane as an adminstrator? Because the crash log appearing under "System" instead of user diagnostic reports means just that. Is there a particular reason why you execute X-Plane with system privileges? Anyway, the crash log points to a part of programming I'm not responsible for, but I forwarded it to the guys in charge. Philipp

Please check your private messages.

As far as I can see, SNU is the last waypoint of the ILS29 approach (regardless of the transition) because it is the holding where the missed approach terminates. When you entered the approach into the flightplan, the meaning of LOWW in the flightplan will actually be "threshold of the selected runway at LOWW". I just tried changing an rw34 approach into an rw29 approach at LOWW: ILS34.NER2N goes something like this: WW836-WW835-WW834-CI34-DME19-LOWW- missed approach begins here-(1000)-WGM-hold at WGM pressing DEP ARR, selecting LOWW arrivals (RLSK2), deleting ILS34, selecting ILS29, then NER3M transition (this is important! always select the transition, even if you are already behind it!) gave me something like this: WW829-WW858-WW910-CF29-FF29-LOWW- (missed approach begins here)-RW29/293/2.2(overfly)-SNU-hold at SNU So, yes, the last waypoint is SNU because the missed approach procedure is to let you hold there until you get further instructions from ATC. Regarding the entry: Simply press the HOLD button. If there is one holding in the flightplan, you will be taken to its page. If there are multiple holdings in the flightplan, you will be taken to a list where you can select the holding you want to edit. So if you press HOLD in the situation above, you will see the published missed approach holding at SNU, which is 350/R, giving a parallel entry if coming from the missed approach situation. If you want to make it a 175° inbound left turn, enter 175/L in the scratchpad and press LLSK3 (inbd crs/dir) and you will see the entry switch to a direct entry in this example. Press EXEC to save the change. Philipp

How did you change the runway? Did you select a new transition?

Tom, how to find the crash log on Mac: Open Applications/Utilities/Console.app and look in the list "User diagnostic reports". This list is chronologically ordered, so the last X-Plane crash will be at the bottom end of that list. EDIT: By the way, did you download the latest 1.4.2 update? No need to fight against long-solved problems. 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

Okay, I found what you are having trouble with - it's a difference between how Windows and Mac handle an UTF-16 to UTF-8 character conversion. Since I do most of my development and testing on a Mac, this slipped my observations. I will see what I can do.

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

When the "no navdata or no magnetic data" message pops up, it means just that. The plugin checks if it can find navdata and the WMM2005.cof file where they are supposed to be. First thing you should try would be to clean the navdata cache. You do this by using Finder to go to X-Plane/Aircraft/X-Aviation/CRJ-200/plugins/CRJAvionics/cache and delete all files in this folder. If this doesn't help, you have a faulty installation in some way, because the navdata is not where it is supposed to be. A clean reinstall might help here. Philipp

You are not allowed to enter any value on the left side. It displays computed values and activates them. So pasting any number on the left side will ignore the number (you could enter 1000%) and set the limited to the computed value. That it allows you to set 0% which sends the engine controller go haywire and kill your engines in the most stupid ways indeed qualifies as a bug. However, this should not happen when you follow the procedures in the manual. That means you have not selected a take off runway. TO calculate the thrust limit, the FMS needs to know the elevation of the departure runway. That means you must have entered your flightplan (which of course includes the departure airport) AND you must have set the active departure runway. Philipp

Pasting an "INVALID ENTRY" somewhere is always a very bad idea. What were you actually trying to insert?

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: 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

Well, disappointing perhaps, but in real world, there is also no goflight. There is no way to automagically upload flight planes into the FMS in the real world (I know, very recent FMS in A320N/A380/Dreamliner have the possibility to get flightplans via a data uplink or through ACARS). Every airline has a collection of flightplans for the routes they fly regularly. They are known as company routes, and stored in a device called the DBU (Data Base Unit). They are updated every now and then (when necessary due to AIRAC changes) by inserting a floppy disk (yes, a floppy, not a CD or a USB pen) into the DBU. As we don't know which airline you are flying for, we allow you to generate the company flightplans by saving your routes to the harddisk (no need to insert a floppy for you ). Consult the manual on page 70 on how to save and load flightplans. Philipp

This is not supported. Reversers have to be activate by the command sim/engine/reverse_toggle (in a standard installation assgined to the dot key on the keyboard). We don't use X-Plane's default reversers, because we wanted to be able to simulate the reverser doors being hydraulically actuated, the interlocking mechanics of the throttles, and the auto-reverse system for rejected takeoffs. There is no way we could do all this with X-Plane's default simulation. Your hardware throttle (or it's reverse axis) doesn't have the interlocking mechanics. You will notice that it works as expected if you use a hardware throttle axis as a throttle axis (not reverse axis) and the standard command (which you can of course map to a joystick button if you like). Philipp