FSUIPC and Throttles being backwards.

[admin9]

I have my throttles setup through FSUIPC with the new bravo quadrant. They are moving etc the only problem is they are all in the wrong position in the sim. Idle on the bravo = full power in the sim & full power on the bravo = idle in the sim.

I have them setup as Axis Throttle 1 Set and "Send to FS as normal axis) ticked.

Is there any solution for this please?

[Slayer]

Have you also configured your throttles in MVAMS?

See these posts:

viewtopic.php?f=105&t=11513
viewtopic.php?f=105&t=12284

[admin9]

Have you also configured your throttles in MVAMS?

See these posts:

viewtopic.php?f=105&t=11513
viewtopic.php?f=105&t=12284

Hi Slayer,

Spent all day yesterday doing the following and going through the above topics already with no success. This is what I am finding:

In other aircrafts such as the PC-12 for example, the throttles are in reverse until you "calibrate joystick section" in FSUIPC and reverse the values and then they work correctly.

If this is done in KA350i (they note not to do it) it does not make any difference.
Have clicked the reverse axis and calibrated the throttles etc in the MVAMS with no success.
Have tried it in MVAMS and not reversed the axis (in case FSUIPC and MVAMS were working against each other) and still no luck.
Was installed through ORBX (still no xml tools included by the way). So removed that one downloaded latest in forum to ensure XMLtools was installed and still same issue.
Removed the ini and did it all again and same outcome.

The only option is to have the throttles setup in P3D and reverse axis ticked which isn't ideal as you then need to go into FSUIPC anyway to set up the reverse thrust (which does work okay and simulates the reverse thrust position in the sim).

I believe the problem lies within the bravo and the KA350i setup. Due to the fact that the bravo is reversed in its wiring the KA350i cant change to fix it. Like I have stated above, it does replicate this reverse throttle issue in other planes but as soon as you calibrate it in REV in FSUIPC it fixes it.

[Ephedrin]

(currently) you can't assign the KingAir levers with the Bravo quadrant using FSUIPC. I've played around with it for hours, there is simply no way, the quadrant works the wrong direction and you can't use the FSUIPC calibration. MVAMS would require a "reverse" setting. For now all that works is to use the P3D assignments and reverse it there. I created a KingAir profil which I can import when I fly the KA and an empty profile for all other planes that don't have a problem with the FSUIPC calib

[admin9]

(currently) you can't assign the KingAir levers with the Bravo quadrant using FSUIPC. I've played around with it for hours, there is simply no way, the quadrant works the wrong direction and you can't use the FSUIPC calibration. MVAMS would require a "reverse" setting. For now all that works is to use the P3D assignments and reverse it there. I created a KingAir profil which I can import when I fly the KA and an empty profile for all other planes that don't have a problem with the FSUIPC calib

Thanks. Glad it's not just me. The weird thing is, is the MVAMS does actually have a reverse setting (invert axis) it just doesn't appear to work with the bravo.

[Ephedrin]

I gave up on MVAMS anyway, read my lever positions from FSUIPC entered them into the ini manually and then set it read-only. I didn't get along with the calibration tool they came up with

[admin9]

I gave up on MVAMS anyway, read my lever positions from FSUIPC entered them into the ini manually and then set it read-only. I didn't get along with the calibration tool they came up with

I hear you so I wonder whom will fix this error then Milviz or Honeycomb?

[Ephedrin]

[Slayer]

I don't want to sound gruff here...It is literally impossible for us to support every hardware combination out there. Especially one where it works in reverse of what every other manufacturer does and then throw FSUIPC into the mix. LM realized this a long time ago that's why there are profiles.

Sorry I don't have a better answer for you but there is just something weird about these that are causing issues.

[admin9]

I don't want to sound gruff here...It is literally impossible for us to support every hardware combination out there. Especially one where it works in reverse of what every other manufacturer does and then throw FSUIPC into the mix. LM realized this a long time ago that's why there are profiles.

Sorry I don't have a better answer for you but there is just something weird about these that are causing issues.

Thing is that the bravo will become the "norm" very soon. It is the only plane were the reverse (reversing the values not reverse thrust) in FSUIPC (and MVAMS) doesnt work. I have tested it now in over 8 planes and this is the only one that it now doesn't work. No doubts there will be more complaints when people get their hands on the bravo.

[Taguilo]

For now all that works is to use the P3D assignments and reverse it there. I created a KingAir profil which I can import when I fly the KA and an empty profile for all other planes that don't have a problem with the FSUIPC calib

Actually the default P3D configuration, using the Reverse checkbox is the one that we MUST support. The KA contains special custom config for the engine levers, that we must ensure are accepted by P3D as default in almost all situations. If they work as well with FSUIPC, great; if they don't then we cant' do anything. As harsh as I might sound (I am a FSUIPC user myself), this is a third party utility, not a component of P3D core. Despite being widely used by the community, we can't provide full FSUIPC support for those controllers that are not directly supported by it, which seems to be the case here.


Tomas

[tcarter.67]

Thats a real shame that Milvis are not prepared to work this out with users of this hardware....very disappointing indeed.

[kevin_firth]

Thats a real shame that Milvis are not prepared to work this out with users of this hardware....very disappointing indeed.

Have you asked Honeycomb for support with their product, since the problem appears to lie there?

[Ephedrin]

For now all that works is to use the P3D assignments and reverse it there. I created a KingAir profil which I can import when I fly the KA and an empty profile for all other planes that don't have a problem with the FSUIPC calib

Actually the default P3D configuration, using the Reverse checkbox is the one that we MUST support. The KA contains special custom config for the engine levers, that we must ensure are accepted by P3D as default in almost all situations. If they work as well with FSUIPC, great; if they don't then we cant' do anything. As harsh as I might sound (I am a FSUIPC user myself), this is a third party utility, not a component of P3D core. Despite being widely used by the community, we can't provide full FSUIPC support for those controllers that are not directly supported by it, which seems to be the case here.


Tomas

Don't mistake my comment as a complaint please. Milviz is probably the only developer for any P3D version who nailed a turbine engine so phantastically, I can totally ignore this "downside". The Kingair is such an amazing simulation, I don't care if I have to use the P3D assignments for it. It works perfectly this way, cumbersome a bit, but I don't care, I have so many different setups I have to change for different aircraft, loadiing this profile is just another step.

What I meant above regarding MVAMS is another topic, I just don't get along with it so I made my work-around. You can't satisfy everyone with everything, I don't blame you.

[Slayer]

No offence taken. Our devs try to support as much hardware as possible but is next to impossible to support everything.

Example: FFB yokes that only very few people own. In that case I think the MFR actually patched it(or said they were going to)

As Tomas said though it must work within basic P3D controls first before anything else as that is were most people tend to setup their controls.