Jump to content

Recommended Posts

Posted

I'm using an X-52 Pro, tried to assign each and every axes (including pitch/roll) to the K-14 range, and they all give me the same problem:

the range "jumps" up and down whenever I move the control, as if the axis is spiking, but it's not a joystick problem, because those same axes work just fine for propeller pitch, trims or wing span. Anyone else having this problem?

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

Posted (edited)

Sorry to say this, but it looks like it is a problem of your joystick.

 

Let me explain ,

here is a un-educated guess what's going on.

So please read this posting for getting further information:

Originally Posted by leafer viewpost.gif

Have you look at the trim wheels when the keys are pressed? They slowly turned as if done manually.

Do they also move slowly when you yank your, let's say, rotary axis assigned to trim?

This is normal and well done, this just simulates the real behaviour/turn-ratio and resistance.

- the same happens if you do it with a axis.

 

Just imagine that these wheels move gears and pulleys and finally the control-surface.. - and this takes some time.

 

ED did this with all flight critical axis inputs In DCS including Warthog/BlackShark.

e.g. You also can't move the rudders in the Ka-50 instantly from one side to another - even if your joystick/rudder paddles are able to do it much quicker. -this simulates the resistance/respond time of the hydraulics.

 

This is one of the reason I will build a trim-wheel box that behaves the same like the simulated one- so I don't have to check visually and I just know that one turn will correspondent 10° .

 

>>> Trim Wheels - turn/deflection ratio ?

Similar is done to the propeller pitch, trims or wing span...

 

But probably not to the K-14 Range axis.

So it spikes because your axis input spikes.

 

We only can hope that they also add a small delay/smoothing to the K-14 Range axis to prevent so the little spiking of your joystick becomes negligible.

 

 

But to be absolute sure about this:

Use DXTweak2 to examine your joystick axis -(don't do it with the on-board windows and/or SST tools - they are way to un-precise to show the jitter properly.

 

DXTweak and other tools can be found here:

subscribed.gif corrupt calibration? crazy joystick response? Use this tools to Fix it:

Edited by PeterP

Posted

I get this too in all axis. Its first a problem with logitech on my end. But it isn't noticeable in any other sim I play. So, second, I'd say its a problem with how DCS manages DX input. I don't care about the K-14 but I am concerned about the throttle which behaves the same.

Posted

Thanks for your reply. While I understand what you are saying, and I agree with it, I am also happy (and quite amazed) to say that according to DXTweak, I have a perfect joystick! No spikes at all on the various axes, especially the rotaries appear to be rock solid.

Anyways, even if there were minor spikes, I guess ED should put some sort of tolerance unless they want us to buy military grade joysticks...

Windows 10 - Intel i7 7700K 4.2 Ghz (no OC) - Asus Strix GTX 1080 8Gb - 16GB DDR4 (3000 MHz) - SSD 500GB + WD Black FZEX 1TB 6Gb/s

Posted

I have to agree with OP here, on at least the X52. My joystick and throttle are ok but the other rotary axis are spiking. I only realised when I assigned a rotary to the zoom view...oh yeah...stuff to make your eyeballs explode it jumps around like im driving over a cattlegrid. This is the same in the options > axis assignment page, the output jitters.

 

Sadly though, in Windows device management the inputs are all rock steady with no spikes shown.

 

I haven't tested it much because I can only use one of the rotarys on the X52, the other two remain un-assigned.

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Posted

Oh i should mention that it jitters when you dont move it, which i believe is absolutely fundamental to disprove there is any problem with the device hardware. IE Put rotary at 50%, leave it, jitters, put it any value, except 1% and 100% it jitters. at max and min, its stable. This does not change with the saturation or curve.

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Posted (edited)
Oh i should mention that it jitters when you dont move it, which i believe is absolutely fundamental to disprove there is any problem with the device hardware.

 

Before this thread turns into a "who is right/wrong" debate....

 

I never denied that this isn't a issue, but did you really had a look at it with DX-Tweak?

 

...No? - so how can you talk of "absolutely fundamental to disprove" ?!

 

But to be absolute sure about this:

Use DXTweak2 to examine your joystick axis -don't do it with the on-board windows and/or SST tools - they are way to un-precise to show the jitter properly.

I suffer myself from this effect - my workaround is to clone the jitter axis with PPJoy to a virtual controller and add a 200millisecond refresh-rate delay for the axis. Edited by PeterP

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...