KA350i Version 1.0.0

[Heronjr]

Hi Heron, yes I have done this for each version and it is a bit of a drag having to do it each time but it needs to be done. I should add that the Propeller and Condition levers work just fine (I have two Saitek Throttle Quadrants). This includes the left Propeller Lever which is on the same TQ as the two Power Levers.

I am away for work for the next couple of days but will follow this with interest

I also have two throttle quadrants and, as the propellers and condition levers work well, the throttles are a little bit trickier to deal. In fact, i use the left quadrant only for the throttles, because only one stick works well and the others are extremely unstable. So i use a triple union on left quadrant and assign the good stick for both throttles. The problem in my case is a quadrant with bad contacts and simply impossible to calibrate. Last month i had to change my pedals for the same motive. I’ve heard that Saitek throttle quadrants have issues.

[Pierdail]

hi,
Congratulations
Happy Chrismas and wonderful 2020 for the all team
Pierre

[mongo501]

Congrats from Southern California. I signed up a longtime ago for the Beech 350, and I know that this was a knotty project for Milviz. I've loved your stuff from the beginning (which is why I own just about every plane), and wish you well for 2020 and beyond. I hope you guys will take a well earned break. Any current problems can surely wait until after the holidays. Mike Gutierrez, North Hollywood, California.

[KenG]

I used the Saitek Yoke, Rudder, and dual Saitek throttle quadrants so I have separate left and right power levers, left and right propellers, and left and right condition levers.

There is something about this aircraft where I had to delete all my global FSUIPC profiles and just us aircraft specific versions. If I tried to use global it caused problems.

[Rossco]

I always use aircraft specific profiles however they don’t work for me with this aircraft.

[KenG]

Try clearing profiles for the B350i as well. See if that helps. I remember having issues, to begin with, and had to set up P3D for this airplane to read raw axis from P3D.

[rayharris51]

Hi Just to let you know I've tried the same flight as previously CYCDCYLW.

Long pause (c 4mins) when I selected TERR on the ND, then 15 mins after takeoff CTD after a brief freeze without warning.

The plane is beautiful but unusable for me. I realise this might be something related to my set-up but this does not happen with any other plane.

I understand the gargantuan effort you put into this plane and that's very much appreciated by all of us, but at the same time my reporting seems to have been a bit of a waste of my time as you have never answered or addressed my problems. If you do decide try to help that would be great, otherwise I will not bother you again - this is my last post.

Have a very good festive break and a I'm sure a badly needed rest

Ray

[KenG]

I know you don't want to limit how you use the airplane, but for now, I recommend only using TAWS with a range of less than 50nm. Before selecting range greater than 50nm turn off terrain.

[N4GIX]

The yokes' chrono light is now always on. It was OK on RC1, Not a problem, guys.

The chrono's backlighting will only come on if the master battery is ON, or engine(s) are running and either left or right generators are ON...

...otherwise the clock's backlighting is OFF.

[dbw]

Something that may be of interest...
Before the last RC I had an axis mapped to control reverse. It worked well so as to have control from beta to max reverse.
It is now none functional and I've checked calibration. it added to realism very nicely. Now reverse is accessible with F2 only.
Also. brakes are now very weak....at least for me.
Dave

[Heronjr]

The yokes' chrono light is now always on. It was OK on RC1, Not a problem, guys.

The chrono's backlighting will only come on if the master battery is ON, or engine(s) are running and either left or right generators are ON...

...otherwise the clock's backlighting is OFF.

Bill,
When I said "always on" I meant back-lightning ON with battery OFF and ON. Contrary to last version RC1, when the behavior was as you say, i.e., correct as with light ON = bat ON and light OFF = bat OFF.

As I said, this is not a problem for me, but I will repeat a comment I made some versions ago: It is kind of strange the way you manage software releasing as there are some features which are working well in version A.1 and when it comes to version A.2 the same feature stops working. It gives me the notion that you have not just one developing unity, but more than one in different degrees of development. I may be mistaken, but I work with software factoring and I've already seen this happens.

[Taguilo]

Hi Heron,
Which “battery” switch are you talking about?
The one it is next to the gen switches or the One that powers BATT BUS?

Thanks

Tomas

[N4GIX]

Bill,
When I said "always on" I meant back-lightning ON with battery OFF and ON. Contrary to last version RC1, when the behavior was as you say, i.e., correct as with light ON = bat ON and light OFF = bat OFF.

As Tomas stated, it is the three switches under the 'crash bar' to which I refer. Each of the two clocks has the same logic that controls the backlighting. If either engine's generator is ON and supplying electrical power, the lights remain on:

Code: Select all

    <Visible>
      (L:B350i_BatterySwitch,bool)
      (L:B350i_L_GenActive, enum) or
      (L:B350i_R_GenActive, enum) or
    </Visible>
    

Click on the 'crash bar' cover to flip all three switches OFF and note that the clock's backlighting is extinguished.

[Chuck Jodry]

RE Throttles snapping back to idle , there are friction knobs on the quad , keep them below 40 % , I have read that these will cause an effect such as described it they are set high.

Best CJ

[Heronjr]

Hi Heron,
Which “battery” switch are you talking about?
The one it is next to the gen switches or the One that powers BATT BUS?

Thanks

Tomas

Tomas, you are right. Now the BATT BUS makes the difference. Thanks.