JGregory

That should be the case… and… Ben Russell has recently done some amazing things with optimizations of Gizmo, which should help with the performance of ALL Gizmo enhanced aircraft!

Ned, Yes, you can do all your flight planning in 2D if you like. Not sure why you lost your flight plan… that shouldn't happen.

I suggest you contact Cameron at XA... http://www.x-aviation.com/catalog/contact_us.php

Are you sure the aircraft is activated? Part of the DRM disables the fuel selector.

This is something that is planned for the Saab. We do not have a release date for the upgraded radios yet.

The Lat/Lon waypoint entry/visibility issue has been resolved and will be included in the next update (1.6).

Correct… existing flight plans can be loaded and should work fine. It's the waypoint entry process that appears to have an issue… I am looking into it.

Andy, The entry for lat/lon is formatted as: +00.000 +000.00 You have to enter the + or -, plus the digits. You do not need to enter the decimal points. After you have completed the lat portion the cursor will automatically position at the +/- position for the lon entry. I believe the display in the Waypoint Entry Window is cutoff and you will only be able to see the lat portion of the entry, which is something I need to fix. I haven't made a lat/lon entry in a VERY LONG time, so be warned there may be bugs that I am unaware of. Currently you can not enter altitudes for each waypoint. This feature is not implemented. This version of the G1000 did not have VNAV, so they would only be advisory anyway.

Andy, It sounds like you changed the "Page" that you were displaying. This is controlled with the large FMS knob. It's easy to click on this by mistake when you are clicking on the small knob to enter waypoints.

Andy, Please have some patience… many C400 customers are doing exactly what you want to do without any problems. Make sure you are following the instructions on Pg. 137 of the POH titled "CREATING AN ACTIVE FLIGHT PLAN". Note that the button to pop-up the Ready Pad is only available in 2D cockpit mode (as seen on Pg. 137 of the POH). In 3D mode you would use the Read Pad in the center console (there is no on-screen pop-up in 3D mode). All flight plan entries are done on the MFD, not the PFD. Rest assured that you can enter a flight plan and do "real nav" just as you wish. Thousands of customers are!

Andy, I don't have time to outline all of this for you right now. It's all in the manual included with the aircraft... see "entering a flight plan".

Two different electric buses.

Ummm… OK…since you have taken away the option of telling the truth I have nothing to say… and (as per your request) I can't give you a new date either. Does that work ?

New link…. http://www.flightvideoproductions.com/columbia_400.htm

Your post asking "anyone?" was certainly not specific enough to make sure viewers would know what you were asking about, regardless of the thread topic and especially since you had asked for links only two posts prior.

Anyone what? The links you requested are in the post right above your last.

Please refer to the speed charts on pages 76-81 in the Charts.pdf. There are several variables to be considered including altitude, power setting, weight, OAT, etc. I can easily find mmerelle's numbers, as well as yours, within the normal parameters. If you find the performance is significantly different from the charts, please document ALL your flight conditions and report them back to us.

Vmo is the MAX operating, or "allowable" airspeed… this does not mean the aircraft can, will, or should get to that speed, it is simply a number that should not be exceeded. You should use the Charts.pdf document to find the speed ranges at various altitudes and power settings.

This is something that we have planned, but it will not be in the next update.

No.

CTOT will NOT engage below 64%. The Throttle Levers DO NOT have to be at EXACTLY 64%. Try moving the levers past 64% and see what happens. BTW… you do have the CTOT switches turned on, and the % torque dialed in, correct?

Next Saab Update: • Fixed bug in anti-skid system preventing user from applying brakes (HotFix 2/13/14)• Fixed bug where changing the NAV selector would not display the proper annuncation on the EADI.• Fixed bug where Glideslope was not being recognized when switching between NAV1 and NAV2.• Added NAV2 radio test logic to glideslope display.• Adjusted reverse/beta/feather/norm modes.• Adjusted sound engine to handle negative gain.• Adjusted fuel crossfeed logic.• Logic for Xvalve and bleed valves re-written.• Changed bleed air and power requirements for proper operation.• DC selector dial reworked to be more user friendly.• AP engage delay time reduced.• Adjusted engine oil pressure warning parameters.• Corrected logic for determining valid signals for nav radios.• Adjusted logic for when the Altitude Advisory speed is displayed on the EADI.• Corrected fuel pump logic on engine failure.• Autocoarsen logic revised to be more accurate per AOM.• OBS1, OBS2, Heading, and Altitude Selector manipulators changed to be more user friendly.• Fixed nose gear tires showing through the gear doors when retracted. … and maybe more

Will it break anything?… no. Is it supposed to do that?… no. Will this be fixed in the next update?… no. As a workaround simply press the AP disco button on the yoke and it should canx the annunciation.

Oh! I have slipped the surly bonds of earth,And danced the skies on laughter-silvered wings;Sunward I've climbed, and joined the tumbling mirthOf sun-split clouds, --and done a hundred thingsYou have not dreamed of --Wheeled and soared and swungHigh in the sunlit silence. Hov'ring thereI've chased the shouting wind along, and flungMy eager craft through footless halls of air...Up, up the long, delirious, burning blueI've topped the wind-swept heights with easy graceWhere never lark or even eagle flew --And, while with silent lifting mind I've trodThe high untrespassed sanctity of space,Put out my hand, and touched the face of God. … John Gillespie Magee, Jr

Enrico, We are aware of this. It has already been fixed and will be in the next update, which should be out within the next week.