philipp

I think I have lost track of what works and what does not. You managed to get it work on your Linux system by downgrading 32bit libraries? Do you use the libQtGui and libQtCore that came with the CRJ or from your system /usr/lib32 ? After you sorted this out you are back to square one with your system, which proved to be the most problematic AMD computer I erver saw Well, I can only say that I MASSIVELY changed the rendering system for version 1.4, offloading more work to the GPU than the CPU, and I am curious how it will work out on your AMD system. I interpret the line "it will not be bothering me next week" as "I ordered a new PC", am I right? Philipp

Most definitely copy protection issue. Cameron will check in here soon. Philipp

Unfortunately not. I think the white screens are a result of a graphics driver bug that won't let me map the PBO like I want it. As it is highly unlikely that Apple will release a graphics driver update for an almost 6 year old hardware, I fear you are out of luck with this. Philipp

CAS is Crew Alerting System. As in EICAS = Engine Instrument and Crew Alerting System, which is the two central displays. It means you should check the yellow warning messages on the left and the white status messages on the right EICAS display and take any messages into consideration. The Fuel crossflow switch is in the overhead panel, in the fuel panel: The center switch of the top row is the gravity crossflow (which is simulated including the influence of sideslip!!!!) and the center switch in the bottom row is the powered (pumped) crossflow. Both should be dark. Philipp

I bought it myself for christmas, and I find it quite enjoyable. I would call it an "ONLY" simulator: It is day-only, VFR-only, switzerland only. The photo scenery for switzerland is *&!"HOLY CR*P THIS IS AWESOME£~+!@ impressive. The dynamic shadows are as good as X-Plane(10)'s. The fps are incredible: Everthing set to "Ultra"+HDR+8xAA=170fps on my machine. The aerial photos are good. The colors look credible (i have seen a lot awful blue-greeny photo sceneries, this is not one of them). The resolution is okay, but it could use either autogen buildings or an even higher resolution because most houses are simply brown blobs if you look very close. However, the scenery is ideal for VFR flying. I flew around areas I know from winter holidays and immediately recognized the skiing areas I'm familiar with. Also the highways I know were easily recognized and some adjacent villages also. The autogen scenery lacks houses (there are some, but too few). The trees are gorgeous however. The flightmodel physics feel plausible as in "it feels very similar to X-Plane". I would say X-Plane and Aerofly FS feel roughly the same, whereas FSX feels quite different. The weather options are barebone: Two cloud layers and one global wind setting. Thats all. However, it has thermal generation for soaring: dark patches of landscape in the sun generate thermals you can easily find when flying over them and hear the Variometer go "boouuuueeeiiiiii! beep! beep! beep! beep! beep!" The aircrafts are barebone: Only the "holy six" instruments are working. No radio navigation is implemented. No Autopilot. No electrics. No working switches, no electrics. Engines are always running and cannot be shut down or started. The piston engine model is nonsense: it has no idea of density altitude, so you can climb the C172 to FL200 with 1000fpm. Mixture control is not implemented. Also the manifold pressure is nonsense, as are the temperatures (neither fuel flow nor EGT gauges work). For me, Aerofly FS makes for a very good soaring simulator, and awesome VFR flying with simple aircraft. However, I would love the density altitude effect as it would make mountain flying really interesting, when you really have to plan ahead because your performance is limited. Philipp

Click Plugins -> Plugin Admin -> Plugin information and look for "CRJAvionics" there will be a version information that is definitive. I also found that X-Plane is sometimes picky with how it initializes aircraft from a running-state into a cold-and-dark state. To be totally safe, make sure you unchecked "start with engines running" under Settings -> Operations and Warnings, then load a default plane like the Cirrus Jet, to be sure that everything is really dark and totally shut down, then load the CRJ and fire it up BY THE CHECKLIST. If you encounter any troubles in this course of action, let me know. Philipp

Hmpf, this looks like we are getting some wrong .so loaded with the plugin. Can you make on ldd on the CRJAvionics/lin.xpl file and post the output here? Other than that, please check your private messages. Philipp

Ben Supnik said he believes the error is fixed with beta6. All users affected by this problem, please update to beta6 and check if it is now working for you. Philipp

