kosmosima on gunfighter base.

[dutchy2000]

The top right had/stick has a weird issue. When I have it in stick mode (little red light is on) both axis work fine, except when I move to the top right. Then one of the two axis only goes to 50% instead of 100/100. So depending on which angle I aproach the edge, either RotX or RotY will not get to 100%. When I move it around the edge, best I can get is both at 75%, but not 100%. If I try any of the other edges they all get to 100%. I have tried recalibrating several times with the same result. Is it supposed to be like that? In both pictures I have the joystick in the top right position. It also feels like there is a little notch in the top right corner, but the top left corner has the same notch. The bottom doesn't feel like it has the same notches.

[Ron61]

Better show a screenshot of the Profile-Axes tab. There will be more information. Need a full window, not a fragment.

[hon0]

I think the problem is the shape of the ministick button. It is too "fat" to go into upper corner.

He advise to remove this part to solve the issue.

[Ron61]

This is where calibration exists. It is she who fixes the real movement of the axis.
If you remove your hat, it turns out that the move is a bit more. But this does not stop working with a hat in full range.

[hon0]

I don't think calibration can solve that. As I understand the problem (I don't have the SCG myself) is that the ministick can not, physically, reach upper corners, due to the round shape around the top part of the ministick or the ministick stem being too wide.

Here is my poor atempt at illustrating the problem



Edit : Note that I have the same problem with my MCG PRO. The shape isn't perfectly square and if I want to be able to reach 100% on both axes at the same time then I need to add high deadzone. I need about 13% high dz to solve that on my MCG PRO.

[Ron61]

Okay, I'll try again.
During calibration, you specify the end (extreme) points of the range for the controller.
And then he “stretches” them from 0 to 65535.
For example, do not move the X axis (roll) or Y (pitch) of the GF from lock to lock during calibration, but do it only halfway.
And after that, your axes will reach 0 and 65535 exactly at the boundaries that you set during calibration. A.
If you remove the cap from the left stick of the MCG, you will see that its maximum stroke is much greater than with the cap.
What does not stop her from working in the whole range.

[dutchy2000]

Better show a screenshot of the Profile-Axes tab. There will be more information. Need a full window, not a fragment.

I am attaching the profile, 3 and 4 are the axes I am talking about.

I don't think calibration can solve that. As I understand the problem (I don't have the SCG myself) is that the ministick can not, physically, reach upper corners, due to the round shape around the top part of the ministick or the ministick stem being too wide.

Here is my poor atempt at illustrating the problem



Edit : Note that I have the same problem with my MCG PRO. The shape isn't perfectly square and if I want to be able to reach 100% on both axes at the same time then I need to add high deadzone. I need about 13% high dz to solve that on my MCG PRO.

Exactly this, but the weird thing is the top left does get to 100%/100% but the top right doesn't.

[Ron61]

Show screenshot Profile-Axes-Logical & Physical.

[dutchy2000]

Show screenshot Profile-Axes-Logical & Physical.

[dutchy2000]

That not what you are looking for?

[Ron61]

I have different hats, they are in the photo. That with one, that with the other - the same result. Both in different angles reach either 0 or 65535. Depending on the angle, of course.
True, I have extreme software - both firmware and the configurator. Try changing too. Located here.

[dtdionne]

Wth??? How did this get through quality control? Utterly shocking.

My lower left stick has never worked properly and it ain’t something any calibration of ANY KIND could EVER fix. The values are never the same. Sometimes it returns to 0, others it returns to 0 WAY EARLY, then goes to full at 0, others it never goes full nor returns 0, others it goes full but returns half. It’s pathetic

[Victorus]

First of all look here http://forum.vkb-sim.pro/viewtopic.php?f=25&t=2762.