cruster

Downloaded and installed. Will check it out on my next flight in about an hour. Many, many thanks Javier and Cameron!!

These are great, Javier! Can't wait to have some additional liveries to choose from. How about a United Express? Or maybe Corporate Airlines? I love the 'wear and tear' on this one...

I've mentioned this a couple of times. With the RPM lever at "Flight" (100%), the prop RPM % will slowly climb up to 103% (the white triangle), which is the lower limit of the governor, IIRC from the manual. So far, I haven't had a problem with anything breaking in flights of one to two hours, but I wonder if that will eventually happen.

Unfortunate. As a forum owner/operator, I know this kind of thing is a lot Less Than Fun. On the other hand, as long as they have it down, I hope they can figure out how to upgrade their Tapatalk install.

I appreciate the info/guidelines from all of you. My first couple of flights in the -32, I felt like a test pilot. There was a lot of "Hrmm, I guess it doesn't respond well to control inputs below about 105 kts" and "Stalling it onto the runway with the stick pusher engaged is not advisable" going on. Putting the props at 97% is an interesting comment, though. As I explained in my first post, I put the RPM lever at "Flight" (100% setting) and leave it there, as it doesn't seem to do much otherwise. In my last flight, I observed the same behavior, in as much as the prop RPM sat at 100% through takeoff and most of climb, but then floated up to the 103% triangle for the rest of the flight. This time I did not disable the TTL computers above FL140, just to see if that was the culprit. It wasn't. For me, the process is: RPM lever to "Flight", flaps at 10%, power up to wherever I can get it while keeping the EGT below 650. Rotate around 110, climb at whatever rate happens until I get everything cleaned up and the AP engaged, then dial in 2000 FPM. From that point on, I use the Power lever to manage EGT. For cruise, I keep the EGT just a hair under the 650 red line and everything seems OK, speed and fuel-burn wise. At TOD, I set and arm the altitude selector, hit VS and dial in appropriate FPM (I've been going around 1200-1500, depending on airspeed...airspeed / 2 * 10 rule of thumb, with some adjustment based on gut feel) then use the Power lever to manage airspeed (below the green/white mark). Once I hit pattern altitude I juggle flaps and power and try to stay up around 150-160 kts, otherwise I feel like the plane is made out of rubber (no crispness to the controls at all). Once established, I drop the gear, power up a bit to offset the drag and try to put it on the ground in one piece. Oh, and up until Intrance's post, I had only been using two notches of flaps on approach. I'll give it max next time and see what happens. My next 'test flight' (haha) I'll actually try to land with the stick pusher disabled. That can be disabled by clicking on the glare shield lights, even if the lights aren't illuminated, right?

The BAe 31/32 is an excellent product, Javier. Thanks for making it available! I have a quick question and I'm hoping you know the answer off the top of your head and won't have to type for an hour and a half. What is the correct cruise configuration for this bird? I just flew about 300nm across the middle of Africa and managed to average about 255 kts ground speed (225-230 kts indicated) at FL160, which is great, in light of the fact I was only burning about 100 gal/hour. However, the prop RPM was initially laying right at 100% but eventually creeped up to the white triangle (103%, lower limit of overspeed governor, IIRC). EGT was also just about 640, with % torque around 65-70%. Pulling the RPM levers back about 1/2 way to the "Taxi" mark didn't seem to have any effect on Prop RPM as far as the gauge was concerned, BTW. I think I remember reading in the manual that "Flight" was 100% prop RPM and "Taxi" was 72%, so maybe there's not a lot of adjustment there to start with. In retrospect, I don't think the prop RPM climbed past 100% until after I turned off the TTL computers (past FL140). Am I setting things (close to) right?

Great shots. Out of curiosity, where did you get an MD-900? That shot, in particular, looks very realistic!

On a more serious note, I was tempted to go pick up the 337 to play with. I'd much (much) rather have this. Mind made up.

"Out Now!" Truth in advertising? heh

I thought that meant it was available, and now I've grown tired of refreshing the X-Aviation site.

I don't know about anyone else, but I uncheck "verbal ATC" and "text ATC" in the Xplane sound configuration dialog box. If I don't, I get VATSIM via XSquawkbox and Xplane ATC via, well, Xplane. I can see where having both on might cause some confusion.

Just logged on (via Tapatalk) and was pleasantly surprised. Thanks for making it functional again! I've gotten to the point where I mostly avoid boards anymore that aren't Tapatalk or Forum Runner compatible.

Is there an issue with the Tapatalk client? Since the update to the board software, I've been having a problem getting full threads in the app. For instance, the BAE Jetstream thread will show as "new" but when I click on it, it's only seven pages long and the last post is from late summer. I know I posted on that thread two days ago, but even my post doesn't show. Strange.

Definitely on my "must buy" list.

I don't have the Duchess, although I was tempted to pick it up during the sale (I did get the DC-3, though!). The thing that bothers me most about the XP development model is that the platform is a moving target which may or may not break the payware I've spent good money on. I don't have a problem with XP9 payware not functioning properly/fully/at all in XP10. In my mind, that's the same situation as the shift from FS9 to FSX. A lot of FS9 payware simply didn't work without a bunch of monkeying around in FSX. Same deal with XP9 and XP10 at this point, so it's not unprecedented, or unexpected. Developers who provide free XP10 updates for XP9 customers are going well above and beyond, in my opinion. What is a problem is that a payware model that works in XP10.xx[whatever] may suddenly break in magnificent, entertaining ways with the next update (even with beta updates off). See the various threads on the CRJ200 for an example. I simply don't have time to build a new matrix of base install+patches+updates+configuration changes+plugin troubleshooting every time an update for XP10 comes out. All of that being said, the fact that you, Goran, took the time to investigate this roll problem not only with your model, but with default and other payware models speaks volumes about your commitment to the XP ecosystem and your customers. I think maybe I'll go back and pick up the Duchess today. (Please forgive the OT portions of this post)

I'd actually rather have this than the upcoming Carenado 337. I will be keeping an eye on the X-Aviation store.

I'm in; should be a nice little workhorse in FSE.

I can confirm that the CRJ-200 works with a (fairly basic) profile when used with the Saitek MFD plugin and X-Plane 9.6x (sorry, can't remember the actual version). "Saitek MFD Pro" plugin is not, however, "XPSaitek" plugin. Maybe switching is an option for the OP though?

LOL. I actually checked X-Aviation and the JRollon site before coming here this morning. JRollon still shows the CRJ200 with the "W.I.P." stamp when you mouse over it and X-Aviation still says "Coming Soon" (and if you try to put it in your basket, nothing shows up...something else I try every time I check there).

I haven't tried this yet. Did you ever get it working? EDIT (next day): I made a plane.txt with the following in it and it works in Goodway: xplane_certified=945 author=JCX Design author_web=http://x-aviation.com release=945 release_date=07 31 2010 plane_constructor=Cessna plane_type=C400 plane_full_name=Cessna Corvalis TT plane_compagny=JCX cruise_altitude=20000 cruise_speed=181 climb_rate=1400 climb_speed=110 descent_rate=1500 descent_speed=110 maximum_range=1250 fuel_max_onboard=106 fuel_max_consumption_hour=20