Hi Marcello, just a few thoughts: -You are sure the update process went well? To be absolutely sure, click Plugins->Plugin Admin->Plugin Information and make sure that under CRJAvionics the version string is 1.3.0 or 1.3.1. It happened to me more than once that I updated some plane but kept flying a copy I had put in another folder.... - Windows firewall might be blocking. Did you get the "Do you want this program to accept connections" window at first load of the CRJ? If not, there might be a permanent setting in the firewall configuration that interferes in some way. To clean up, open the Windows Control Panel -> System & Security -> Allow a program through Windows firewall. Click "change settings" and scroll the list to find X-Plane. Highlight X-Plane and Click "Remove". Click OK. This will remove any non-standard settings you might have set for X-Plane and will make sure the firewall asks again for permission at next CRJ load. - Can you access the CDU on the same machine now, by entering http://localhost:18387 in Chrome? If it works there, we are sure it works on X-Plane's side, and from there on can address network problems while being sure it is not an X-Plane/CRJ problem. Philipp

Are you sure about the driver version? Your graphics card is brand new, but the driver version you claim to be using is years old. Are you really sure that's not a typo and you meant 285 ? If not, could you please try updating to a recent driver from the nvidia site and check again?

Hi folks, Ben Supnik asked me for help for fixing the HDR problem in X-Plane 10, that causes the CRJ displays to be completely dark at night. We need more data who sees the problem and who does not! -Please first make sure you are running the latest beta of X-Plane 10, which is currently 10.03beta5. -Load the CRJ with engines running, so all displays are up and working normally. -Now try the following: Turn on the "HDR rendering" option in the rendering settings, and turn the time so you have a pitch dark night. If you are affected by the problem, the CRJ displays (PFD, MFD, EICAS) will be dark now. Please post your following results here: 1. Are you affected by the problem? 2. Operating system (full version please, not only "Mac" or "Windows") 3. Graphics card vendor and model 3.a If on Windows or Linux, driver version (omit this for Mac) Here's what I have so far: 1. No, all is fine 2. Windows 7 Professional with SP1, 32bit 3. Nvidia NVS3100M 3.a 280.26 1. No, all is fine 2. Suse Linux 11.3. 64bit 3. Nvidia NVS3100M 3.a 285.05.09 1. No, all is fine 2. Windows 7 Professional with SP1, 64bit 3. Nvidia GeForce GTX570AMP! 3.a 285.62 1. Yes, displays are dark 2. Mac OSX 10.7.2 3. nVidia 320M 1. No, all is fine 2. Mac OSX 10.5.8 3. nVidia GeForce 9600M GT Please add your experiences to the list, so Ben Supnik can locate the problem!

If you start X-Plane with the cold&dark option (Settings -> Operations&warnings -> uncheck the box "start with engines running") and then fire up the CRJ by the book, you will not encounter an engine fire. The engine fire is triggered when you are in a hotstart condition (fuel is added while N2 is < 16%) AND you don't pull back the fuel lever when you notice the hotstart (EGT rises violently). However, a certain condition can trigger an errornous hotstart when you load X-Plane 10 with the CRJ when the "start with engines running" box is checked. This error occur only in X-Plane 10 and is fixed with the 1.3.1 version of the CRJ. You can check the version by opening Plugins->Plugin admin->Plugin information and then see the entry "CRJ Avionics". If the version reads 1.3.1 you are seeing an engine fire because you are really doing something wrong. If the version reads 1.3.0 you might be experiencing the X-Plane 10 bug and you must download the update from your X-Aviation account. Philipp

The CRJ makes use of all CPU cores available, as you can easily see in CPU monitoring widget like MenuMeter. If your CPU is improperly cooled this may exhibit problems. Improper CPU cooling can mean for example a too thick layer of thermal grease between CPU and cooler, or an improperly installed cooler. I once had a notebook with that problem, turned out it was uneven thermal grease. Had it serviced, no problems ever since. So you see a high CPU load because the CRJ actually uses the CPU cores available to maximize framerate - most other planes simply don't and your cores stay idle. If you experience severe thermal problems because of this, this would indicate a visit to your local Apple store and have the CPU cooling checked. Philipp

Looking good: == X-Plane 10.03 Beta 4 Scenery: Custom scenery packs with legacy file organization now work Fixed crash for RealScenery Oahu (and any DSF with car-only road networks) Restored some v9 library paths for overlay scenery This update should install the bug fixes to Paris, Denver, and a few other tiles if you have them installed from DVD. Aircraft: Fixed erroneous FMS clear Fixed Auto-throttle auto-engage Prop disc plugin override is not reset when the flight is restarted Fixed out-of-order key-frame tables for generic rotaries Fixed black area in 3-d cockpit of P180 and other planes with HDR on Temporarily removed generic map instrument - we'll put it back once it's fully finished ATC: Fixed a common ATC related crash due to weather changes Fixed common ATC related crash due to an audio issue Corrected Heading/Altitude Rounding Improved efficiency and quality of ATC taxi routes Misc: Removed 16-bit color option from monitor-res popup. 16-bit color is not supported! Fixed ghosting on NVidia cards

