philipp

Yes, that's a perpetual issue with navigraph, they have changed their convention on capitalization of the folder names several times already, is was LevelD_proc when we released 1.4 and now it is LevelD_Proc and I bet when I make an update to the CRJ they're gonna change it to LEVELD_PROC No one else notices, because on Windows and Mac the file system is case-insensitive. And as 90% of navigraph's customers are MSFS users, no one complains. So I'm glad you solved it. Cheers, Philipp

1-3 confirmed. I've filed X-Plane bug reports for them, but I would stand by for at least 10.10 to go rc before changing anything in the CRJ about that. Otherwise we keep changing the parameters over and over again... 4. unsure about that. Did you try Javier's alternate pitch constant suggestions?

No problem here - I assure you that the Avionics plugin doesn't write to any of the AI controls. However, I can imagine one of X-Plane's idiosyncrasis at play here: the flight control override we activate when there is no hyd pressure, perhaps that gets incorrectly propagated to the AI planes also. Can you test if the behavior you see is dependent on the CRJ being "up and running" i.e. with hyd pressure, opposed to the CRJ being cold&dark? Philipp

I told Ben and he said "we'll look if the fix make sense", so I filed a bug report. All we can do now is hope&pray. Philipp

Neither. SCS plugin comes from vasFMC 2.10. I'm not aware of any other program requiring this plugin.

Yep, crashes for me also. The reason is the new joystick handling of X-Plane 10.10, which collides with our lookup for the FBW input to vasFMC. This is the plugin for vasFMC 2.10, but it has nothing to do with the CRJ, so this plane won't be affected. Note that SCS was never required for the CRJ, as it used it's own subset in a different plugin, at least up until 1.3.3. Since 1.4.0, the CRJ is totally independent from ANY vasFMC component. I guess this is now the last missing nail to vasFMC 2.10's coffin, as we cannot publish any changes to the source anymore, for licensing reasons. Which means I could fix the bug, but I'm not allowed to release it. Philipp

I would say it's a Collins Weather radar: BRT knob adjusts the accelerator voltage of the CRT (yes, it's a tube, not an LCD screen!) thereby adjusting screen brightness. Wx is weather radar display WxA is weather radar with alerts, which makes the red and pink areas blink NAV is a flightplan overlay GAIN controls the actual emitted power of the radar antenna OFF, STBY, TEST, ON should be self-explanatory, LOG I don't know from the top off my head. Rotateing the inner knob changes the antenna tilt so you can look upwards and downwards relative to your current altitude. RNG up and down control the range of radar echos displayed on the screen TKR left and right draws a helper line that you can pan left and right. You use it to find a path through the "holes" in the weather system, to find a safe way and then you can look what TRK you must fly to avoid all the dangerous zones. Finally on the bottom right is the antenna tilt stabilization that corrects the antenna tilt (given with the knob on the top right) against the pitch angle, to keep the radar image stable when the aircraft changes pitch (because the antenna tilt is counter-acted). You can disable this counter-acting by pulling the knob (STAB OFF). Philipp

Now that is really off topic in this thread, so I've moved it out. What you are pointing at is the radials you can introduce on the FIX page. Well, I have some little improvements coming up for the 64bit version, and those radials should be easy to make. However, NO promises at this time. Philipp

No, some of these datarefs are writeable and they actually perform actions in the cockpit, like pressing a button or turning a knob. I think what you are after are the scripts to tie these actions to joystick buttons. Just take a look here: The plugin xjoymap http://forums.x-plane.org/index.php?app=downloads&showfile=11720 and the config file for the CRJ-200: http://forums.x-plane.org/index.php?app=downloads&showfile=13581 Philipp

That file doesn't go in any particular folder, it is a reference for developers and cockpit builders who need to look up the datarefs.

Well, we originally had the close button on the top right screw of the display frames, that's why the screw still features a red X instead of a regular philippshead. However, we found most people found the display frames too obtrusive and fly without them - so using the screw as a close button was no longer an option. I can however bring the close button back as an invisible click zone in the upper right corner of the displays themselves - with no visual clue. Try the CDU, there it should still work this way. Do you think you'd be happy with using "invisble" close buttons? Philipp

