philipp

No. The post you are citing is from a person no longer involved in the project. I am currently explorating how far we can push web technologies to use the other displays over network, like I did with the remote CDU (have you tried it?). No promises now if this works as I think it ought to. Other than the displays, have you taken a look at the full list of datarefs we published - basically every CRJ system functionality is available to third-party applications via X-Plane datarefs. Philipp

No, the lean_assist compatibility problem only affected Mac and Linux. So your problem must be different. Please check that -your X-Plane is the latest version (earlier than 9.6 will cause this error, too) -you installed new navdata correctly (if unsure, go back to the deafult and try again) -try cleaning the navdata cache as described in post #9 Philipp

Thanks for testing. This is the officially fixed version, including this fix also for Linux (Windows was not affected): http://forums.x-plane.org/index.php?app=downloads&showfile=12206 Please re-download also if you took the temporary test version, because the temporary version would not work with the Carenado Bonanza. This one does. Philipp

We display the weather that is known to X-Plane on the MFD (in 3d-mode only). If Xsquawkbox sets the weather in a way that X-Plane can't generate the WXR picture, then there is nothing we can do about that. Philipp

Markus, would you try the attached mac.xpl as a replacement for your lean_assist mac.xpl? If it works for you I will put it up at the official location. Philipp mac.xpl.zip

Okay, found it. In fact, it IS exactly a plausibility check that causes the trouble: the check for trying to post a holding onto an existing holding (this cannot be done, existing holdings have to be edited through their own page), which does an invalid operation if performed on a flightplan with less than two entries. Fixed in next update. Why shouldn't this be allowed? LOWG is a waypoint as any other and perfectly valid to be selected the active waypoint. At least I can't remember reading anything like "you are not allowed to set the departure airport as direct-to waypoint" - as opposed to dependent waypoints, which are indeed not allowed to be selected either active or dir-to. Philipp

Confirmed. Route name is not displayed. Fixed with next update. Philipp

Confirmed. ID indication should not be tied to the DME indication. Fixed for the next update. Philipp

Snip from your crash report: Thread 0 Crashed: Dispatch queue: com.apple.main-thread 0 libSystem.B.dylib 0xffff0877 __memcpy + 215 1 com.laminar_research.X-Plane 0x006f48a5 png_read_row + 821 2 com.laminar_research.X-Plane 0x006f4d06 png_read_image + 518 3 com.laminar_research.X-Plane 0x00388c60 TEX_load_png(std::string const&, xmap_class*, unsigned char*&, unsigned long, int, int, png_alpha_mode, int, TEX_image_desc&, OGL_normal_mode*) + 1616 4 com.laminar_research.X-Plane 0x0039bd65 TEX_obj::load() + 8421 5 com.laminar_research.X-Plane 0x0012d2ff tman_class::load_texture_obj(tex_fail_mode, int, tex_load_time, std::string const&) + 1295 6 com.laminar_research.X-Plane 0x0028f466 OBJ_command_builder::set_texture_lit(std::string const&) + 486 7 com.laminar_research.X-Plane 0x004072e8 build_obs_v8(OBJ_command_builder*, obj_mod_struct*, xmap_class*, conditional_t const*) + 2776 8 com.laminar_research.X-Plane 0x0042995c build_obs(std::string, int, tex_load_time, tex_fail_mode, int) + 2508 9 com.laminar_research.X-Plane 0x006568ec veh_class::IO_veh(int) + 3580 10 com.laminar_research.X-Plane 0x001d802c veh_class::load_veh(int, int) + 892 This is almost definitely an out-of-memory condition. Try lowering the texture resolution before loading the CRJ. The texture sized at "extreme" quality settings is massive, and depending on the scenery installed in the area where you load, might be more than the virtual memory. Note that we are talking about the virtual adress space here, which has nothing to do with the 16GB of RAM you have installed - which is certainly more than enough. Please read the Laminar blog post about virtual memory vs. RAM for the details: http://developer.x-plane.com/2011/12/bad-alex-bad-the-road-map-for-memory/ Philipp

