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

[FinnJacobsen]

And here we go again... seriously, I'm running out of patience.

The engine control levers have been working until this SP1. The throttles don't go into idle and beta AGAIN, the Prop1 lever snaps into feather after every movement AGAIN and I really don't have the time and will to tweak, search for help or fix things every time I try to start the Kingair or installed an update..

PLEASE!

WHAT for God's sake do I have to adjust NOW or what do I have to use to assign NOW to use this airplane???

I use one lever for every control, so six levers in total. They are assigned via FSUIPC's "send to FS as normal axis" as before and the detents are set through MVAMS. No FSUIPC calibration is applied. The axis.cfg is not read only, the values set by MVAMS are saved. Everything is set as it was with the 1.0.6 version, it just doesn't work. And I'm really really tired to search through dozents of forum pages..

Thanks for any help..
Marc

Edit: 4.5HF2.

Using FSUIPC "Send to FS as normal axis" -> use "AXIS_THROTTLE1_SET", "AXIS_THROTTLE2_SET", "AXIS_PROPELLER1_SET", "AXIS_PROPELLER2_SET", "XIS_MIXTURE1_SET & "XIS_MIXTURE2_SET"

No calibration should be applied.

Also in MWAMS ensure that under "Controls" -> Enable Hardware Mapping" is ticked (I could not get my Axis' to work yesterday, until I found it was unticked).
Then setup each axis under "Axis Calibration".
Probably not necessary, but for each Axis I configure I click "Save" and goes back into "Axix calibration" to setup the next axis.

Also ensure that the axi´s aren´t assigend in P3D controls, sometimes they get automatiaclly assigend again, odten if a controller has been unplugged and then replugged or other changes has been done to P3D.

[Ephedrin]

Using FSUIPC "Send to FS as normal axis" -> use "AXIS_THROTTLE1_SET", "AXIS_THROTTLE2_SET", "AXIS_PROPELLER1_SET", "AXIS_PROPELLER2_SET", "XIS_MIXTURE1_SET & "XIS_MIXTURE2_SET"

No calibration should be applied.

Also in MWAMS ensure that under "Controls" -> Enable Hardware Mapping" is ticked (I could not get my Axis' to work yesterday, until I found it was unticked).
Then setup each axis under "Axis Calibration".
Probably not necessary, but for each Axis I configure I click "Save" and goes back into "Axix calibration" to setup the next axis.

Also ensure that the axi´s aren´t assigend in P3D controls, sometimes they get automatiaclly assigend again, odten if a controller has been unplugged and then replugged or other changes has been done to P3D.

a thousand thanks, Finn!

Hardware mapping did it for the throttles.

No I just have to figure out that Prop1 axis warp.. I had it before and maybe I'll find the solution again.. sigh

anyway, thanks!

[FinnJacobsen]

a thousand thanks, Finn!

Hardware mapping did it for the throttles.

No I just have to figure out that Prop1 axis warp.. I had it before and maybe I'll find the solution again.. sigh

anyway, thanks!

I´m not sure what Throttlequadrant You are using.
I use the CH-Products Throttlequadrant with six levers, each lever has a detend appr. 10-15% from fully back.

The levers has some slack within the detends, so my setup for each type of control is as follows:

• Power lever 1&2:
  • Max reverse set with levers appr. 1mm forward of fully back.
  • Beta set appr. 1mm back of the detend, just where the lever becomes firm / free of slack.
  • Idle set appr. 1 mm forward of the detend, just where the lever becomes firm / free of slack.
  Max power set appr. 1mm back of full forward.

• Propeller lever 1&2:
  • Feather set with levers appr. 2mm forward of fully back.
  • Minimum set with levers within the detend (range where slack is present).
  • Maximum set with levers 1mm back of fully forward.

• Condition lever 1&2:
  • Cut off set with levers appr. 2mm forward of fully back.
  • Low idle set with levers appr. 1mm back of the detend, just where the lever becomes firm / free of slack.
  • High idle set with levers appr. 75% forward (in MWAMS set halfway between Low idle and High idle "SET" boxes).

