KA350i Version 1.1 (SP1 - 1.1.29) [UPDATED MAY 24]

[ccmh15]

You said all other aircraft work fine? That really is weird then, because I can't imagine there's special code within the MV KA when it comes to nose wheel steering, I'd rather guess stock P3D stuff is used...

I have Saitek pedals as well, and they work perfectly fine.

Some things that come to my mind that you could check:
Other flight control axis (like aileron and elevator) work within the King Air?
Do the visual rudder pedals in the in the virtual cockpit move when you operate the Saitek pedals?
In the external view, does the rudder tab within the vertical stabilizer move?
How did you assign the rudder axis (P3D or FSUIPC)?
If via FSUIPC, did you check "Send to FS as normal axis"?
If via FSUIPC, which command did you use?
Do you apply any processing, calibration or a slope within FSUIPC?

As a workaround in the meantime, you could always taxi using differential brakes or differential thrust (if you have a throttle quadrant with seperate engine controls).

Cheers,
Chris

[rayharris51]

Hi Chris

Thanks for your reply.

Yes it’s strange. I’m not on my PC now so will have to look in the morning,

As far as I remember I have not set calibration to go via FSUIPC.

Also my pedals do move the rudders, just not the nosewheel. I’ve checked the control assignments and already have toe breaks assigned to the rudder pedals. They just do not steer the plane.

Will let you know what else I can find tomorrow.

Thanks

Ray

[bmw969]

Autopilot is on, but I do not see green lights next to the button

[Taguilo]

Autopilot is on, but I do not see green lights next to the button

There is no green light. All autopilot active modes are displayed in top of both PFD.

Tomas

[Taguilo]

Also my pedals do move the rudders, just not the nosewheel. I’ve checked the control assignments and already have toe breaks assigned to the rudder pedals. They just do not steer the plane.

Pedals won't move the nosewheel when aircraft is still. Nosewheel rotation is inertial, only happens with aircraft in motion.

Tomas

[zkalos]

Hi !
-When nav lights switch on in down/dusk/night conditions, it's illuminates the whole cockpit, like a dome light, and on external view the whole plane is glows as if illuminated by an external lamp post too in white light (new RealLight problem ?). Wing ice-lights works properly and the other external lights are good too. Uninstalled SP1 - 1.1.23, than installed the original release 1.0.1 version, which works good (when nav lights on, the cockpit and the external model staying dark and the lights works correctly outside, illuminates the ground only, not the whole plane is in white light). Deleted the Shader folder too several times. Please check this.
-Taxi with this plane very hard to me because it is difficult to keep it in a straight line, the turn is very delayed from my rudder input (because of default P3D ground physics ?) constant struggle with him for the straight taxi and very sensitive too. My other planes good, I have Saitek pedal and X-65F stick. They are calibrated, of course. XPlane11 good too.
-Performance better than previous versions to me, but it's stutters densely, sound tones changed/ripples when switch on things sometimes on a first time. Other planes working good, like PMDG, Flight1 B200, Majestic, A2A, Maddog, Realair etc.
I look forward to the promised performance enhancements (because my aged hardware with 4GB Vram, 8Gb Ram), and texture patch for a lower VRAM consumption, like my lovely PC-6, which was only flyable to me after the "lite texture" patch. I love this bird, but it's parking again in my virtual hangar again. But it is changing promisingly after all. I hope You not ending repair and develop this fine product,too much work has been put into it, and don’t forget about customers with weaker hardware and less money, who want to use this fine, realistic turboprop in P3Dv4.5. There are so few of them. We know why.
-It would be nice if we could adjust the brightness of the radar and terrain's gain on the screens, it's too bright.
-And one small note, MVAMS not detecting my X-65F throttle quadrant's one slider/pot, which I use for my all other planes as a mixture. I configured this in Fsuipc as a "Send to FS as normal axis" and didn't apply any processing, calibration or a slope for it. This happen after I changed in the registry 2 weeks ago my Saitek stick axis allocation with a regedit/program because of my Falcon BMS sim, that for me the ministick/mouse cursor works instead as two axis and not the stick default twisting rudder, which useless to me after all (because of the DirectX axis number limit). This patch (X65F regfix_v2.1) disabled my rudder axis on the stick, and enabled my mouse cursor stick in my throttle quadrant as an new XY axis. P3D detecting it and working good with other planes, and I can use my slider pots as I like (mixture). This potentiometer is working with my KA350 too, but I can't calibrate in MVAMS now. Not a huge problem. Thanks, and sorry for my bad English and long post. I wrote here for the first time.
Good health to all !

[Matthieu-C]

Hello!
I confirm the nav light switch issue.
I don't see VRAM improvment from 1.1.23 to 1.1.24.
(But I enjoy this aircraft!)

[bmw969]

Why is blurry font so cheap? The glasses did not help.
Give me back sharp vision please !!! This is 4K, not VR

[Kdub]

Should I stay with 1.1.23?

Kdub

[bmw969]

I had to go back to the previous build.
I compared the blurry font of the last two builds.
If you want to make textures easier for weak graphics cards, then please make it possible to select textures in the settings. I have no problems with video memory on 2080ti

[c.jurek]

hello,
Same for me, textures are too much blurred, even with the sharpen option activated in Nvidia drivers.
Revert back to to 1.1.23.
Anyway thanks for your hard work !

Georges

[Philippe Mendes]

Same here. If you can put an option for the textures would be great !

Thanks for your hard work !

[doodlebug]

thanks for the heads up - we are investigating

[doodlebug]

is this with internal light on?

[c.jurek]

"is this with internal light on?"

Yes, it accentuates the issue. It looks like the characters are duplicated white and blue, the blue being shifted a few pixels above.

Best regards

Georges