philipp

To me this looks like an incompatibility between freetype and your libc. My guess is that this is not related to updating X-Plane 10.10 to beta8, but rather to updating system libraries which you might have done at the same time. you could try removing the libfreetype.so from the CRJ-200/plugins/CRJAvionics/liblinux/ folder (keep a backup copy, please) so it falls back to your system default (make sure you have freetype for 32bit installed on your system, of course!) - that should be compatible with your libc, since it was probably updated by the package manager at the same time. Philipp

From the output you posted, you didn't run X-Plane from gdb. Use gdb to run the X-Plane exectuable (instead of starting it from your desktop, or how you normally do it). The output will look very different then and reveal a lot of detail. Philipp

Using Linux? try the following: open terminal and navigate to X-Plane main dir type gdb X-Plane-i686 run when crash triggers, type bt full post output here.

That's about the dirtiest panel I've ever seen. Can't you guys afford someone to clean up once in a while Just kidding. Amazing textures!

Okay, two separate issues here: You bought the CRJ at the org: You don't need Gizmo You bought the CRJ at X-aviation: You absolutely need Gizmo. If you remove it, some displays simply won't show About the displays disappearing when you're under high graphical load: that is totally possible. The displays are rendered off-screen and blit into X-Plane on-the-fly while it renders the cockpit. If there is no memory on the GPU left where I could copy my displays into, it will simply not paint anything.

Perhaps you just use the wrong kind of motivation - how about awarding refrigerators to gold-medal winners - I mean, it definitely works for North Korea...

64bit will not help with performance at all. 64bit helps with crashes you get due to out-of-memory conditions. That's when X-Plane crashess with a "bad alloc" error or simply crashes the graphics driver. That's what you'll get out of 64bit, but only if your OS supports 64 bit AND X-Plane suppports 64bit in the future, which is planned for X-Plane 10.20 which is not in beta yet. Regarding your specific problem, please make sure you have no process running in background that could possibly force the graphics card to do a lot of context switches. That is, close any Browser, PDF viewer, Image viewer, etc you might have running in background while running X-Plane. We've had numerous reports already, most of them ATI graphics users, who experienced lagging displays when they had a browser window open in background. If in doubt, open windows task manager and check for browser, adobe reader, etc. processes that might be running. Philipp

Unfortunately, only the 777 FMS does this, the CRJ's doesn't

Perfectly normal - the Source selector changes the source for the autopilot to either captain's side or fo's side. Captains side displays NAV1, Fo's side displays NAV2 (apart from a failure condition when a displays on one side fails, which is not modelled in the CRJ, as it only has captains's side). Philipp

Whatever you measured when you say "it's never getting to 2Gb of memory used" - the fact that you get "bad_alloc" is a proof for an out-of-memory problem. Because std::bad_alloc is C++'s way of saying "I can't fulfill your memory request": http://www.cplusplus.com/reference/std/new/operator%20new/ Can you try what the effect of a lower number of AI aircraft is? This setting is NOT under Rendering settings, but under "Aircraft and Situations". Philipp

I suppose you are using X-Plane 10? The oil pressure model changed compared to X-Plane 9, we will adjust the CRJ once XP 10.10 is out of beta. Philipp

bad alloc is just another word for X-Plane running out of memory. You are hitting the limits of 32bit with your combination of scenery, AI traffic (or in this case, IVAO-provided traffic, but for memory it's the same) and our plane, which has a consuming model and textures. As long as X-Plane 10 is available as 32bi only, your options are limited to either - flying with less displayed AI aircraft or flying with lowered texture settings, or just flying X-Plane 9 until X-Plane 10.20/64 is released. Philipp

We have no direct mapping of the load stations to the index. That is, we assume you, as a good load manager in real life also would, will fill the plane in a way that it LEAST affects the index. Which means, if you start loading passengers, you first fill up the group that has least impact on the index. If those seats are full, you begin filling the next section with the second-minimal impact and so on. And when you then add the baggage, you begin loading it to counter the effects of the passengers, or at least not add to the effect. That is, if you end with a negative index after loading the passengers, you begin loading the cargo where you get positive index. In real life, you have your dispatcher who calculates all this for you, and you have an experienced purser and ramp agents who know how to load your plane. Ever travelled in a MD-83 and you were asked to change your seat? It sometimes happens that at the gate they assign passengers seats that in the end lead to the aircraft being unbalanced, and then the purser will ask passengers to relocate. That is a common experience in aircraft like the MD-85 which is very sensitive to the cg location, and it generally holds true for all aircraft with the engines at rear and cantilever-type stabilizer. Less for the CRJ than for the MD-83 though. Okay, what am I building up to? In real life, you have people who take care of this for you and load your airplane so you don't get adverse effects on the balance. Therefore, you can treat the aircraft as perfectly balanced when you added the payload (don't touch the explane slider for the cg), and then add fuel and enter the calculation taking only the fuel's effect on CG, and assume the payload effect to be practically zero. If you really want to load your airplane in an insane way, you can totally work through the whole Excel sheet and then manipulate the cg slider in X-Plane, just to experience how it feels when your dispatchers are monkeys, but I wouldn't recommend this for your everyday flight experience. Philipp