With these settings I´m sure that I can feel when going into reverse range, Beta range is within the detend range (slack range), and Idle-Max is surely felt to be forward of the detend within the firm /free of slack range.
During taxi, I´m well aware when I´m within Beta range, and it´s very easy to control taxi speed.

For the propeller levers, Feather is only achieved with the levers pulled fully back, and I have the full range from the detend to full forward for prop rpm control.

For the condition levers, Cut off is only achieved with the levers pulled fully back, Low idle is still held when the levers are rested fully back in the detend, and High idle is achieved as soon as the lever is 75% forward.

I have a good feel to where I have the power levers, and no lever is moved into postions not intended, like Cut-off or Feather.

[Ephedrin]

I have the Saitek Throttle quadrant twice with 3 levers each. They are pretty bad quality actually but I just wait for the Honeycomb Beta controllers to arrive. Anyway, the range is fine now and I found the solution of the warping throttle to be the 16384/-16384 resolution. MVAMS saves 16383 and I corrected it in the .cfg. I'm flying now and I really appreaciate the effort Milviz took with this service pack. Unfortunately their MVAMS approach is really not user friendly but that's what we have to deal with.. So I fought my way through it and I hope I can enjoy the Kingair to the fullest now ;D

[Kdub]

I had trouble with my Saitek, (not really unexpected), in that one throttle was a little jumpy and degraded my left engine. I'm not sure exactly what it did. My experience is that the CH is more precise, and Finn's settings work real well. So I second the idea of thanking Finn!


Kdub

[FinnJacobsen]

1.1.8 Reallight Beta not working.

Sorry guys, but for me the new Reallight beta makes it inop.

VRAM usage has dropped to 2650, but no light in the cockpit.

At least it is butter smooth now.

It doesn´t seem that the 1.1.8 Reallight installer, installs the Reallight.dll and Trueglass.dll into the \Gauges folder of P3D.

[bmw969]

We have long wanted to test every new version. Now it is provided. I am satisfied.
The developer said that sometimes in the next version something fails. This is normal.
But we are participating in testing! Still to see the installer for v5

[Thorsten42]

1.1.8 Reallight Beta not working.

Sorry guys, but for me the new Reallight beta makes it inop.

VRAM usage has dropped to 2650, but no light in the cockpit.

At least it is butter smooth now.

It doesn´t seem that the 1.1.8 Reallight installer, installs the Reallight.dll and Trueglass.dll into the \Gauges folder of P3D.

Finn, just installed 1.1.8 and working fine with Reallight Beta. Possible that you had sim running in back and prevented from updating blocked files? Otherwise I still see a much higher mem footprint then in any other high end addon. Will do a testflight now to see if ctds are gone...

Cheers
T.

[Thorsten42]

Still CTD after an hour of flight over big blue nothing... Still nearly 6gb vram blocked where other high quality addons take only around 2,5... Sorry to say but it will go to hangar again

Cheers
T.

[FinnJacobsen]

1.1.8 Reallight Beta not working.

Sorry guys, but for me the new Reallight beta makes it inop.

VRAM usage has dropped to 2650, but no light in the cockpit.

At least it is butter smooth now.

It doesn´t seem that the 1.1.8 Reallight installer, installs the Reallight.dll and Trueglass.dll into the \Gauges folder of P3D.

Finn, just installed 1.1.8 and working fine with Reallight Beta. Possible that you had sim running in back and prevented from updating blocked files? Otherwise I still see a much higher mem footprint then in any other high end addon. Will do a testflight now to see if ctds are gone...

Cheers
T.

I re-installed, and now Reallight.dll and Trueglass.dll are present in the \Gauges folder, but there is no light in the aircraft.
It also renders the MilvizPC-6 Reallight inop.

Furthermore all annumciator lights become very dim, and the lower ones, when turned on becomes black.
I have cleard my shader cache too.