My hardware zoo grew by another gadget today: The New iPad replaces my old laptop as the FCOM viewer, sitting besides my main screen to have aircraft manuals at hand for reference. You know why the New iPad is evil? It makes your screen look ugly - until this morning, I thought my 1680x1050 screen had a reasonable resolution for working. 4 hours reading stuff on the iPad, returning to my desk to resume hacking - WTF has happened to my monitor? There are blocky pixels all over the Place!!1! I need a 300ppi 26" monitor for development NOW! Philipp

Stefan, please check your mail inbox. I need your dedication to bug finding in the current test setup, where it will help the CRJ more.

I think the answer to this is already given in the second half of that post: Plus, you both please check your private messages. Philipp

Good luck with that

The "changes" are that the X-Aviation version simply does not have these sounds. For support for the aircraft at x-plane.org, please use the correct support forum. It is confusing to other readers when we give advise here that doesn't apply to the aircraft they bought. Philipp

Wow! It needs almost the same runway size as the real thing. But the sound is annoying. Reminds me of those idiots driving scooters with extra-loud mufflers...

I have a small fix for that on my list of things to include in the 64-bit version, that will be released when the development kits for 64bit X-Plane are available. The 64bit version will be a free update for all CRJ customers. Philipp

@Sethesus: http://www.dailymotion.com/video/xme7s_george-carlin-airline-announcements_news

What I don't understand here is how people have been able to fly our birthday child for one year now with this navdata, and now all of a sudden you discover it doesn't work any more. Last time I checked, software didn't rust on your harddrive. I have been unable to produce "stutters" by renaming waypoints on any of my Windows, Mac and Linux test machines. With several thousands of people flying the CRJ in and out of airports all over the world now I wonder what possible configuration causes you experiencing the stutters, and even more weird, make them go away by renaming waypoints. Don't get me wrong, I'm not implying I don't believe you experience a problem. I only wonder what configuration causes you to have problems right now and a few thousand other people not during the last year. I agree that relying on the stripped down navdata format like the Level-D-XML-Format we use is not optimal, as it doesn't give us all the data available for real-world systems. However, the choice was reasonable when initially designing the CRJ Avionics two years ago. Right now I am working with a partner from real world aviation to make it possible to use aviation industry-grade data for home users. It's not an easy task, not only because of technical problems, but because of huge legal concerns. I can't promise anything right now, but I am in negotiations with partners at Navigraph, Aerosoft and Lufthansa Systems to find a solution for getting industry-grade data that is affordable to home users. I don't promise we will succeed, nor do I give a timeframe for that. If we do, the CRJ will become the first aircraft ever to confuse users by having changed its navdata format three times during its lifetime Philipp

Your IPv6 is definitely not working, otherwise you wouldn't be getting this error message. Can you ping6 any adress?

A simple sudo apt-get install miredo should do the trick.

How that? The CRJ only comes in a 32bit variant. Because X-Plane is 32bit only for now. So if there was a 64bit CRJ, it wouldn't load in X-Plane. Make sure you have local IPv6 connectivity. Your problem is the plugin is getting a timeout on opening the listening socket for the CDU server, and before it receives the timeout, XPLM decides the plugin stalled and kills the enabling process (this is why you see the plugin as loaded, but not enabled). Philipp

Thanks for the flightplan. Now I have at least an idea what is going on. This could indeed be related to the new Navigraph data, because I was unable to reproduce it with neither the navdata shipped with the CRJ nor with 1202. I will get myself 1204 and see if I can reproduce your error. You could meanwhile check if it works for you using the navdata originally shipped with the CRJ. Philipp

Hi Emalice, I tried your flightplan on both my Windows PC and my Mac. I had no adverse effects on display refresh on either system. We however had several reports in the past where users complained of "stuck" displays related to programs running in background that interfered with threaded rendering. Such programs where - most of the time - webbrowsers, image editors, and one user complained of extreme lagging due to a free font viewer running. You should check the list of processes running in background. Everything that uses the GPU to render stuff can cause the context switching overhead that kills your displays. Next step would be to check the plugins you are running. For example, you are running X-IVAP and XSquawkbox at the same time. I don't know if they play well together. Try with all plugins but Gizmo and shrink-wrap de-activated (not disabled in the menu box, but temporarily moved out of the plugins folder) and put them back one-by-one. Philipp