Vickers VC-10 ?

All Linux users affected by the problem please write me a pm for testing a potential fix. Philipp

I _think_ they fixed it in beta 4. At least on my Mac it's okay now. Can't speak for windows though and not for ATI graphic cards. Let's hope for the best. Philipp

Known bug of beta3. Already reported to and confirmed by Laminar. Philipp

A heads up from the new CRJHQ : CRJ 1.5 brings a few fixes for X-Plane 10.10 compatibility, yet another small bump up in framerate, a few improvements in navdata processing, and two cool new features. The first is easier fuel loading. Now you can enter the exact amount of fuel you need in the CDU, and the CRJ will fill its tanks appropriately, without stumbling over X-Plane's idiosyncratic behavior of filling the center tank before the wing tanks. It's really simple, but saves you a lot of headaches with otherwise possible fuel system misconfigurations: The second thing is a really nice addition for iPad owners, who want to enhance their cockpit experience: I'm proud to introduce RRC - retina remote CDU - which makes the iPad an even better companion in your CRJ cockpit. The new renderings were done by Andreas Guecklhorn (@Gourmador) who has just learned Blender and did the CDU as an exercise. He not only did these gorgeous 2K textures but also the slick 3d-effect of the screen and the subtle glow of the text, like you'd see it on the CRT display in a real CRJ cockpit (no LCD screens in there yet!). I added some Javascript magic for better usability and day/night modes. Also, it is now a fully iPad-aware HTML5 App - you no longer have this browser-like feeling with resizing and moving - it feels as solid as a native iOS-App. This is a 2048x1024 screenshot right from the iPad. It must be viewed in 1:1 mode or the subtle glow effect will look overdone. So if you're not viewing it on an iPad, make sure you display it pixel-by-pixel, not scaled, and realize how small your computer screen actually is... http://philippmuenze...rj/IMG_0007.PNG CRJ 1.5 is a free update for all customers, and will be available after the beta-phase of X-Plane 10.10 is over. Cheers, Philipp

Please file bug reports with screenshots, Log.txt, exact hardware specs and graphics driver versions. Philipp

Yes, I use a MacMini with nvidia graphics (poor old 2010 generation). You should first clear your preferences. If the error persists, definitely file a bug report -> http://dev.x-plane.com/support/bugreport.html Don't forget to include your Log.txt and exact hardware specs (preferably dump of "About This Mac" -> "More Info..." -> "System Report" -> File->Export as Text) and a screenshot. Philipp

Perfectly working here. In fact, better than before, because beta 3 solved a special issue of color-matching the CRJ uncovered. Philipp

I'm pleased to announce that after an intensive one-hour Skype session with Ben Supnik we figured out what the "grey-out" problem was. X-Plane 10.10 beta3 brings you back the crisp dark screen look. Philipp

I think this is not an X-Plane 10.10 problem, but rather you got stuck in Mach mode by accident. Just open a default plane, select the speed mode back from Mach to KIAS using the standard changeover button, and then load the CRJ and it will work again. Also I think that this has nothing to do with X-Plane 10.10, rather with you missing to select a departure runway. You must have a departure airport AND a departure runway selected at that airport AND a valid temperature input at that airport to get the thrust values Probably directly related to 2), since the limiter is set to 0.0 it won't allow the engines to spool up, as it tries to limit the N1 to 0.0. I think you are referring to the reflective surface over the screens that should be just translucent with a tiny bit of reflections over a pitch dark "tube" screen which now looks gray. This is a known issue of the 10.10 version in both HDR and non-HDR mode and Ben Supnik already knows about it, so no doubt it will be fixed. Philipp

I did a few experiments with the oil pressure and starter. I'm very optimistic we'll have this working nicely again soon, but I won't publish anything until the 10.10 has an "r" for "release candidate" in the version string. Otherwise it's like hunting down a moving target. Philipp

The CRJ is not going to work without Gizmo and shrink-wrap. So the issue you are seeing is what is to be expected. I suggest the following: Run the uninstaller of the CRJ. Then make a copy of your whole X-Plane installation folder. Name the copy something like "X-Plane-with-Gizmo". Run the CRJ installer and point it to the newly created "X-Plane-with-Gizmo". It will set up everything so you can fly the CRJ again with all its functions. Use this X-Plane installation for all planes that require Gizmo, like the fantastic DC-3 from Leading Edge, or any other plane you buy from X-Aviation. Now back to the old X-Plane folder, where you removed the CRJ, and you manually removed Gizmo. That now is your place for the other planes where it says "incompatible with Gizmo", like Peter's A321, Carenado planes, etc.. Continue your struggle with the A321 there, undisturbed by Gizmo. I agree that this is neither an ideal nor a convenient solution, but its the only thing that works as long as Ben Russel (Gizmo developer) and Alexander Babichev (SASL developer) don't sit down together by a glass of beer to agree on rules how to peacefully coexist. Philipp