**** EDIT ****
I have now tried to install 1.1.7 and then saved the Reallight.dll (version 1.1.0.0) from the \Gauges folder.
Then I uninstalled 1.1.7 (and removed any trace of it in various folders) and installed 1.1.8 with the Beat Reallight.dd (version 1.2.0.0).
With Beta Reallight.dll v.1.2.0.0 - Reallight does NOT work. Simply copying the original Reallight.dll v.1.1.0.0 and reloading the KA350i, Reallight works again.

Note that I use P3D V4.5 HF3 on a Win7 64bit system with a GTX960

[Thorsten42]

Hmmm... don't know what to say... I see the Reallight.dll updated in the gauges folder with version info 1.2.0.0 and change date of 23.4. after installing 1.1.8. Both KA and PC6 lighting working fine for me with the beta version.

But even with the 1.8.1 the KA takes 5.8GB VRAM (Trueglass and Reallight disabled 3.7 GB VRAM)
Default plane none addon airport 3.1GB vram usage. Other addons in comparison tested at same spot:
tfdi717 4.6GB
maddog 3.9GB
qotsiiv3 3.3GB
mjdash8 3.2GB

and now the interesting:
PC6 nearly the same with 5.7GB
and the older DHC3T still 4.8GB

For me clearly something hiding in Reallight/Trueglass.
But the PC6 for example doesn't CTD for me in contrast to the KA.

Perhaps some HF3 relation here, too? I'm still on HF2, latest W10 and a GTX1060.
Cheers
T.

[Turbofandude]

There was a brief issue with the RealLight beta - if you're experiencing issues, please reinstall it via the RealLight_Installer.exe located in the Redistributables folder in the SimObjects\Airplanes\MV_King_Air_350i folder.

The VRAM should have dropped by ~1GB for the KA. Others may have dropped, as well. The reduced VRAM won't be a magic pill for performance, but it should help, at least. If it's not working at all, that's odd. Anyone who it's not working for completely please PM me and we'll setup a time for me to take a direct look (if you're comfortable with that).

[FinnJacobsen]

There was a brief issue with the RealLight beta - if you're experiencing issues, please reinstall it via the RealLight_Installer.exe located in the Redistributables folder in the SimObjects\Airplanes\MV_King_Air_350i folder.

The VRAM should have dropped by ~1GB for the KA. Others may have dropped, as well. The reduced VRAM won't be a magic pill for performance, but it should help, at least. If it's not working at all, that's odd. Anyone who it's not working for completely please PM me and we'll setup a time for me to take a direct look (if you're comfortable with that).

I ran the Reallight installer (Version 1.2.0.0), but that simply installed the old Reallight.dll (v.1.1.0.0) with the same VRAM footprint as before - so no improvement here.

[paul.ziegler96]

When I insert ILS25 in EDDS via STG VOR everything is fine until the aircraft should turn right at x DME when flying with the AP. Instead of turning right on the correct course, it initiates a left turn and gets lost... Can you have a look at this navigation issue?

Thanks,
Paul

[Turbofandude]

There was a brief issue with the RealLight beta - if you're experiencing issues, please reinstall it via the RealLight_Installer.exe located in the Redistributables folder in the SimObjects\Airplanes\MV_King_Air_350i folder.

The VRAM should have dropped by ~1GB for the KA. Others may have dropped, as well. The reduced VRAM won't be a magic pill for performance, but it should help, at least. If it's not working at all, that's odd. Anyone who it's not working for completely please PM me and we'll setup a time for me to take a direct look (if you're comfortable with that).

I ran the Reallight installer (Version 1.2.0.0), but that simply installed the old Reallight.dll (v.1.1.0.0) with the same VRAM footprint as before - so no improvement here.

Yup, that makes sense. I apologize - you need to run it with the /beta switch (you can do this by creating a shortcut and adding it as an argument or by starting it from the command line as "RealLight_Installer.exe /beta".