philipp

the animation dataref is sim/weapons/x the main door is the 6th entry of the array.

Nav autotune has NOTHING to do with your route. The only purpose of NAV autotune is to select suitable navaids for improving the accuracy of your position. Remember that GPS is a carrier option, and the early CRJs without GPS rely on IRS corrected by VOR/VOR or VOR/DME. Autotune has absolutely no idea of your route and what VORs are part of your flightplan, it just selects VORs not further away than 30nm perpendicular to your course. Philipp

http://forums.x-pilot.com/index.php?topic=2111.0

You could also have a look at the new sticky thread I posted yesterday Philipp

Your crash log shows: Thread 6 Crashed: 0 libSystem.B.dylib 0xffff0877 __memcpy + 215 1 com.laminar_research.X-Plane 0x005bca35 png_read_row + 821 2 com.laminar_research.X-Plane 0x005bcd10 png_read_image + 128 3 com.laminar_research.X-Plane 0x004a6c38 TEX_load_png(std::string const&, xmap_class*, unsigned char*&, unsigned long, int, int, int, int, TEX_image_desc&) + 1560 4 com.laminar_research.X-Plane 0x004b75fa TEX_obj::load() + 7946 5 com.laminar_research.X-Plane 0x0072ec42 TEX_obj::do_it(int) + 18 6 com.laminar_research.X-Plane 0x00735c8f UTL_threadpool::thread_func(void*) + 79 7 com.laminar_research.X-Plane 0x0069b1a9 THREAD_launch(void*) + 57 8 libSystem.B.dylib 0x9035d7fd _pthread_start + 345 9 libSystem.B.dylib 0x9035d682 thread_start + 34 This is not a CRJ-routine! It's not the CRJ plugin or the vascore plugin crashing, it's X-Plane crashing when trying to asynchronously load textures. Maybe you are running out of memory, when using the CRJ (which has highly detailed textures using quite some memory) in a highly detailed scenery. This topic has been covered before. Sceneries containing errors or sceneries with just high memory demand might work well with other planes, but become a problem with a highly complex aircraft like the CRJ. There is nothing we can do about that. Philipp

11.04 is a nightmare!! I installed it on a notebook and downgraded to 10.10 again after a day, experiencing abysmal battery runtime and roaring fan due to a faulty kernel module. As far as I can see, there is a problem with the 2.13 glibc. If you absolutely want to run on this system, you can try installing libc in version 2.11 locally (besides the libqtGui.so). I personally suggest waiting for 11.10 or downgrading to 10.10 which runs rock-solid. Philipp

Now TOBS has all the datarefs, I'm sure he will be able to create amazing stuff. Philipp

Hello, as promised, the comprehensive list of all CRJ datarefs. With these it should be possible to create a full-blown CRJ homecockpit with all the switches, buttons and lamps operational. Also it will help TOBS with his scripts for more keyboard commands. Have fun, Philipp PS: You will notice a pattern for the buttons with integral lights: the dataref suffix "_btn" is the button press or click. The suffix "_lth" indicates the light, with possibly more than one value, and it is STRICTLY READ ONLY, because the light status is determined by the CRJ systems logic. CRJ-Datarefs.h.txt

I confirm there is an error with the order of the transformations applied to the flight director. Fixed for 1.1 version. Philipp

Topics merged.

It is definitely "CRJ/popup/cdu" Philipp

You can copy the waypoint where you want to go in the scratchpad, and insert it in the active position, and the FMS will delete all intermediate waypoints by itself, just like the real thing. Philipp

No. Displays rely on being drawn by X-Plane. Perhaps if we sell a million copies and I can retire to work solely on CRJ, then we can have an external version also...

About overshooting the thrust limiter: See known bugs, it is highly dependent on the type of hardware input you use as the throttle axis. For the 1.1 patch, I changed the design so it should work with whatever hardware throttle input you use. About selecting the limit by temperature in the FMC: I have no idea, because I got the tables the way they are and didn't change a thing. If in doubt, I would trust the pilot handbook more than the FMC, and this is also what a real pilot would do. About the distances: Please keep in mind the FMS shows intermediate distances, while the MFD shows the accumulated distances (from where the plane is now!). However, the accumulated distance recalculation after making a shortcut has a bug and fixed in 1.1 About making shortcuts: It is not true that you have to delete all intermediate waypoints by hand! Just select a waypoint on the route, insert it where you want it, and intermediate waypoints will be deleted. Just like the real thing, no need to do a DEL on every waypoint. Philipp

Yep, the speed tape reads INDICATED airspeed. As you climb higher, the air becomes "thinner", so the differential pressure in the pitot tube (that's how airspeed is measured) becomes smaller. Airspeed indication drops. The readout on the MFD in turn shows TRUE airspeed, which is corrected for the altitude and temperature by the ADC (air data computer). Philipp

Then it is not a software bug, but you are doing something wrong. Please remeber that not all screens come on immediately if you turn on the battery. The PFD and MFD screens are powered by busses that don't get energized by battery only. You need to either plug in ground power or start APU and select APU power to have all screens operational. Refer to the manual for further details. Philipp

Confirmed. Thanks for detailed report. Fix in 1.1 Philipp

Logfile shows the CRJ plugins load okay. However, the logfile says you are running on an Intel integrated GMA, which might not work with the CRJ. Did you run the hardware test? Philipp

They are read from the database.

Please post the Log.txt from X-Plane.

From the Rockwell Collins FMS 4200 Pilot manual, 2nd revision december 15, 1999, page 4-18: "Occasionally a waypoint identifier (such as BLH) may be used more than once in the navigation database. In such instances, the SELECT WPT page shows when the TO line select key is pushed in the previous step. ... You also cannot use two airways that cross without a defined crossing intersection." That means: Crossing Intersection has always to be entered by the pilot, AND if this intersection's name is ambiguos, the pilot MUST select it. If you have evidence indicating otherwise, show me. I totally understand that you BELIEVE it must be possible otherwise (because theoretically it is possible from the database), but I implement based on MANUALS, not on beliefs. Philipp

There is no reason why the CRJ would inhibit using the Python Interface. EDIT: I saw you got it working. Great.

Great you got it working! Now this will allow to interface every single button of the CRJ when I release the datarefs - really soon after patch. Philipp

otools is part of the Apple Developer Tools (XCode). If you don't have them installed, it won't work. Moreover, if you are not confident in using Terminal, scratch that suggestion. Wait for the 1.1 version, if this also doesn't work for you, contact Cameron for a refund. Philipp

Well, the 3d cockpit is modelled according to real measurements. The screens are not bigger in the real thing than they are in the simulator. But in the real thing, you have much a broader view than even a 27in. monitor. To compensate for this limitation, we provide the popup-screens. The resolution of the popup screens is the same as of the little screens. So they are smaller, but not "blurrier". If you absolutely don't want the popups, you will have to either adjust your field-of-view setting to a more close-up perspective, or you setup a closer view to use with pilot view plugin. Philipp