Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

COMMANDER 114 ISSUES

Featured Replies

I've ruled out the controllers for the EGT / Mixture problem by using keyboard only, same problems. Also, did complete reinstall with 2 service packs same problems.
Try calibrating them-especially feather position.

Geofa

WANTED DEAD OR ALIVE-the best Flight Sim!

  • Replies 73
  • Views 28.1k
  • Created
  • Last Reply

Top Posters In This Topic

Try calibrating them-especially feather position.
Yeah ...just try re-calibrating all your hardware over and over again. Surely nothing is wrong with thwe Carenado Baron 58 FSX ..right???A couple other sim sites have now published reviews on the Carenado Baron stating the untypical / unexpected flight characteristics it has. Guess it IS a broken product and it's not just me. That'll PO the moderators for sure..

And what have the wrong stall characteristics to do with your inability to feather the prop ???

Hi Folksthis is my first time on this Forum.Re Carenado Commander 114 I have quite a few FSX Carenado GA's as from experience they seem to look and work really well compared with other companies offerings. I have recently purchased the Commander 114 for FSX and have a few problems with the panel as follows. Mouse used to operate.The OBS switch labelled "Course Select XXX" VOR1 will not move the compass card properly as does the VOR2 OBS which works just fine. The ADF Heading Knob labelled "ADF bearing to station" does not move the compass card properly either The Heading Hold Selector doesn't move the Heading Bug properly on the DG. By properly I mean the card/ fidgets a small amount in random directions. If the operation was as the VOR2 I would be satisfied.The the Century III Autopilot.The following items do not move from home position. The cursor does change to a hand meaning to me there is an animation expected.Roll Left & Right Knob.Pitch Command Wheel.Lateral Guidance Switch.Apart from that list other AP functions work. I have read the Autopilot Operation PDF and d/l'd the centuryflight.com/manuals/CENTIII.pdf Must be something I'm doing wrong. Ideas would be appreciated.

Yeah ...just try re-calibrating all your hardware over and over again. Surely nothing is wrong with thwe Carenado Baron 58 FSX ..right???A couple other sim sites have now published reviews on the Carenado Baron stating the untypical / unexpected flight characteristics it has. Guess it IS a broken product and it's not just me. That'll PO the moderators for sure..
I have to admit this is getting downright humorous. You do realize that stall characteristics have nothing to do with feathering a prop-which is surely on your end since others don't have the problem.By the way-it isn't just stall characteristics that are off on the fm...As for the mods-yep-getting complaints from others about your attitude.

Geofa

WANTED DEAD OR ALIVE-the best Flight Sim!

