VKB-SIM

Hi

i will use the X and Y axis from my NXT THQ Throttle as twin engine plane throttle.
to bad the X and Y axis are not synchron (see Pictures)

what i can do to make the axis synchron.

hi VKB SIM Team

i try all, Bootloader, calibration back to default nothing help the Y axis is faster than the X or Z axis.

So is the Axis broken or is this a foult from the controller



to other gnx thq throttle quadrant users

please can you test it?
use the doppel axis lever heads and test it "the Axis are synchron" in the VKB Device Config

If you physically link 2 throttles there should be only 1 of the 2 axes assigned in game, not both.

I don't want to put them together as one axis, i will use the axis X and axis Y as throttle for two mot planes.
so the axis X and axis Y must work synchron.
for now the axis Y are faster in game the engine 2get more power.

i hope you unterstand what i mean

I'll chime in, since I have the same problem: no single axis is in sync with any of the other two, even if I lock them together (using the supplied linkage). Both axes coincide at 0% and 100%. However, if I set one axis to 50%, the other shows 45% (give or take), instead of the expected 50%. This was checking directly in VKB JoyTester. If I put all axes at 32767, they should be lined up physically. However, they aren't.

I'm also seeing an interesting phenomenon in my THQ: it feels as if there are dead zones in X (the biggest) and Y axis (a bit smaller). Z axis reacts almost immediately. Also, maybe because of this, I see that the biggest offset is between the X and Y axis; the gap between Y and Z is lower (and also my annoyance). Thus, I've set my engine 1 and 2 controls for axis Y and Z for all my flight sims.

I understand each axis has its own potentiometer, and calibration may be different for each one. But is it there a way to calibrate the signals so that, for the same position, the readings in all 3 axis are the same along the whole throttle travel?

EDIT: I forgot to say. My THQ is equipped with an USB controller.

thx for your replay, so my THQ is not broken it is a Controller problem.
my THQ are on USB too.

must be a software error, i hope the VKB SIM Team read our post and look for the problem.

Veteran66, I see you use MSFS. Do you have FSUIPC7 installed? If so, try to apply the procedure in page 40 of the User Guide. I know this isn't the solution I'd like to have, but this is all we've got.

I had to apply this in FSUIPC6 for all my planes in P3D (but the Aerosoft buses*). I did also in FSUIPC7, except for the PMDG DC-6 (which somehow inherited my default settings, despite having a DC-6-dedicated profile) and the FBW Airbus (which I calibrated directly in the EFB). For all this, I linked my Y and Z levers together (with only the white connector between the throttles, no screws at all) and proceeded with the calibration. Now it feels better, but I would have liked the synchronization to be done at driver level instead.

* There's something in the Aerosoft Airbus code that allows me to have the throttles synced, at least for each detent. For the linear range, as expected, they have nothing. I fear that they will be lazy and port that setup to MSFS, complicating us all...

Veteran66 wrote:...

Please stop emphasizing your posts for no reason.

@fallout19
would be nice if you would write something for this synchon problem

Show tab Profile-Axes (logical and physical).

here my settings

Check out this thread.

If I understood correctly, I should set the THQ axis as in this post:

viewtopic.php?f=25&t=6402&start=15#p53859

Is this correct?

In each case, you need to look at the settings and data after calibration. Naturally, the settings for the axes and dead zones should be the same.

This is what I've got:



I had to invert the axis because FSX, P3D (both V4 and V5) and MSFS are reading them backwards, which give me control reversion issues with some aircraft that can't be corrected from within the sim. As you can see, all the parameters are the same for all 3 axis, except for High and Low gain coefficients. However, this is not enough for compensating the issue as I managed to do so in FSUIPC.