philipp

In an ongoing effort to make our planes better, we not only want to improve what you see, but also what you hear. Today we took an important step in this process: We are proud to announce the collaboration with the leading provider of high-quality FSX sound packs, Turbine Sound Studios, in a joined effort to bring their astounding sounds into the world of X-Plane. Turbine Sound Studios is renowned in the FSX community for their highly acclaimed aftermarket sound packs for numerous jets, helicopters and turboprops and is also a winner of the simFlight award. With their first-ever appearance on X-Plane, Turbine Sound Studios is to provide a full range of engine, cockpit and environmental sounds for the JRollon CRJ-200, thus greatly enhancing your sim experience. Turbine Sound Studios also has a YouTube channel: http://www.youtube.c...er/mrsubmission As a first step towards a more immerse atmosphere, we are releasing an update to the CRJ-200 including two new custom plugin-driven sounds to ensure compatibility on Windows, Mac and Linux. The update will ship this week, together with corrections and bugfixes, as the second service pack to the CRJ. Cheers to all CRJ Pilots, Javier and Philipp from JRollon Planes Christoffer from TSS

Help! Seems I've lost my moderator rights in the transition of the software... Well, please post any follow-ups in the linked thread.

Thanks Cameron for clarification. aerot, I'm taking care of you case and posted the answer over at X-Plane.org: http://forums.x-plane.org/index.php?showtopic=53456 If you haven't already, create an account there. In order to keep the .org and X-Aviation discussions separated, I'm closing this thread. Regards, Philipp

I don't promise anything here, but I reassure you our goal is, and always will be, to become better. Currently, I'm however working solely on FMS stuff, because this is what you use ALL the time: Controller tells you to go into hold somewhere, due to traffic, and you want to be able to punch that into the FMS... Currently seems more important to me than being able to change the engine sync parameter, which makes little sense anyway unless you have two separate hardware throttle levers. Philipp

In the real CRJ, you have to separate means for controlling the Rudder and the Nosewheel: -the rudder pedals move the rudder -the steering tiller moves the nosewheel However, there is a setting where the nosewheel is connected to the rudder pedals, if only to a certain degree and limited by speed. The exact values I would have to look up in the manual, but think of it as a pretty direct connection at low speeds, fading when you accelerate (for takeoff). The real CRJ has the N/W STRG switch to disconnect this automatic entirely (N/W can ONLY be steered with the tiller). As no one we know has a joystick, rudder pedals AND a separate steering tiller at home we saw little need to implement this feature for our simulation. Philipp

Sorry Peter, not yet available as datarefs. See my post to your other question about the possibility of external displays. Philipp

Well, the FMS will do what you tell it to. It doesn't save you from errors. The only way to reset a TGT thrust is by just hitting the "DELETE" button and then pressing the LSK adjacent to the TGT thrust setting. After that, you have the full range of the throttles back. Philipp

Hi Peter, You want to have the CDU console (CDU screen + keypad) on a second monitor outside of the X-Plane window. Am I understanding this right? Currently, this is not supported. But I am working on a technology that will allow me to "detach" the overlay windows (popups) and have them outside of X-Plane, or on a second monitor. This is a shot from the current development, where I use this with an INS CDU: https://picasaweb.google.com/philipp.muenzel/7231102?authuser=0&feat=directlink You can see the gauge inside X-Plane and the detached display outside X-Plane (and the real unit sitting besides on the table ). Don't ask me when this technique will make it into the CRJ though. Cheers, Philipp

If you have a Log.txt please attach it. Other than that, I second Cameron's and Javier's advise to not tamper with the installation by moving files around. When in doubt, trigger the deinstallation, then remove any files you manually copied or moved, and then do a fresh reinstall. This must work. Philipp

I run my CRJ on a weaker system, you should be fine! Philipp

The crash log shows an X-Plane scenery crash, not a CRJ Avionics crash. Do you have any custom scenery installed for Valencia? Maybe your system is running out of VRAM with the CRJ and a highly detailed scenery. You might try lowering the texture resolution by one notch. Philipp

Unfortunately, the crash log looks rather unspecific. Can you recreate a situation that triggers the crash? Like, a flightplan and a point in the flightplan where the crash is likely to occur? Philipp

This is a carrier option. Airlines can choose whether they want the software with the single-cue "inverted V" or the dual-cue "cross-hair". Personally, I like the cross-hair a lot more, but if there's sufficient interest I could make the single-cue available in a future update. Philipp

