philipp

if sim/cockpit/electrical/avionics_EQ is 0 then you are loading an acf file where it is 0 - are you sure you were editing the correct .acf? Maybe you have one of the user modifications .acf installed instead?

What's the status of the variable sim/cockpit/electrical/avionics_on (use dataref editor to inspect)? Note that this will come on ONLY if the DC ESS bus is powered from the ESS TRU, which in turn is powered by the AC ESS bus. So unless you have that power established, you will hear nothing. When both the avionics_EQ in the plane is 1 and this variable is on, you will hear the fan. If not, check your volume sliders in the sound menu.

You are talking about the background noise of the avionics fans? That's easily fixed. Open the CRJ200.acf with a text editor (I use BBEdit). Search for the string P acf/_avionics_EQ 0change that to P acf/_avionics_EQ 1and save. This has nothing to do with Linux. It's just that X-Plane now checks the presence of an avionics switch in the panel to decide whether it should play the sound. Since the CRJ-200 doesn't have a dedicated "avionics power switch" (it decides based on whether the DC ESS bus is powered) as a panel instrument, X-Plane needs to be explicitly told that there is an avionics system that can make noise.

That's a crash of the graphics driver. You have an Intel graphics card which is obviously not the best choice to fly X-Plane on. My suggestion is to turn down the rendering settings to a level the Intel onboard chip can actually handle. Here's what I would do: 1. Start with your rendering settings at minimum. If it still crashes, then we have a serious problem with the openGL stack. If you still get a crash at minimum settings, we'll submit a bug for that so Ben can look into it. He knows more about openGL than I do. 2. My guess however is that it'll work fine at settings okay with your little onboard GPU. So crank up the settings, coming from the minimum, up to a level that your GPU is happy at and doesn't crash the driver. Philipp

On the last one, flying the A330 though I see a SASL error, You should send the last Log.txt flying the A330 to the folks of JARdesign to figure out that error. However, the crashes you are getting seem to be not dependent on the type of plane you fly. Is there any reason why you are using a seriously out-of-date OSX? OSX 10.10.4 has been out for a while now, I seriously recommend updating to it, as it is bound to increase stability especially of the graphics driver. Staying with 10.10.1 is certainly not a good idea. When you have updated to OSX 10.10.4 and are still getting the crash, please do the following: Open /Applications/Utilities/Console locate in the left column the category "user diagnostic reports" The reports will be grouped by application and then sorted by date, so find the one of X-Plane that corresponds to the date after you've done the OSX update, in case you are still seeing the crash. Post that report here, along with the Log.txt from the incident.

Looks like the AI is getting stuck. Which airport in your area had the 8L runway active? Because that airport scenery has a problem with the taxi network. You need to locate the airport scenery that is causing the problem (again, it was an airport within 30nm of your plane, and it had runway 8L active at the time), and then flag that airport for a taxi route error at http://gateway.x-plane.com/ A short term fix is obviously to turn the number of AI aicraft down to 0 or do not fly in the vicinity of that airport.

Those are the _installers_ for the Visual C++ redistributable libraries (msvcrt.dll and other dlls). The _installers_ can be safely deleted. They are unpacked by the installers of the parent products (like the CRJ, Skymaxx, and probably other addons) and then launched in the background to have the msvcrt.dll and similar files installed in the appropriate location of Windows (C:\Windows\System32 and C:\Windows\SysWOW64 respectively). So you CAN delete the installers left behind in the X-Plane directory. Nuke them, nothing bad will happen. You CANNOT delete the MSVCRT.dll from C:\Windows\System32 because that will cause many software (not only X-Plane plugins) to fail. Philipp

Suface winds are reported as MAGNETIC. Winds aloft are reported as TRUE. The reason is simply that runways are oriented to magnetic north. You expect the surface wind to be reported in the same way your runway heading is measured.

You will find the display frame graphic in X-Plane/Aircraft/X-Aviation/CRJ-200/plugins/CRJAvionics/Resources/ Rename them at your leisure to make the plugin not find them. Altitude callouts are the default from X-Plane, not much that the CRJ can interfere with here. Check your volume settings. If in doubt, try another plane that uses the X-Plane altitude callouts, like the default 747.

