philipp

The modified acf is made for X-Plane 9. To have the X-Plane 10 landing lights, you should try this approach instead: http://forums.x-plane.org/index.php?showtopic=75438

I used "Sporty's Instrument Rating Course iPad/iPhone App" though in a version that is seemingly no longer available (It was mostly videos and I paid $139 I think, the current version seems to be beefed up on the interactive part and now costs $199) and took about 6 weeks to go through all the lessons, one evening at a time. My instructor signed me off for the written test after just one hour of additional ground school, so it was definitely worth the investment. Same holds true for going into the actual flying with a very solid theoretical knowledge already. My lessons consisted of 98% just flying and only 2% explaining, at least that's how it felt like. Of course X-Plane helped a lot to get proficient in all the procedures before actually flying them. To be honest, after most of my actual lessons I was like "I don't feel like I learned anything new today", but of course that's not true. There's so much fun in flying actual IFR! In my opinion, there are few things more rewarding than flying an approach in actual conditions down to the minimums, and then seeing the approach lights appear dead-center in the windshield. I did encounter some actual conditions since I got my ticket, and am now working on converting my FAA IFR to an EASA IFR.

better than scrolling back to the end for bug fixes only, search for "beta 8" and find all the added features, datarefs, etc.. Also, see this: http://developer.x-plane.com/2014/08/some-recut-dsfs-for-x-plane-10-30/

If you bought at x-plane.org then this where you need to go for support. Cross-posting doesn't help. Please take a look at my answer to your question on the org forum.

Unless you discharged the fire bottle. In that case the engine is toast and needs to be replaced by maintenance (read: re-load the plane in X-Plane).

The technology is the same. It's literally the same code, because I made them both The URL is the same, the port is the same. You are not by any chance using the no-network patched CRJ?

If you enabled X-Plane once to accept connections, it works for all airplanes. So if you allowed X-Plane to accept connections when connecting to the 757 CDU, that will also have allowed it for the CRJ.

I bet it's a problem of the intel HD driver. The Intel HD is a particularly poor choice for X-Plane, both it is slow, and the Intel drivers are borked beyond belief when it comes to openGL. If your computer doesn't have a PCIe-slot for a decent, dedicated graphics chip, the only thing you can do is always install the latest Intel HD driver whenever there's an update, and just hope for the best, since sometimes they actually fix such bugs.

No, it's 64bit only. X-Plane 9 is not available in 64bit.

@Mik75: send me a private message please. I'll get you links to the updates.

You can get the "un-twisted" version back by going to CRJ-200/plugins/CRJAvionics/Resources and exchanging the docroot/ with the docroot-old/ folder - the old version has no 3d effect. If you want to make your own version with only screen and no button, you can do this by writing your own HTML. Just look at how index.html in docroot works. You can make your own html and css code there to make every view you want!! Sorry, I don't speak Spanish. Javier can translate perhaps.

if the problem occurs again, be sure to post your Log.txt so we can see what went wrong.

OSX 10.9 "Mavericks" brought some changes to the network stack that cause certain server functions to not work properly in some network setups. This can cause the CRJ-200 to be unable to start the remote CDU server, thus the plugin hanging in initialization state forever. Some users report it works again when re-loading the plane in X-Plane rather than starting X-plane up with the CRJ being the first plane. It seems to be largely correlating with users who did upgrade installations, and almost never a problem after a clean install. It is usually solved with a clean install and sane network setup with a router that behaves properly with multicast (not all home routers do, unfortunately). Mulitcast is a network feature used to discover the remote CDU over zeroconf/bonjour on Macs. As not all users want to perform a clean-install, which is admittedly some more work than an update, I provide the no-network CRJ as an interim solution to those who have trouble until they have the time for a clean-install and making sure their router is working properly. This patch only disables the remote-CDU feature of the plugin. All CRJ-internal functions continue to work just the same! Download this patch from here if you got the CRJ from X-Aviation. Do NOT download this patch if you got the CRJ from any other shop!!! For the X-plane.org version, go to their forum instead! The patch contains a replacement plugin for Mac and instructions how to install. Note that this problem does not occur on Windows and Linux, so the patch does not contain anything else! CRJ-200-nonetwork-patch-xaviation.zip

The values that were changed are found in Expert -> Artificial Stabilty -> Autopilot I suggest you make a screenshot of this pane for easy reference.

That Intel HD has problems with that is not surprising. That GPU is really not the right choice for X-Plane.

transparency issues can be really tricky with HDR and the implementation in the GPU driver. To know for sure, we need more information, like your GPU, your OS, the exact driver version, and whether you are using HDR or not.

What exactly do you mean by the display light switch? If you are referring to the display brightness rotary, then this is no surprising, because the dimming is simply not simulated on the CRJ.

I'm seeing a gajillion of license checks - don't know if this is correct. Also, you are using XSquawkbox 64bit. Do you have the latest version installed because the first 64bit version could crash other plugins! The Log,txt looks to me like X-Plane crashed when you un-loaded the CRJ after completing your flight - changing to a different plane or shutting down X-Plane entirely. Is that correct?

Sounds like the Saab install changed something with Gizmo and activation. I suggest you contact the activation support by using the contact form: http://www.x-aviation.com/catalog/contact_us.php Make sure to include your Log.txt and the gizmoLog.txt (both from X-Plane main folder) when asking for help.

The backcourse mode of the CRJ autopilot maps to the backcourse of X-Plane. No additional magic attached to it.

Yes, but not at full texture resolution. We recommend 1GB VRAM to run at "extreme" texture res. With 512MB you will not be able to use that setting. EDIT: If you have further questions regarding the 777 please direct them to the appropriate forum to prevent cluttering up this thread.

The current latest versions are 1.4.5 for 32bit 1.5.3 for 64bit If you are running 1.5.0 on 32bit without problems, consider yourself lucky. Many people were complaining about 1.5 on 32bit, which is why the 32bit branch of the CRJ is reverted to the longest stable version 1.4.5 which is really very stable. So if 1.5.0 is running fine for you and don't have out-of-memory crashes, there is really no reason to up-(down?)-date.

A very important spec is missing: you didn't tell which graphics card you are using and how much VRAM it has. We recommend at least 512MB VRAM, 1GB is better if you run at maximum texture resolution. 1.3GHz is a little bit on the lower end. You might need to turn down objects count, cars and other traffic (CPU-intense stuff) to get an acceptable frame-rate with an 1.3GHz CPU. But first you should find out what your graphics card specs are.

I guess what happens is that RXP GNS530 probably uses the same API (XPLMNavigation) that I use to make X-Plane fly the flightplan. Thus, X-Plane gets competing requests every other frame, because the CRJ FMS want to go one way and the 530 the other. As the FMS is an integral part of the CRJ-200 simulation, it is not possible to de-activate it.

Hi maletin, please look at this html file that comes from a user modification for the 777 remote FMC. It is modified to use touch events on the iPad rather than onClick and it works remarkably well. Maybe combining your modifications with this would be a win? I do have a github account and forked the repo already. Philipp index.html