There are two different plugins for the Saitek stuff. One does work, the other does not. Besides TOBS, I think wooweezowee has got it to work. Could you please post a download link to the one that crashes? Philipp

Your problem is probably that xjoymap accesses X-Plane's autopilot directly. Thereby you bypass all the CRJ logic and confuse the system. This won't work! You must setup your config so that the CRJ datarefs for the autopilot are triggered. All datarefs for the CRJ are published here: http://forums.x-pilot.com/index.php?topic=2256.0 Philipp

If I'm not mistaken, the ND shows "TRK up" while the HSI on the PFD shows "HDG up". But whether there's an additional "ball" on the ND I would have to look up in the Collins Manual. If there is one, I will add it. Philipp

I'm really surprised the CRJ loads at all. Intel integrated HD graphics are a very bad choice for X-Plane, as has been discussed many times on various forums. This has gradually improved in the past, but not to a point where I would really recommend them. The problem is that the Intel driver has a very poor implementation of the openGL standard. It does better with the Microsoft DirectX, but X-Plane and thus the CRJ of course use openGL. If you look for recommendations for X-Plane, you will almost always find the advice to use Nvidia cards on Windows, and ATI cards on Mac. These perform best for X-Plane. Intel drivers have improved a bit, but you cannot expect an integrated chipset that uses shared memory to perform as good as video card with dedicated video memory. Philipp

Okay, I see what is wrong here. It is the same bug that Woweezowee reported: When trying to re-select a SID without re-selecting the runway, the FMS crashes. Well, it should not crash of course, it should just do nothing. I will correct this in the future. Philipp

Hi David, this doesn't make sense. There is no such thing as a "1017" or "1015" cycle. The CRJ was shipped with 1103 (2011, 3rd cycle) and now we have 1107 (2011, 7th cycle). Please have a look at this file X-Plane/JRollonPlanes/Navdata/cycle_info.txt In the first line it says "AIRAC cycle : xxyy" Please make sure that xxyy is the number you downloaded (1107 presumably). If it is not, you makde a mistake installing the update navdata. I can confirm that the NINOX and MANDY SIDs of LEVC load without crashing on 1103 and 1106 here. You said "after loading all fixes and waypoints", so could you please post the entire flightplan route that you entered here? Also, did you select a takeoff Runway BEFORE selecting the SID? SIDs may or may be not available for all runways. So can you try the two runways of LEVC separately to narrow down this problem. Philipp

I just tried it and found nothing wrong. NINOX4A loads perfectly for me. Also, your crashdump makes no sense in relation to SIDs. Which AIRAC cycle do you use? Did you update from Navigraph? Just to be sure, can you confirm it occurs only with the NINOX4A SID or also with others? Next, if it is indeed a problem of this SID, can you post the contents of the X-Plane/JRollonPlanes/SidStar/LEVC.xml so I can check it whether it is a problem of the new AIRAC cycle. Philipp

Hi folks, I want to give you a quick update from the development. The most annoying issue of compatibility is, as you all know, the CTD that occurs when XPUIPC is used with the CRJ. We had an intensive debugging session together with Torsten "Spyy", the developer of XPUIPC. We found that the underlying issue as a problem of XPUIPC, not of the CRJ. In short, XPUIPC is doing something that is illegal in the first place, but as long as there is little load to X-Plane, it still works. So nobody ever noticed XPUIPC is doing something illegal. Now the CRJ exploits X-Plane's limits in various ways. It stays within what is legal, but to its maximum extend. And now the error in XPUIPC is revealed and leads to the crash. Think of it like a street with cars parked at the streetside. There is a white line on the concrete separating the road from the parking cars. This white line is clearly specified by the X-Plane SDK. XPUIPC is parked slightly across this line. If you drive a Beetle through the street, nothing happens. If you drive a big truck through it, XPUIPC gets bumped and scratched badly although the truck doesn't touch the white line. As soon as there are more projects in X-Plane behaving like big trucks, more errors like these are going to surface in software you now believe works perfectly. We provided Torsten with all the necessary information to fix this issue, along with a developer copy of the CRJ to test things. I'm sure he will come up with a solution soon and park XPUIPC again in the right place. But that shows we need the developers to collaborate. We mailed the Conex Sound engine developer twice, but got no answer. If you want plugin conflicts to be solved, write to the developers and urge them to contact us. We can provide with free copies of the CRJ for testing, and also we are very good providing debug information that helps them. If you are developer working on new stuff, make sure you obey to the guidelines for X-Plane plugin threading. And by obey I do not mean fire up X-Plane, see that it doesn't crash and assume everything is right. Multithreading doesn't work like this. Bugs surface under high load and tight timing conditions. All the best and have fun "up there", Philipp