This is a question I see popping up over and over again with all the advanced airplanes. In fact, with the 757 and 777 we have that several times a week: "I get this terrible noise every time I switch off the autopilot, how do I make it stop?" I guess the underlying problem here is that people are so used to doing it wrong. I see that all the time I watch other people "flying" or rather "simming": When they come down the ILS, at some point their mouse cursor reaches over to the AP master switch, or in Boeings, the disengage bar. I've acutally seen this with people flying elaborate home cockpit setups with hardware MCPs (like the Goflight). When they want to go to manual flight, their hand leaves the yoke, reaches over to the disengage bar and they flip it down. This is SO NOT what you do when flying real planes: Your hand stays on the yoke, and you squeeze the AP DISC button with your thumb (or, on some yokes, with your index finger). Same with the autothrottle. No one lets go of the thrust levers and reaches up to the MCP to disarm the A/T. Instead you squeeze the A/T disc with the thumb on the throttle lever. On Airbusses, you sometimes see pilots squeezing the A/T triggers on both sides of the throttle with the thumb and pinky finger while holding the throttles with three fingers, matching them up with the little white dot on the EICAS. From the Cessna 182 up to a B777 the AP DISC on the yoke is what you press. One time to actually disconnect the autopilot, a second time to silence the warning. Same with the A/T. First press of the button on the throttle turns off the A/T, second press cancels the EICAS warning (on the 777). Get out of this habit of reaching for the disengage bar on the MCP for no reason. If you actuate the disengage bar on a Boeing, you get that blaring autopilot warning, and you cannot cancel it by resetting the bar! You have to press the AP DISC on the yoke to cancel the warning! So, assign yourself joystick/yoke buttons for AP DISC. Get that habit of taking your hands off the yoke to reach for the mouse or the MCP out of your system. A pilot simply does not let go of the yoke when on final approach! Sorry for the rant, but seeing people at FlightsimCon flying their thousands of dollar hardware setups like this, not having a yoke button for the AP, makes me want to cry.

Thanks for posting the flightplan. I can't see any problem with it: You have any plugin overwriting the DME or GPS information?

Can you give me the full flight plan (including departure procedure) that you are trying to fly there so I can try it myself?

Cannot confirm this. 4NM at 230kts is about 1 minute: 31nm at 6 minutes also looks good to me: 116.80 is what I get when I depart Seattle. That's the SEATAC VOR, which makes kinda sense. Note however that the FMS likes to autotune DMEs even if they are standalone (a DME with no attached VOR or TACAN) over VORs without DMEs because DME updating provides more navigational accuracy. Do you have any other plugins installed that override the radio frequency, like a hardware radio (Saitek panel or the like)?

I beg to differ. X-Plane 10.35 beta 1 had a bug that caused it to run only on Vista and later, but not on XP. We got exactly 1 (ONE) complaint from a guy in Russia before we fixed it in beta 2. And 10.35 Beta 1 was live for several days, it was not one of these Betas that were superseded within hours.

Also, this is not the right forum to discuss Steam content. There are a few minor differences depedning from which publisher you got the content. To minimize confusion throughout the support, I strongly suggest you go to the support forum of the publisher Aerosoft who is responsible for the CRJ on Steam: http://forum.aerosoft.com/index.php?/forum/596-crj-200-jrollon/

10.6.8 is way below system requirements, and more than 5 years old now. You have to use 10.9 or newer with the 64bit version. Upgrading your OS to 10.9 or 10.10 is free through using the Mac App Store.

You don't need to actually enter a SID (there are many airports that don't have any published departure procedures in the database), but you will need to select a departure runway at least.

The X-Aviation version has no alert sounds due to an incompatibility with an old version of Gizmo.

Click on the center of the GPS screen, or assign a keyboard or joystick command to sim/GPS/g430n1_popup Either one will do.

I don't know about X-IVAP. Starting to analyze a crash by eliminating factors one-by-one (plugins, scenery) is always a good idea though.

First step: Remove XSquawkbox and try again if it still happens. XSB64 is notorious for crashing in openGL functions.

I would start by updating to the latest stable version of X-Plane, which is 10.35. Then I would like to draw your attention to these two entries in your Log.txt: Loaded: /Volumes/G-DRIVE mobile/X-Plane 10/Resources/plugins/mac.xpl.This file should be deleted. Because it's a fat plugin, but it is not in the folder it belongs to, thus it cannot work. dlerror:dlopen(/Volumes/G-DRIVE mobile/X-Plane 10/Resources/plugins/Gizmo64.plugin/64/mac.xpl, 6): Library not loaded: @executable_path/../Frameworks/libcurl.framework/Versions/A/libcurl Referenced from: /Volumes/G-DRIVE mobile/X-Plane 10/Resources/plugins/Gizmo64.plugin/64/mac.xpl Reason: image not foundThis is the real reason for your trouble. Gizmo doesn't load because of a missing library. I leave it to the Gizmo exports to tell you how to solve this.

Kyle, this will work as long as you are still using OSX 10.8 Mountain Lion. Hold off upgrading to Mavericks or Yosemite until you can make the switch to X-Plane 10.

Does anyone of you listen to the BBC 4 radio sitcom "Cabin Pressure"? Not only does it feature great (voice) actors, but it's also fairly well researched for a sitcom. I simply love it. http://www.bbc.co.uk/programmes/b00lmcxj

crj200.xjm is a config file for the plugin xjoymap, I belive? The dataref that control the popups are: CRJ/pop/pfd CRJ/pop/mfd CRJ/popup/p_eicas CRJ/pop/seicas make sure those are the ones referenced in the xjoymap configuration file.