"Use anisotropy" persists

[a584-droid]

Nothing works. I just need to constantly open a gui to remove. It isn't constantly applying. So i need to really try hard. Sometimes it is, sometimes it may seem to apply an effect…

[AndyFilter]

Hey, I'm not gonna pretend like I understood this:

Nothing works. I just need to constantly open a gui to remove. It isn't constantly applying. So i need to really try hard. Sometimes it is, sometimes it may seem to apply an effect…

So, lets break it down.

Nothing works.

Pretty sure some things do work...

I just need to constantly open a gui to remove.

Remove what? The anisotropy? You have it technically removed in the screenshot you attached. As the ratio is 1.

It isn't constantly applying. So i need to really try hard. Sometimes it is, sometimes it may seem to apply an effect…

Yea, so I don't know what mouse and DPI you're using, but you have a pretty "slow" curve:

That might explain why you might not feel the effect, assuming you're using a mouse with a DPI like ~800 or ~1600.

I'm not sure where you got the value of Pre-Scale of 0.22 from, as it translates to roughly 3636 DPI...
Output Cap at 4 is a... safe choice to say the least. The curve is nowhere near 4, so it's not doing anything.
I don't know if you just set some random parameters, or if this is actually what you wanted, but either way I need more details.
What have you tried?
When does it automatically reapply (guessing it does from this: "I just need to constantly open a gui to remove"). On reboot? Re-login? Just randomly?
Are you clicking "Apply", or "Apply + Save"?
And the one question couple of lines above.

[a584-droid]

Are you clicking "Apply", or "Apply + Save"?

I'm clicking on Apply + Save and then Apply. But this may have some issues with how program changes parameters if order is backwards: "Apply" and then "Apply + Save".

I don't want to comment other your criticisms. The reason is that how it works and configured even in mouse acceleration program for Windows (I forgot its name but I guess you know it). If you have anisotropy active it somehow like creates a different line. It feels like mouse interprets not only that curve but an additional which kinda different. I'm not sure about formulation. But sometimes it works like should have been.

And I forgot to mention that it also connected to Speed Smoothness. It's like I also have been changing it to 0 cause it felt too fast. But my screenshot with 75 felt actually better than it should've been.

In other words it feels like my cursor is going mostly from left side rather than from center like it should be.

So I keep this issue here until I get consistent feeling after changing or not changing some parameters.

I know it may be some bias or placebo. A lot of problems may be and occure from time to time with other programs too. So I'm really on this to compare with every time.

Since even changing scaling may have an effect on mouse accel I think this might be a more complex problem than only with this driver. Cause that after changing it feels sometimes inconsistent too.

Like I use to change from 150% scale to 100% every time I'm gonna play. And I need to be sure that anything got stocked.

Sometimes it's easier to reboot and start a new session and then ensure that everything works smoothly.

Sorry I don't have enough time to recheck this for you.

[AndyFilter]

My bad, I the program cut the decimal points. With Pre-Scale of 0.(2) it does indeed equate to 3600DPI.

If you have anisotropy active it somehow like creates a different line.

Yea, because now you have 2 different acceleration curves, depending on the direction of the mouse movement.

It feels like mouse interprets not only that curve but an additional which kinda different. I'm not sure about formulation. But sometimes it works like should have been.

I'm not tracking again. How do you expect the anisotropy to work? To all curve parameters be different for each direction?

And I forgot to mention that it also connected to Speed Smoothness. It's like I also have been changing it to 0 cause it felt too fast. But my screenshot with 75 felt actually better than it should've been.

This slider does absolutely nothing functionally. That's why it's not in the Parameters window, and rather - above the graph, which it influences.

I feel like you should run some more "analytical" tests, if you felt any difference changing this parameter, as - like I said - it doesn't change anything.

In other words it feels like my cursor is going mostly from left side rather than from center like it should be.

Is your cursor moving on it's own? I'm completely lost again.
Or is it faster when moving left to right rather than top to bottom?

I know it may be some bias or placebo.

This. But, if you want me to check the exact config against RawAccel, send me the parameters (File->Export), and I'll check if it gives the same results as RawAccel with an Arduino Pro Micro emulating perfect mouse movements.

Sometimes it's easier to reboot and start a new session and then ensure that everything works smoothly.

That's odd, the behaviour should be consistent if you apply a config, and when it's applied automatically on boot.

---

Again, I feel like there's a language barrier playing a role here. I'm still not sure what the issue even is, and I won't be able to help you if I don't know what's the problem.

Can you send me the configuration you used in the Windows program (which I assume is RawAccel)? And I'll try to give you a configuration that would be equal to it using YeetMouse.