philipp

The distances are of course different, because the MFD is showing the accumulated distances, while the LEGS page shows the distance point-to-point. Also, the total distance to the final destination is calculated including any arrival procedure - I see a waypoint behind CYOL in your MFD, does this belong to the approach? Note that what is displayed as the CYOL waypoint is actually the coordinates of the treshhold of the runway you set for approach. This indeed sounds like a driver problem - never saw anything like this on any of my three PCs or my Mac - but all of them have nVidia, no exeption. Now this is hilarious... Haha. I use the Saitek yoke myself. Can you tell me what exactly did you program the hat switch to do so I can try this myself - though I have not the faintest idea what could cause this. Note that flight plan saving/loading works on the ACT FPLN. If you edited your flightplan and where in MOD FLPN mode and didn't EXECute the modifications, the saved flightplan will reflect the state of the last ACT FPLN, not the MOD FPLN. Summary: EXEC all changes before saving. Smells ever more of a openGL driver issue. The temp rating does not influence the autopilot speed at all - If the autopilot is in CLB250 mode, it will hold 250 knots, even when you are pushing ridiculous N1, just you will be making a higher climb rate. The fact you are describing the VS between -200 and +600 makes me think the autopilot was not in the mode you thought it was - normal climb rate below 10.000 with full CLB power according to the temp is going to be well over 3000fpm, depending on weight, of course decreasing with altitude. Perhaps the autopilot was out of trim? What was the trim indicator showing? Did you center the flight controls (roughly) before activating the AP? Philipp