Try calibrating them-especially feather position.
Thanks Geofa,It looks like the EGT/mixture and prop feather issues are due to controller calibration issues after all. Stupid me! :Black Eye:I'm able to get one prop into feathered postion, but the prop lever is still in the wrong position. I'll have to get the saitek proflight throttle calibration program matched with FSUPCI.There is some light in the tunnel. :( Thanks,Billybob

BillyBob :biggrin:   

David M. Edwards

Dell Alienware Area 51-R5: Intel Core i9 7980XE (18-Core Central Processing Unit [C.P.U.]), 64 Gigabytes (GB) of Dual Channel HyperX DDR4 at 2,904MHZ, 2X Nvidia GeForce GTX 1080Ti (11GB GDDR5X, each) in Scalable Link Interface (S.L.I.) or parallel configuration, 1,500 Watt power supply, 3x Solid State Drives (S.S.D.), Track Infrared (I.R.) 5 head tracking head gear and receiver (Natural Point, Corvallis, OR. United States of America [U.S.A.])  and a Dell 4K Ultrasharp 32 inch monitor.

Lockheed Martin Prepar 3D version 4.4 (P3Dv4.4), Addons And Updates GALORE! 

KPDX (Portland, OR), KHIO (Hillsboro, OR)  United States of America, Planet Earth..

Thanks Geofa,It looks like the EGT/mixture and prop feather issues are due to controller calibration issues after all. Stupid me! Black Eye.gifI'm able to get one prop into feathered postion, but the prop lever is still in the wrong position. I'll have to get the saitek proflight throttle calibration program matched with FSUPCI.There is some light in the tunnel. :( Thanks,Billybob
Glad it finally worked-getting the controls to work/calibrate properly can often be a challenge.

Geofa

WANTED DEAD OR ALIVE-the best Flight Sim!

Glad it finally worked-getting the controls to work/calibrate properly can often be a challenge.
The B58 is the only one I've had a problem with the controllers. All the other planes work fine. Perhaps the B58 is more sensitive. Anyway, hope getting this fixed in the B58 doesn't screw up all the other planes.

BillyBob :biggrin:   

David M. Edwards

Dell Alienware Area 51-R5: Intel Core i9 7980XE (18-Core Central Processing Unit [C.P.U.]), 64 Gigabytes (GB) of Dual Channel HyperX DDR4 at 2,904MHZ, 2X Nvidia GeForce GTX 1080Ti (11GB GDDR5X, each) in Scalable Link Interface (S.L.I.) or parallel configuration, 1,500 Watt power supply, 3x Solid State Drives (S.S.D.), Track Infrared (I.R.) 5 head tracking head gear and receiver (Natural Point, Corvallis, OR. United States of America [U.S.A.])  and a Dell 4K Ultrasharp 32 inch monitor.

Lockheed Martin Prepar 3D version 4.4 (P3Dv4.4), Addons And Updates GALORE! 

KPDX (Portland, OR), KHIO (Hillsboro, OR)  United States of America, Planet Earth..

'Ello, 'ello, 'ello; I thought this thread was concerned with the Commander 114. How did a Baron (one "r", by all that's holy) come to be involved?Jist askin',Fritz

After $32.95 and 2 service packs.I nominate the Carenado Barron for the Avsim 5 Cow xxxxx award!Below is my latest request from Carenado, No response yet.Dear Carenado,I’ve purchased the Barron, and have installed both service packs. I report the below squawks, please fix,asap.1) Mixture / EGT modeling on both engines are wrong. The general principle for the mixture controls is to DECREASE the fuel to air mixture ratio. Upon leaning the both mixtures the full range of motion, there is an INCREASE in fuel flow for both engines where there should be an overall decrease and not an increase of fuel flow. Also, on engine #1 (left) the final bottom 5% allows for some leaning but ultimately results in engine fuel cut-off because the extremely narrow range of mixture function. Engine #2 (right) is slightly better than engine #1. However, both mixtures should lean overall there full range of motion forward to aft resulting and overall decrease in fuel flow to both engines and increase in EGT up to the point of max lean “Peak EGT”.The Engine #1 (left) engine mixture problem makes the aircraft nearly unflyable and the engine fuel is cut-off upon leaning.2) Neither engine allows for feathering! Neither prop (pitch) lever will move into the feathered position. Thus, not allowing for single engine operations.3) Stall characteristics are poor and nearly non-functional. The aircraft PLUMETS at greater than 60 degree nose dive before stall recovery initiates. Upon release of back pressure the aircraft should immediately begin stall recovery. The aircraft should be in a greater than 60 degree nose dive before the stall recovery begins.Best,
Well, since I just bought the "Barron" (or, "Baron" as some like to call it, including Beechcraft for some reason) Big%20Grin.gif) and have flown it a bit, maybe I can help out a bit here. Re #1 - are you sure you aren't reading the EGT gauges and not the FF gauges? I didn't see any issues in my machine and the EGT's did behave as you are suggesting the FF gauges do, which is correct. Insofar as the mixture controls being able to lean over their full range of motion, they can. You lose your engine(s) if you come too far back for the altitude of course. But, for some strange reason, this will also happen with the simulated aircraft as well. Bottom line is, you cannot come full back (or anywhere near it at low altitudes) and expect to keep the engine(s) running. How this makes the aircraft unflyable does escape me, unless of course you lean too far and the engines quit. The aircraft remains fully flyable... until you touch down that is :Whistle:For #2, my props feather. I think you solved this though, so I won't comment further.For #3, there's an easy answer to that too. Don't stall the "Barron"! In all my time flying "Aztrucks" I don't ever once recall stalling that airplane, even in checkouts for my employer. Frankly, if it doesn't behave correctly, who cares? Stalls and spins are for Decathalons and other aerobatic aircraft. IRL if your boss or instructor ever found out you accidentally stalled a "Barron", you'd probably be fired/fail the checkride. You should never, ever get even close to the stall speed in that class of aircraft, even when doing Vmc training. Don't worry about it.Lastly...
I thought this thread was concerned with the Commander 114. How did a Baron (one "r", by all that's holy) come to be involved?
...I was kind of wondering that myself ^_^Don't know if that helps, but maybe I'll check over on the "Baron" forum to see since that's where the Baron info really does belong. In all honesty though, I rather like this Baron. I do enjoy flying it quite a lot. FWIW.
Don't stall the "Barron"! In all my time flying "Aztrucks" I don't ever once recall stalling that airplane, even in checkouts for my employer. Frankly, if it doesn't behave correctly, who cares? Stalls and spins are for Decathalons and other aerobatic aircraft.
Hi GlennThe glaring problem is not the stall itself, but that it occurs at a way too low angle of attack. You can neither flare the Carenado Baron during landing or rotate at the correct speed on take off with the default air file.But AFAIK you are using the new airfile anyway.....
  • Author

Guys this thread has gone off topic. As much as the info about the baron is absolutely fantastic, remember this is for the Commander.CheersRoss

Intel Core i7-3770K @ 4.4GHz|Asus Maximus V Extreme|16Gb Ballitix Tracer @ 1866MHz|EVGA GTX680 SC Signature SLI|Asus Xonar Pheobus|Custom Watercooling|Corsair AX1200W PSU|CM Cosmos II

Hi GlennThe glaring problem is not the stall itself, but that it occurs at a way too low angle of attack. You can neither flare the Carenado Baron during landing or rotate at the correct speed on take off with the default air file.But AFAIK you are using the new airfile anyway.....
Ahh yes. If that's what he was referring to, then absolutely. I had the feeling he was more commenting on what happens after you enter the stall. Good point, and yes, I am using the updated file, which works beautifully.Thanks :(
Guys this thread has gone off topic. As much as the info about the baron is absolutely fantastic, remember this is for the Commander.CheersRoss
Good point, and I think I made reference to that in my next to last post. You are quite correct though :(

Commander issue here! Engine stops when props feathered, or at least when the prop lever is brought right back to idle. It's as if the mixture lever was leaned right out. Can that be right?

The World is divided into two groups. Those who say "Give me a link" and those that provide the link. WWG1WGA

Commander issue here! Engine stops when props feathered, or at least when the prop lever is brought right back to idle. It's as if the mixture lever was leaned right out. Can that be right?
It sure does. I hadn't noticed that. I wonder if it could be fixed in the .cfg file? Bummer.Cheers,Fritz

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.