Implement missing FFB effects

[Ultrawipf]

Most effects are not used by most games but all effects reported as supported should be implemented in some way.

Supported are currently (edited with current devstate):
Constant force
Sine
Square
Spring
Damper
Friction (Needs tuning)
Deadbands for spring and damper
Inertia effect (Needs tuning)
Triangle
Envelope (kind of)
Sawtooth
Always on damper

Missing:
Optional custom force (or remove from descriptor as its not really standard anymore)
Testing multi axis effects
Always on filter and inertia

[arilink-tech]

I did not find the relevant calculation formula in the USB PID document. Does the force feedback calculation formula need to be implemented by myself?

[Ultrawipf]

I did not find the relevant calculation formula in the USB PID document. Does the force feedback calculation formula need to be implemented by myself?

There are some examples how to implement the conditional effects. But its already being worked on in the active development branch.

[arilink-tech]

How long will it take to perfect these force feedbacks? I will upload a document later, which contains the types of force feedback output by different games.

[Ultrawipf]

Well. Perfect depends on the game and hardware. But the goal is to make it as tunable as possible and provide a good feel with most setup.
Overall i think it is pretty good when tuned properly but it needs a lot of testing and comparing to further improve it.

Having a list of games and which effects they use would be great.
Maybe also for what scenario a different effect is used if possible (like spring only in menu, or sine for extra rumble) and at which rate updates are sent if known.

[arilink-tech]

test result：

[arilink-tech]

From the results, Friciton needs to be supported. Traingle SawtoothUp SawtoothDown is unnecessary.

[jonlidgard]

All effects apart from custom are already implemented, although there is stills some tweaking to do with a few of them (friction, inertia - rarely used). If you use the latest dev version (rtos_multiaxis branch) you can run a game & then, using the Configurator app, issue the 'effects' command & it will tell you which effects the game used. Essentially any game that respects the official FFB spec should work, some work better than others but that is down to how the game is coded & not something we can change.

[jonlidgard]

Friction is supported but we're still experimenting with different gains & filteringt to improve the feel.

[arilink-tech]

Ok, I will try the rtos_multiaxis branch. I am currently modifying the code in the Configurator and the main branch to get the effect of the game.

[jonlidgard]

One thing that isn't implemented yet is assigning an effect to a button e.g. pressing 'fire' button gives feedback which might get used in some games like DCS

[arilink-tech]

Does the program need to adjust the gain and filtering for different motors to improve the feel?

[jonlidgard]

Ok, I will try the rtos_multiaxis branch. I am currently modifying the code in the Configurator and the main branch to get the effect of the game.

No need, that functionality is already implented in the dev branch. (You'll need the rtos_multiaxis branch of Configurator too)

[jonlidgard]

Obviously different motors will require different tuning according to user prefs, etc.

[arilink-tech]

Okay, got it