v0.7.315

[coasting-nc]

[0.7.315]

Fixed

• Profiles Import was saving the imported profiles in the wrong folder, so the profile would not show up after a restart of the app.

FFB Safety

• Implemented Crash Protection Mechanism, limiting the slew rate when crashing hard with other cars or walls
• Fixed Slew Rate safety limiter being bypassed when Safety Duration was set to 0.0.
• Fixed FFB spikes due to Stationary Damping, Road Texture Fallback, Suspension Bottoming, and Yaw Kick

UI

• Added the "Slew Restriction" slider into the "General FFB" section to make it easier to find and adjust.

---

This discussion was created from the release v0.7.315.

[ricklovelisa]

I ran into a strange problem and I'm not sure whether it's a bug. When I keep the LMUFFB window open (regardless of whether Always on Top is selected), the in-game FFB is very smooth. But as soon as I minimize the LMUFFB window, there is a slight vibration in the FFB — not violent, but clearly noticeable, somewhat like a gear-like feeling. Could you help take a look at what might be causing this?

[coasting-nc]

Is it just a temporary thing and then the FFB returns back to normal?
It might just be the game retaking control of the wheel instead of the app.
In Direct Input, there is this thing that only one program can have control of the wheel to send FFB at a single time. So minimizing the app window might temporarily give back to the game priority over FFB.

[ricklovelisa]

Is it just a temporary thing and then the FFB returns back to normal? It might just be the game retaking control of the wheel instead of the app. In Direct Input, there is this thing that only one program can have control of the wheel to send FFB at a single time. So minimizing the app window might temporarily give back to the game priority over FFB.

This behavior consistently happens whenever I minimize LMUFFB, and it still occurs even after I disable the game's FFB. Could this be some kind of system-level restriction on minimized windows? Similar to how some games limit the frame rate when running in the background?