Hey folks, this is Philipp, reporting for X-Pilot out of the new German headquarters, where rapid progress is made on the way to world domination. No, just kiddin'. You might have noticed I have much longer latency in forum postings, PNs and emails during the last few weeks - and this is why. I've relocated my place in the greater Frankfurt area, now living roughly at EDDF/360/3.5. I moved in with my girlfriend, and we are slowly re-compiling our stuff to form a new household. With her parents and a very helpful fellow we moved my stuff (basically a desk, a few computers, a few books, lots of cables) and her stuff (a truckload of clothes, plus some neglect-able other things) to the new place over the last few days. Actually, her stuff included a washing machine, a device weighing approximately 50kg, which we carried up three flights of stairs (no elevator in the new house). Thanks to Martin, Marit and Jörg (no, not dr.coolgood, another Jörg) for helping us moving our stuff so quickly, you all did a terrific job! Now I've erected my desk and set-up the internet connection: 50MBit/s VDSL. Works marvelous with the new router I bought, and now I can upload CRJ updates at more than 50 times the speed I had in my old apartment. So this is the new place I work from, as you can see all my books and stuff is still packaged. But that's nothing compared to .... ... this is what our kitchen looks like right now. Way to go. So this continues to be on my agenda for the next weeks, while I try to be as responsive as possible here. Now I'm off to find my teapot and kettle in this mess... Philipp

Sorry, typo. The correct path is Aircraft/X-Aviation/CRJ-200/plugins/CRJAvionics/routes/ Delete the folder you created.

For starters, could you check if the route is actually saved after you press "COPY ACTIVE" ? Does the file appear in Aircraft/X-Aviation/CRJ-200/plugins/CRJAvionics/routes/ ? Philipp

@tharan, please check your private messages.

If the IRS is already aligned, you can't enter a new POS unless you force a re-align, by turning the IRS mode selectors to OFF position for a few seconds. It's not a bug, it's a feature

Okay, then I will look into unifying the codebase and publish an update for LeanAssist. Philipp

Thanks Marcus, I have an idea what is going wrong - could you temporarily remove my lean_assist plugin and try if the CRJ loads up then? Philipp

Please post your Log.txt. There are some reasons that can trigger this error: -Navdata missing or wrong format -WMM2005.cof file missing in Resources -cache folder missing -something went wrong loading the cache, in this case deleting the cache helps -initialization of the worlddata subsystem failed due to missing datarefs, this happens when you try to load in X-Plane 9.6 (9.65 is minimum) So my advise: -Make sure X-Plane is current and no files missing, by running the X-Plane updater manually -uninstall the CRJ and manually remove any folders it might have left behind (navdata cache is a candidate) -install CRJ, don't touch navdata -check if it works -install navdata update, if desired -check again When it doesn't work, post the Log.txt.

Looks more like an out-of-memory error than a CRJ error. First try would be to lower the texture resolution. Then take a look at the advise here: http://developer.x-plane.com/2011/12/bad-alex-bad-the-road-map-for-memory/ Philipp

Try cleaning the navdata cache. To do so, go to CRJ-200/plugins/CRJAvionics/cache and delete all the files inside the folder (don't delete the folder itself, please) and see how it goes. Philipp

It's exactly the same error as this one:

Hi Stefan, I think I know what the problem is - it is in the interplay of DME intercept waypoints and the turn anticipation. When there is a big turn after the virtual waypoint, everything works fine. If there is a shallow turn (or no turn at all) after the virtual waypoint the turn anticipation becomes narrower than the error margin with which the virtual waypoint is calculated. I will not go into the numerical details here, but it is an error I can and will fix soon. Philipp

The problem with custom animations (driven by custom datarefs) and replay mode is, that X-Plane doesn't record them. So if you plugged in the GPU, and then go into replay mode, the GPU will remain plugged in, because there is no way for X-Plane to know what the state of the GPU was when the replay was recorded. There is currently no way for a plugin to set up a custom animation for recording. This is a feature I will suggest to Ben Supnik when I meet him in two weeks - no promises though if he will listen to me Philipp

Just a dim idea - this might be caused by an ABI mismatch. Could you temporarily test without other plugins, so if anyone loads a c++ runtime incompatible to ours, we can find it?

You might be haunted by what we re investigating as a problem of late X-Plane 10 betas - a few users experience autopilot oscillations, but not limited to the CRJ, with other aircrafts too. Perhaps you are one of them. However with the CRJ it is more critical than with other aircraft, because our fuel system modelling is very accurate on g forces: If you apply negative g, fuel flow to the engines will be disrupted immediately, leading to a flame-out. Some users reported that deleting the preferences and re-assigning their joystick axes and augmentation settings solved the problem. However, I think there are factors at play only Laminar can find.

Yip. Only ACT flightplan is tracked, never MOD. Philipp