CRJ-200 Development
  • Content count

  • Joined

  • Last visited

Community Reputation

83 Excellent

1 Follower

About philipp

  • Rank
    Flight Instructor, Team Laminar/X-Plane
  • Birthday 03/18/1987

Contact Methods

  • Website URL
  • Skype philipp_muenzel

Profile Information

  • Gender Male
  • Location Wiesbaden, Germany
  • Interests flightsimming, programming, maths, classical music and opera

Recent Profile Visitors

6,546 profile views
  1. CRJ 200 FMS

    Just make sure you have both the latest Xsaitekpanels plugin AND (very impotant) the latest config file for the CRJ-200.
  2. CRJ 200 FMS

    We found that the SaitekPanels plugin prevents the FMS from working. There's an update available for XSaitekpanels that fixes that.
  3. Ram Air Turbine

    You have to call maintenance, because it cannot be restored by the flight crew. The plane is grounded until maintenance has resolved the underlying issue, stowed the RAT, and signs off the plane back into service. That's how it works in real life. In X-Plane, you need to re-load the aircraft.
  4. CRJ 200 FMS

    Take a look at the side panel on the left side wall on the pilots side. It's called the display control panel. On the top center there's two concentric knobs labelled FORMAT/RANGE. Turn the outer one (format) to the right to get to the NAV and PLAN views.
  5. Attached is the replacement CRJ200.acf for X-Plane 11 that fixes the engines idling too low. Replace the CRJ200.acf in the base folder of the CRJ in your X-Plane 11 installation with this file. Please do not try to use this with X-Plane 10, it won't work. CRJ200.acf
  6. Navigraph navdata update

    That is the default location the Navigraph FMS Data manager would have installed it in anyway. This location is used by a lot of add-on aircraft nowadays, as listed above.
  7. Navigraph navdata update

    Do not use the old mapping for the CRJ-200 from Navigraph FMS Data manager. It's for 1.5 and earlier. Use this cycle "X-Plane GNS430, 777 Worldliner (Ext/Prof), Flightfactor B757 Professional, VMAX B767-300ER Professional, X-Crafts Embraer E-175, Aerobask Aircrafts" even though it doesn't mention the CRJ, it is compatible.
  8. CRJ-200 knobs/switches inert XP10.50

    That shouldn't be a problem. I don't think the hackintosh has anything to do with it. I have changed so many components in my MacPro 5,1 it's basically becoming a hackintosh now. Plugins simply not loading is usually either a plugin conflict, a missing dependency, or plainly binary incompatibility (32bit plugin with 64bit X-Plane) none of which I would chalk up to running a hackintosh.
  9. Approaches incomplete

    I see what you mean. LFLL has a very strange encoding for the STAR, where it lists the same trunk route twice for the L and R runways instead of listing the trunk once with a "B" for both runways, as is the standard. Unfortunately, this is due to how ARINC424 data is converted to the various file formats for the different FMSs, and these converters are done by Aerosoft and Navigraph. This is one of the many reasons why for X-Plane 11 I have changed that whole process and now support 424 directly and wrote the converter myself, instead of leaving that to Aerosoft and Navigraph, which eliminates the possibility to have different encodings of the same data. If you try the X-Plane 11 FMC, which uses my new data flow, it of course works correctly: For a future pure X-Plane 11 version of the CRJ, I will obviously use this new infrastructure. For the current CRJ, which still supports X-Plane 10, I cannot do this.
  10. CRJ-200 knobs/switches inert XP10.50

    I see a lot of errors in this Log.txt, among others you have installed the XSquawkbox plugin into the Las Vegas scenery?? This installation of X-Plane looks seriously borked to me. The one most likely related to the CRJ is this error: dlerror:dlopen(/Users/nolimac1/Desktop/xp/X-Plane 10/Resources/plugins/shrink-wrap.plugin/mac.xpl, 6): no suitable image found. Did find: /Users/nolimac1/Desktop/xp/X-Plane 10/Resources/plugins/shrink-wrap.plugin/mac.xpl: mach-o, but wrong architecture That is the X-Aviation wrapper that has since been superseded as far as I know. The CRJ itself also appears to be an outdated version: lerror:dlopen(/Users/nolimac1/Desktop/xp/X-Plane 10/Aircraft/X-Aviation/CRJ-200/plugins/CRJAvionics/mac.xpl, 6): no suitable image found. Did find: /Users/nolimac1/Desktop/xp/X-Plane 10/Aircraft/X-Aviation/CRJ-200/plugins/CRJAvionics/mac.xpl: mach-o, but wrong architecture If it was the current version, it would read "CRJSE" instead of "CRJAvionics". My suggestion is to systematically go through the plugin errors in the Log.txt and remove those that don't load or are out of date. Then make sure to download the latest 1.7.1 version of the CRJ (which also works in X-Plane 10).
  11. Selecting an Arrival RWY with no STAR

    I understand what you mean now - I'm talking about the case where both an RNAV transition and a STAR exist from the same starting point and you want to use the RNAV transition but not the STAR. In this case, the points of the STAR are automatically overridden (deleted, actually), when you select the RNAV transition. You can achieve the same effect for a (non-RNAV) transition to approach by selecting an arbitrary STAR, then the approach and transition, executing, then de-selecting the STAR and executing again. This is not ideal, but it does work. The limitation "SELECT STAR FIRST" is a leftover from the 1.4 version of the CRJ, where the FMS was not as capable as it is today. With 1.6, I changed the FMS to support all that, but I never removed the scratchpad warning, despite it actually works now. The somewhat complicated solution I offered above does work in CRJ 1.6 onward, and allows you to fly an RNAV or non-RNAV transition directly to final approach without STAR.
  12. Selecting an Arrival RWY with no STAR

    Not sure why you say it's impossible - it is actually quite common in Europe to fly RNAV transitions instead of STARs, like for example this in EDDL: In that particular example, the DOMUX STAR is overridden by the DOMUX arrival, so the STAR isn't used. Same thing in EDDS with the BADSO STAR, and several other airports in Germany that I use regularly for testing.
  13. CRJ-200 v1.7 Issues (XP 10.5x)

    I have tested on XP10, 11, Windows and Mac and do not see any throttle problem neither with 2x sim speed (sim time running faster) nor with 2x ground speed (sim time runs standard but plane covers more ground distance). I was also reliably getting the plane launched in the air by selecting an approach scenario, pressing the pause key, waiting for all the systems to initialize (note that this requires the "start with engines running" setting to be set), and then un-pausing the sim to fly the approach. As I said, this kind of "duplicate assignment" where one key triggers two unrelated functions is usually the sign of a bad X-Plane preference file. Which is cleared by deleting the files under $X-Plane/Output/preferences
  14. CRJ 200 FMS

    Have you checked the yaw dampers?
  15. CRJ-200 v1.7 Issues (XP 10.5x)

    1) sounds like a broken preference file to me, like you are triggering two commands with one button. See if the same happens if you change the simulation speed directly via the dataref (using DataRefEditor). 2) Starting up the plane in a situation other than "cold&dark" or "engines running" is not supported and will lead to unpredictable results.