Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
time = 21 minutes
in order to see him losing control.
I tried to post a link that starts playing at t=21m but didn't work.
You can add
&t=21m
to the link above to start playing at the right time.
I've played FH3, FH4 and FH5 exclusively with a Logitech and a Thrustmaster wheel. The game is perfectly playable, specially FH5. Wheels have never been a plug-and-play experience, even more if you're a controller player. It takes months to get used to, and even more to master.
After playing more with the wheel settings and comparing the driving experience in FH5 with that of Assetto Corsa and AC Evo,
I'm getting quite convinced that there is problem with FH5's handling of the wheel.
My current guess is that the game
-applies a smoothing algorithm to the controller/keyboard inputs which works well
-it applies a similar smoothing to the wheel inputs which works poorly
The input smoothing works well for the keyboard and controller and makes the driving experience enjoyable.
The keyboard inputs are all or nothing so smoothing is definitely required.
Most of the time, the controller inputs are also "bang/bang" or "end to end" inputs so a similar smoothing works well.
But a wheel doesn't need smoothing or it should only be very slight (to eliminate small noise for example).
If the FH5 devs apply heavy smoothing to the wheel inputs the effects will be very similar to what we're seeing.
It could be perceived as a delay (in my case).
Ttower seems to have a similar idea/perception:
Guess, I'll keep fiddling with the settings, but if my guess is true, it should be corrected by the devs.