[Technical Feedback] VelocityOne Race: Critical FFB Signal Drop at 50% Input & Non-Linearity Analysis
Hello, I am a VelocityOne Race user. I recently analyzed the raw Force Feedback (FFB) logs from the wheel because I felt some irregularities while driving.
I found two major issues that seem to be related to the firmware. I hope the engineering team can look into this.
1. Critical Signal Drop at 50% Force (Raw Input 5000) There is a specific "dead spot" where the wheel loses position data exactly at the 50% force input mark. I logged the data (Input vs. Output) and found a reproducible error:
- Input 4900: DeltaXDeg = 377.1
- Input 5000: DeltaXDeg = 0.45 (Signal drops to near zero)
- Input 5100: DeltaXDeg = 377.9
This occurs consistently. When the game requests 50% force, the wheel momentarily sends a near-zero response, causing a noticeable "click" or loss of FFB detail mid-corner. This happens regardless of the simulator (AC, ACC, AMS2). I have verified that this is not a USB or grounding issue.
2. Non-Linear (Boosted) Force Curve The wheel's default FFB curve is heavily "boosted" (Gamma approx. 0.7).
- Issue: The wheel reacts too strongly to small forces (0-30% input), causing oscillation and clipping even at moderate gain settings.
- Workaround: I currently have to use a custom LUT in Assetto Corsa or modify config files in AMS2/LMU (setting sensitivity/gamma to ~0.7) to get a linear 1:1 response.
- Request: Please provide a "Linear Mode" toggle in the Tuner App for PC sim racers who prefer a raw, unboosted signal.
Summary: The 50% force drop seems to be a firmware bug that needs an immediate fix. The boosted curve makes it difficult to play titles like ACC without aggressive damping.
I have attached the log analysis graph below. Please forward this to the dev team.
https://www.overtake.gg/downloads/lut-generator-for-ac.9740/
Posted Jan 30, 2026, 5:24 AM UTC