So what have you guys got dialled in for now as a work-around?

 

6 minutes ago, Will Fly For Cheese said:

So what have you guys got dialled in for now as a work-around?

Well, you could tinker with the elasticity parameters that Rob mentioned. Unfortunately lowering the sens got even worse with that weird curves.

Then there's still a possibility to limit your control-input via external tools (similar, but more static than what the elasticity params do).

I don't want to start mucking about with .cfg.s What have you got dialled up on the sensitivity options in sim?

 

We already told them that lowering the sensitivity wasn't the solution, but they went and did it anyway, shoveling it to us as "bug solved", it's the french way of telling "I don't care, my solution is better even if it's wrong".
I hate bugsobo more and more every day.

Can we somehow disable the controls in the sim and use FSUIPC to set up the controllers like we did in FSX and P3D?

1 hour ago, EmaRacing said:

We already told them that lowering the sensitivity wasn't the solution, but they went and did it anyway, shoveling it to us as "bug solved", it's the french way of telling "I don't care, my solution is better even if it's wrong".
I hate bugsobo more and more every day.

Is lowering the sensitivity all they did? Because before I had my sensitivity settings extremely low, but still had problems. Now everything is much less uncontrollable. Just using a joystick BTW.

Voted...

We need greater (or user) control over the sensitivity curve. The generated curve just spikes the sensitivity at the far ends.

Other sims (X-plane and DCS World) all have custom curves where the user can clamp the curve “per” plane, or have a flatter linear line across the throw (X and Y paths), such as…

X = 10, y = 8

X = 50, y = 40

X = 100, y = 80

This is how I am mapped in other sims to control the total output / sensitivity depending upon the different planes / Developers. I am not sure if surface deflection / reaction / sensitivity is consistent across the board for all controllers and planes, but being able to dial in each plane has worked for me with custom curve settings.

I think Asobo should allow custom curves.

Well there is a payware that might be worth a look there is a demo 

https://secure.simmarket.com/lorby-si-axis-and-ohs-fsx-p3d-msfs.phtml

Avsim forum

https://www.avsim.com/forums/forum/794-lorby-si-payware/

Edited October 31, 20205 yr by Richard Sennett

3 hours ago, Will Fly For Cheese said:

So what have you guys got dialled in for now as a work-around?

 

Best solution I found was to use the Joystick curves software, its free and I basically set a linear curve for my Honeycomb yoke and it works wonderfully. I leaver all the crappy MS curves on zero. I did the same linear curve for my Saitek rudder pedals and I can now perform a take off roll without exiting the runway midpoint lol

I can definitely recommend, it is 100% free and takes no time to setup

5 minutes ago, Richdem said:

Best solution I found was to use the Joystick curves software, its free and I basically set a linear curve for my Honeycomb yoke and it works wonderfully. I leaver all the crappy MS curves on zero. I did the same linear curve for my Saitek

Would assume you are referring to this ? thanks 

https://www.xedocproject.com/joystickcurves.html

Is this only for a Saitek X52  ? 

Edited October 31, 20205 yr by Richard Sennett

4 minutes ago, Richard Sennett said:

Would assume you are referring to this ? thanks 

https://www.xedocproject.com/joystickcurves.html

Yes,

I downloaded the first driver as I couldn't get the 2nd one to work. once installed make a note of your current assignments for yaw, pitch and roll i.e Roll - L-Axis X

Then select the virtual driver in MS control panel and manually search for the assignments. Then delete the original assignments 

Edited October 31, 20205 yr by Richdem

6 hours ago, ChaoticBeauty said:

Voted, though I would suggest posting this in the Wishlist section instead. It is less crowded and it might gain more traction.

True, but I won't double post. I was already scared that one would get deleted as the original thread was moved into the "solved" section weeks ago.

We got around 50 votes already. That's not bad. I think if we get back to around 200 it should be in the top 20 again and cause some awareness. 😄

Edited October 31, 20205 yr by tweekz

On 10/31/2020 at 5:38 AM, robert young said:

0:0.3, 12:0.4

Where the first zero equals zero knots and the next value means 0.3 out of 1, or under a third of the authority, and the next speed (12 knots) has an authority of 0.4, and so forth.

You can then enter the next speed, say. 55 knots, and apply a slightly higher value of authority thus:

I found that the first value is not speed, but the dynamic pressure in kg/sq.cm (if I'm not mistaken the units). So 30-40 is about cruise speed for C172. While trying to adjust these values thinking they were knots I didn't succeed.

Their new sensitivity curves aren't even symmetric.  You get one response on the - axis side and another response on the + axis side of the curve.  At the high negative sensitivity values greater than say -50% (which at least made a smooth curve in the prior implementation) you can actually create curves where the response goes DOWN with greater joystick deflection.

How they could be so inept to implement something this poorly is beyond me.  It's like someone implemented some 3rd order polynominal smoothing and never bothered to look at it and see what it actually did. I'm getting the feeling that it's not helpful for us to give Asobo feedback because they are mucking things up worse and worse and then marking the tickets as 'solved'. Night lighting being the other example in this update.

This whole thing is absolutely idiotic and makes me seriously consider deleting the entire thing and buying a copy of X-Plane.

As far as I can tell the only settings that make sense in the controller sensitivity is a straight linear curve now, and it's up to the people doing aircraft to make their aircraft work with the linear curve.

Edited November 2, 20205 yr by marsman2020