There are as many "real" checklists as there are airlines that operate the CRJ. Every airline has its own company procedures. Every airline orders their CRJs with different carrier options. You get the picture ... Philipp

Kamil, the only common denominator I see here is that you are both using AMD processors, while MdMax and I use Intel. It might be that the CRJ plugin makes use of optimizations that work great on Intel, but less so on AMD CPUs. What is strange however, is that this issue only affects Linux users. I have no record of a Windows user on AMD having the same problem. So it might be a problem of the scheduler, who knows ??? The only thing I can offer you is a specifically AMD-optimized plugin build to test. It would require you to exchange your CRJ and vascore plugins in the file manager, without an installer. As you are Linux users I have some confidence you can do this If you want to test this, dop me a private message. If this proves helpful, we might include it in a future update. Philipp

Hi xfan, First, the Log.txt alone is rather useless. When X-Plane has a crash to desktop, there is a crash_log.txt generated that you should post alongside with the Log.txt. Only when I see both of them I have a chance to narrow down the root cause. However in your case I have a very good idea of what is going on. You must remember that there are two kinds of plugins: global plugins and per-aircraft plugins. You already ruled out the global plugins given the procedure you described, this is fine. Then there are plugins tied to specific aircraft, that get only loaded when this aircraft was loaded once in your sim session. And here I see a possible culprit: You use the ND Art BK117, which in turn uses the Dreamfoil sound engine. The Dreamfoil engine is known to be incompatible with the CRJ. This issue is already under investigation with the developer of Dreamfoil, so you can expect a fix in the next update. For now you can fix this only by not loading CRJ and Dreamfoil in the same sim session. About your unstable framerate, as you said that it is better in the demo version it might be related to some of the other aircraft loaded. Also, overall fluidity is greatly improved by limiting your frame rate. 60fps is completely useless. I found that using X-Plane's option to limit to 30 (half the rate of a 60Hz monitor) gives the most smooth experience, as the frame rate stays at 30 then. For comparison, I run my Mac tests on a 2.4GHz dual core with smooth 25-30fps, so you should be able to fly on a 3.3Ghz six-core without any problems. It is a known issue however, that the refresh rate is worse when the LEGS page of the FMS is displayed in contrast to e.g. the FPLAN page. While this has been improved in the 1.1 update, it is still noticeable, if only barely for me. Could you test if what you call "jerky" depends on the LEGS page being displayed on the FMS? Last, your flightplan issue. This has been discussed before. The FMS stores and loads ICAO routes. This is nothing more than a text. If the text contains an ambiguous waypoint, even when tied to an airway, how would the FMS be supposed to select "the right one"? Yes, it might just select the "geographically nearest" one or "most likely" one, but this is dangerous, and by all means forbidden. I would like to remind you of the American Airlines 965 accident, where they flew a perfectly working 757 into a mountain by just selecting the "nearest" waypoint when resolving an ambiguity. Ouch. Now I hope you understand why we can't automatize the WPT SEL page when loading an ICAO route. What we could do instead is emulate the function where you get your fligthplan as a company route, that is stored on some kind of floppy disk that is read into the FMS like it is done for an AIRAC database update. As far as I know, these routes are stored in an unambiguous format where these problems cannot occur. I would have to check my manuals to see how to implement this correctly, though. This is certainly a feature I want for future CRJ updates, I just have to figure out some clever way of simulating you inserting a floppy disk with the company routes Regards, Philipp

Hi MdMax, I analyzed your flight and found the following: The FMS is doing perfectly right, just the MFD is drawing utter nonsense. If you just leave FMS mode on, the autopilot will fly the flightplan exactly as expected, and guides you safely over the 180° meridian and to the destination airport. You just have to trust it and ignore the MFD, which will be showing a wrong track. However, using the MFD in HSI mode will show perfectly okay. Thanks for the detailed bug report. I will see what I can do to the MFD projection. Philipp