No Levers will move [Resolved - Delete FSUIPC.ini]

[pascal.bidlingmaier]

It is so frustrating. Bought this plane for 70€ and I cant fly it. Non of the levers could be moved with my Saitek Throttle quadrant. I have done all the tutorials. Cant even move the Throttles with the mouse.

Any ideas?

[Slayer]

It sounds like your XMLTools did not install. Can you please uninstall your current version and use the latest installer from the link I gave you in the other thread? Make sure to run installer as admin.

Thanks

[jan.e.st]

Hi,

I just bought the 350i yesterday through ORBX, and I experiance the same. Futermore there are no power on the plane battery. I have to use the GPU to get some battery power. The trust/power levers are in fully closed position. Will not move with the Saitek trottle quadrant. I have managed to get the prop lever to move slightly by using the qudrant, but not the power levers. They are locked, and will not even move using the mouse pointer.

The plane is unfortunately grounded.

[jan.e.st]

Hi again,

I have downlowded from your link MV_KA350i_v1.1.34_20200724. My ORBX downloaded version is 20.05.24. But it is missing the XMLTools etc. Trying to install the newer version fail as i do not have the reg code (not available at ORBX site) . How do I proceede.?

Jan E. Stene
ENZV
Norway

[Slayer]

To use that build because you purchased from ORBX, you will have to locate your product key. It can be found in this file:
Lockheed Martin\Prepar3D v4\Milviz\MVKA350i.ini

You should uninstall the old version first but make sure you write down your key so you have it to install the latest version from this forum.

If you didnt write it down you will need to install it again from Orbx

[CajunRon]

Any resolution to this problem??

I've tried everything I know to do. I've run through the general trouble shooting guide in the SUPPORT section of the website. Insured everything was as it should be. I've tried every combination of FSUIPC throttle assignment. Tried removing the throttle assignment in FSUIPC and using the P3D axis assignment. Tried first loading the default aircraft and then changing to the Milviz KingAir. Tried a different throttle device (both are CH Products, their Throttle Quadrant and their Pro Thottle).

MVAMS does recognize the throttles and I can calibrate the different throttle positions with it (I'm assuming this "calibrates" the P3D axis assignments but not FSUIPC)

Even though the levers in the cockpit don't move, my throttle device does increase/decrease throttle (but something still didn't seem right).

I can move the on screen levers with my mouse and with the P3D keyboard mapping.

[Raptor]

I would recommend you install version 35 from the Support forums

[Slayer]

Any resolution to this problem??

I've tried everything I know to do. I've run through the general trouble shooting guide in the SUPPORT section of the website. Insured everything was as it should be. I've tried every combination of FSUIPC throttle assignment. Tried removing the throttle assignment in FSUIPC and using the P3D axis assignment. Tried first loading the default aircraft and then changing to the Milviz KingAir. Tried a different throttle device (both are CH Products, their Throttle Quadrant and their Pro Thottle).

MVAMS does recognize the throttles and I can calibrate the different throttle positions with it (I'm assuming this "calibrates" the P3D axis assignments but not FSUIPC)

Even though the levers in the cockpit don't move, my throttle device does increase/decrease throttle (but something still didn't seem right).

I can move the on screen levers with my mouse and with the P3D keyboard mapping.

Can you have a look at your dll.xml in notepad? ( use windows search to find it if you don't know where it resides)

It should have this:

<Launch.Addon>
<Name>XMLTools64</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>XMLTools64.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>

If that section is not present, then your XMLTools did not get installed. Need to make sure to run the installer as an admin to prevent any permissions issues( right click/run as admin)

[CajunRon]

My search found dll.xml in 9 different locations. They were not all the same. Four of those did have the code you mentioned. The one that showed the newest "Modified Date" and located in my AppData\Roaming\Lockheed Martin\Prepar3D V4\ directory did not have the code so I copied the code into it and ran P3D. I got the same results as before.

I've uninstalled and reinstalled three times. I am certain in install #2 and #3 that I ran the installer as admin. Also in the second and third install I specifically watched for an indication that XMLTools was installed. In both of these installations I got a message window that opened and specifically stated that XMLTools was installed successfully and XMLTools64.dll shows to be in the Prepar3D v4 root directory.

I have been able to get the throttle levers and the prop levers to move IF and ONLY IF I assign these axis in BOTH FSUIPC and P3D and I enable the controllers in P3D. Any other combination will not work. But the condition levers (the mixture levers) do not move no matter what I do. However they do their function. In other words even though they do not show to move, when I pull them all the way back with my controller, the engine does cut off.

[Slayer]

You should use either or with P3D and FSUIPC. If you have any set any calibrations in FSUIPC it will cause issues for some people. Have seen this problem before but it's hard to say exactly . Also have you tried just using directinput in P3D instead of the default RAW?

[CajunRon]

You should use either or with P3D and FSUIPC. If you have any set any calibrations in FSUIPC it will cause issues for some people. Have seen this problem before but it's hard to say exactly . Also have you tried just using directinput in P3D instead of the default RAW?

Steve, I'm not sure you understand.

If I assign the axis with P3D only there is no movement. The axis aren't even assigned in FSUIPC so there can't be any calibration conflict.
If I assign the axis with FSUIPC only, calibrate the axis with FSUIPC and disable the controllers in the P3D settings (which is what I normally do) there is no movement.
If I assign the axis with FSUIPC only but send them to P3D direct (the second option in axis assignment in FSUIPC) there is no movement.

ONLY if I assign the axis with both P3D and FSUIPC and enable the controllers in P3D settings do I get movement of the throttle and prop axis. I know this is very weird but it is what it is. (I actually stumbled across this by accident. I know this doesn't make any sense and it's not something I would have thought of try)

Yes I did try "directinput" in P3D.

In about two weeks I will get a new computer and a fresh install of P3D. I'll see if that fixes the problem (a very expensive solution )

[Slayer]

There is something weird with the saitek throttles as you are not the first one to have the issue. Maybe an old driver or something. Wondering if you try the Logitech drivers instead as they bought out saitek.

https://support.logi.com/hc/en-us/artic ... e-Quadrant

Make sure you get the 64 bit package...

[CajunRon]

I'm not using Logitech controllers. I'm using the CH Products Throttle Quadrant controller. I am not using the CH Products control manager to calibrate it. I am using Windows 10 Controller Settings to calibrate.

[Slayer]

I'm not using Logitech controllers. I'm using the CH Products Throttle Quadrant controller. I am not using the CH Products control manager to calibrate it. I am using Windows 10 Controller Settings to calibrate.

Ah...doh . The OP had a Saitek setup..my bad.

[CajunRon]

I didn't know if you saw my other post where I fixed the problem. I deleted the fsuipc.ini file and let FSUIPC create a new one. This solved the problem. It seems to be working as designed through P3D axis assignment.