Yeah, there is a programmed Excel sheet a user made and uploaded here - unfortunately it is inaccessible right now. I will have to look if I saved it somewhere. Philipp

Discussion goes on there:

This is a three minute walkthrough of the new FMS for the CRJ 1.4. You can see the following new features -new font render with accurate character placement -keyboard input to the scratchpad -ACT/MOD flightplan logic -STAR transitions -Direct-to with position update and turn prediction -overfly waypoints -altitude conditional waypoints -intercept conditional waypoints The 1.4 update will be a free update for all CRJ customers and will work on X-Plane 9 and 10. Philipp

Just wanted to tell you that I finally found that %&!§$@#*!1! bug and fixed it for the next update. God, this fella was hard to find and well hidden... Philipp

That's what I'm telling you. We have basically very similar computers. I'm running at LOWI, extreme texture resolution, 4x anti-aliasing, 3200*1200px at solid 50fps. You are seeing a drop in fps as soon as there is power to the displays, because we are launching 5 rendering threads in the background to asynchronously render the displays while X-Plane is running. My development system is an aged, dual core, 2gb ram, 256mb integrated graphics mac mini. And it runs 25fps at LOWI also. So I still think you are missing one important X-Plane setting that steals your fps, because our (similar) windows PCs are immensly more powerful than my Mac and if I get 50fps out of it, so should you. If you want to get into technical discussion you can do so by sending me a pm and uncover which FS products from you I should know. Philipp

There's no way your PC is too weak for the CRJ - we demoed the CRJ at FSWeekend on a PC with quite similar specs: i7-2600K, P8P67 mainboard, 8GB RAM, Zotac GTX570 AMP! We demoed on 3200x1600 screen resolution (dual monitor setup) with extreme resolution and 50+fps. Here are a few things you should try: -Up-to-date graphic drivers are a must! Get the drivers from the nvidia site and not via Windows update -X-Plane settings scenery-wise: You mentioned you are having trouble on airports - is there any scenery setting that brings down fps at airports? -Background applications: One customer reported that he had a stuttering problem when in the background his browser was open on a website with snowfall animation. Make sure there are no applications are running in the background that require GPU power. And these days, a browser is in this category, as modern webbrowsers use GPU acceleration to render certain CSS effects. Philipp

For the time of CRJ development I occupied a desk in my mother's office, which happened to be understaffed at the time. As you can tell from the books on the shelf and the italian architecture poster on the wall, she's an architect. So this office has quite an interesting output: virtual planes and real houses Philipp

Bill, sorry if you feel offended by my wording. Keep in mind I'm not a native speaker and tend to translate a certaiin German "directness" verbatim into english As for your problem, the crash log definitely points to IPv6 being unavailable. Re-download the CRJ from your X-Aviation account. There you get the updated 1.3.1 plugin, which will also work in an IPv4 single-stack setup. Philipp

Personally I think it is a stupid idea to delete X-Plane 9 so early in the 10 beta phase. Because X-Plane 10 is to stay a moving target for add-ons for quite some time still. But for your problem, please post a gdb stacktrace of the crash. How you do this, is explained in detail here: http://forums.x-plan...showtopic=29916 except that you of course don't send the report to Laminar, but post it here for me. Philipp

X-Plane 9 and 10 version are the same plugin-wise. Only the 3d model is different. So if your CRJ in X-Plane 9 works, the plugin in 10 must work also. Because it's exactly the same code. My best guess is that something went wrong during installation. Could you please post your Log.txt from both X-Plane 9 and 10 here. Both after you tried to load the CRJ of course! Philipp

The engine fire problem is fixed in plugin 1.3.1. Please log in into your X-Aviation account to download the update. @falloutgamer65: If the frames drop, there might be an application in the background causing a context switch. One user reported that he had this problem when in the background his browser was open on a website with snowfall animation. Make sure there are no applications are running in the background that require GPU power. And these days, a browser is in this category, as modern webbrowsers use GPU acceleration to render certain CSS effects. If the problem persists you are probably running the sim at too high a setting - until there are more optimizations to X-Plane 10, it will be worthwhile to use rather conservative settings on GPU intense options. Philipp