Hmm, can not reproduce here. I took your exact ICAO codes, and it works. Can you please look what version of the plugin you are running (either on FMS STATUS page or in Plugin Admin->Plugin Information. What build number do you see there?

There is some stray plugin in your plugins folder that doesn't belong there. You have a file named win.xpl under Resources/plugins. That's not supposed to be there! Because if it is called win.xpl as opposed to some_cool_plugin.xpl means that it is a plugin of fat architecture, which belongs to some folder. Either a folder under Resources/plugins, or a particular aircraft. I have no idea why you put this file there or what it does, but before we can start investigating anything else, this problem must be solved. Move this file out of Resources/plugins, and later you can try to find out where it really belongs. Philipp

@bonfiki: I just tried every combination of FARAxx SIDs with KARyy transitions at Malpensa and nothing crashes. Perhaps you also fell prey to some error copying/moving/fiddling with Navdata. Could you please first try to use a clean installation, confirm it works, and then move on using newer navdata. For the navdata, please observe the important announcement: Philipp

If you purchased at org, the org forum is the place where to ask questions. http://forums.x-plane.org/index.php?showforum=121 1.3 and 1.4 are mutually exclusive, since we changed the backend. You can't have both installed at the same time. 1.3 will stop working when 1.4 is installed, as the required backend was replaced. The navdata is now in the plane under CRJ-200/plugins/CRJAvionics/navdata. But please try a flight first with the navdata we ship by default, before you try anything else. Other threads indicate people are having a hard time because of moving/copying/whatever navdata folders around - perhaps of the wrong format. Please try with a clean install first. If this works, proceed with updating the navdata as mentioned in the sticky post. 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.

Well, we are not going to post detailed stats here. But you might remember we celebrated the 1000th CRJ customer some time ago... Philipp

Louis, please do not cross-post. I answered your question at length on the .org forum. Please ask your question at the site where you actually bought the plane: Otherwise we might end up answering the same question multiple times, which certainly won't lead to anyone getting answers quicker. Thanks for your understanding, Philipp

You are getting 1.4.1 directly. Shouldn't take Cameron more than a few hours, tops.

*****ALERT!: The navdata is now in the plane under CRJ-200/plugins/CRJAvionics/navdata***** Starting with 1.4.0, the CRJ has switched to a new Navdata format, but Navigraph has not changed their website yet. The correct dataset to use with the CRJ-200 1.4+ is the format currently known as "vasFMC Flightmanagment - native**" DO NOT download the old format labelled "JRollon Planes CRJ-200 - native**" !!! Navigraph has been notified of that change and will update the description on their webpage accordingly.

maybe you switched from another plane while in MACH mode - and the speed button now means 9 mach (which the CRJ definitely won't do ). Switch back to a default plane, make sure the speed dial is in SPD and not in MACH mode, and load the CRJ again.

Look at it this way - the org folks burned their hands on the 1.4.0 version already, which I found to have one really nasty bug - you are getting the 1.4.1 without this bug already. Trust me, you will be glad Philipp

Hi Tristan, depends on what information I can extract from the Navigraph procedures. Because there is a lot of guesswork involved as there is no DTD and I have to figure out all the quirks by try-and-error. So, can you give me an airport and a procedure where the feature you are thinking of is required? I need the airport and procedure code obviously, so I can look it up in the database, and a chart where I can see how it is _supposed_ to look like. Because chances are, this already works. Philipp

The crash log unfortunately reveals next to nothing. But the fact you are saying the crash is not related to a certain action (i.e. I press this button, then it crashes), but to a certain timeframe into the flight, might point at an out-of-memory condition. It is not unlikely that the CRJ is a contributing factor to this - the textures we are using have an extremely high resolution, combine this with some add-on scenery, and you might be hitting the two or three gigabyte barrier of your Windows OS (depending on whether you used the /increaseuserva switch). For general information on memory problems, not only related to X-Plane 10, but also 9, look here: http://developer.x-plane.com/2011/12/bad-alex-bad-the-road-map-for-memory/ Also, I saw in your logfile, you are using airport navigator. We had a lot of mentions from other customers recently that this plugin is causing some kind of conflict with our aircraft, see for example here: I suggest you try both lowering your texture resolution by one notch, to see if you are facing an out-of-memory problem, and remove airport navigator to see if you are seeing a plugin conflict. Either one has to be the solution. Philipp

Did you see this? Wow!

A late Santa told me he is shipping a few leftover Christmas presents to X-Aviation customers this week Among them, the completely reworked holdings:

I asked Wade for a debug version of the squawkbox plugin, perhaps we can figure out what is going wrong there. Philipp

Normally not. It is usually not done unless you have an engine failure and want a backup for the bleed air. If you are critically short on bleed air (engine+wing anti ice with 14th stage bleed, not modelled in our CRJ though) you could also use the APU for backup. Philipp

I just tried it on Windows 7 with X-Plane 10.03 and don't see any problem: I tried both CRJ 1.3 and 1.4 and all displays are running fine with XSquawkbox. This leaves two possible causes for your problem: -It is related to 64bit Win7, because I tried on 32bit Win7 and can't use my 64bit machine this week. -Something not drawing always smells of an openGL problem. So perhaps it is related to the graphics driver and an update could help Philipp

I believe he is seeing the same bug that was reported by the Dutch guy on the .org form last week. This is something I introduced with 1.3 and already fixed for 1.4. Philipp

Starting with engines running shouldn't be a problem. If you see this again, please provide me with the exact flight plan so I can reproduce it. Philipp

Hard to tell without the actual crash report. When X-Plane quits unexpectedly, you have to click the "Report" button and copy the report here so I can see what is going wrong exactly. Philipp

No christmas present unfortunately, even for the Spanish christmas where you get the present on Jan 6th. However, we are getting there. I know several people who will like this: Philipp

I just tried beta 10 and displaying all kinds of navaids on the MFD works flawlessly, see screenshot. They only show up in ARC mode, are you sure you selected this mode? Have you tried various ranges? About the engines: There has been a massive change in X-Plane 10, and it keeps changing over the betas. No use trying to fix our model for one beta to notice it is again nonsense with the next beta. We will re-evaluate the engine situation when X-Plane 10 has stabilized, as in 10.1 is out and the updates don't keep rolling in every other day. Philipp

Hi Pepel, since you bought on .org, you have to get the 1.3.1 update there. Please avoid cross-posting in both support forums, because I tend to lose track on who's problem is solved and who is still waiting... Philipp