Dhruv

Standard ramp procedure when working Mesaba's Saab fleet was to GPU start 2, disconnect the GPU, then start 1. Lot safer to play chicken with one turning prop than with two!

Looks like you guys had a great weekend. One of these years I really need to get back down there and enjoy it with you guys!

The props, even on the B/B+ used to windmill all the time in wind during my ramp experience working the Mesaba fleet. We used to put a RON kit on overnight that would tie the props down.

This is my shocked face: .

Flown on: A300 A310-200/300 A319 A320-100/-200 A330-200/-300 A340-300 B717 B727-200 B737-200/300/600/700/800 B747-200/300/400 B757-200/300 B767-200/300 B777-200ER/200LR/300ER DC-9-10/30/40/50 DC-10-10/30/40 MD-82/83/88/90 RJ85 CRJ-100/200/700/900 E120 E135/140/145 E170/175 Saab 340B/B+ Flown: Cessna 150/152/172/182 Piper PA-28 Cherokee/Warrior/Archer Piper PA-28R Arrow Piper PA44 Seminole Beech C33 Bonanza CRJ-200 (simulator)

Alien abduction. Every week I keep wondering when they'll bring Alex back.

SOUTHWEST! If you don't do it Morten, I'll paint the whole fleet, special liveries and all .

They've taken a design icon that was preached as an instant classic and replaced it with what looks to have been done by a 13 year-old in Microsoft Paint.

Sounds like X-Plane for the past 10 years...

The .org store software doesn't allow the proceeds to be split between multiple contributors, so (for now at least), our liveries aren't included in the "Complete" collection by Will. I'm a bit disappointed that either he/nicolas chose to represent that pack as "complete" when our pack includes some of the more prolific North American paints for the -200. Either way, we've got at least one more pack planned that will include some more US liveries from varying vintages, so we'll see if they change their marketing tune or not.

You're free to do what you will with NZAA, Chris. If you do put an update out, we'd be happy to host it on the XP Jets website as well.

Toronto! Looks great!

If that's our scenery running in X-Plane 10, looks pretty good! Are those up-to-date photos from LINZ?

Keyboard entry into the FMS, hence the orange K in the corner

More accurate typeface, STAR/APPR now have to be executed to be entered into the flight plan.

Try intercepting the localizer at a 30 degree angle or less. The plane's autopilot might have a hard time with a sharper intercept angle than that.

You do realize that "Turn the Page" was just a warmed over cover of a Bob Seger classic right ? That being said, I definitely have a lot of respect for what Metallica has accomplished over the years.

Yeah sorry I haven't gotten back to you, Jim. Unfortunately I haven't been able to get the time off to go anywhere this weekend. We're chronically short as always at work, so I'm going to be stuck in Grand Forks.

Looking awesome. Bring it on!

Alex will love that.

Believe me I understand the complexities of plugin-driven displays and code just fine, Cam . Plugins or not, ideally if you can leverage a built-in dataref to drive a plugin system, it's often the better course of action than inventing your own unless you need specific custom functionality that the built-in data can't provide. That doesn't seem to be the case in this instance, but it's not my plugin. The only reason I was as harsh as I was in the first place was because there were a lot of misunderstandings being thrown about as to what the real plane does with the knob in the first place, which I attempted to clear up on two occasions with documentation from the manufacturer. Now that that's resolved, I'll leave this thread be at this point and wait patiently for a decision from Javier/Philipp. I've got some CRJ runs to make in the meanwhile, so I'm off to go enjoy the plane. I rarely fly anything else these days .

I appreciate the insight into your prioritization of tasks. You certainly seem to have a clear goal in mind, which is great! You should be able to just tie the spd knob to a default X-Plane dataref to swap between Mach number and knots. I believe the one you're looking for would be: sim/cockpit2/autopilot/airspeed_is_mach and have the manipulator toggle the boolean value.

Here you go. Same manual as you: Sorry about my word choice on the previous post. Believe me I appreciate the herculean task you guys have accomplished by getting the simulation this accurate in the first place. It'd be nice to get those last few inconsistencies sorted out!

Come on, Javier. Isn't one of the goals of the Take Command series to attempt to recreate the real plane as faithfully as possible? When someone provides you the documentation to support a change, why not make the change? You're interpreting "the way as it as said in the fcom" incorrectly, and I have CRJ-200 jumpseat AND simulator experience to back that statement up. A LOT of CRJ flying happens at altitudes below FL310 and is still performed using Mach numbers for performance. Are you seriously going to turn around and tell your customers that there is simply no way of changing the speed reference to Mach manually? If so, that's borderline ridiculous.

AP/FD Sync and synchronizing the speed bug selection are two different things. Pressing the button on the inboard control wheel syncs the AP and FD to the current attitude of the plane and then sets the bugs as required to maintain it. Think of it as a CWS switch (Control Wheel Steering). That allows the pilot to quickly set the autopilot to maintain the current flight conditions. That has nothing to do with the IAS/MACH selection switch actuated by pressing the SPD knob.