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
I hope that this at least gives you an idea where the state is for these issues for the game. Not many players could've been using any of this so far it feels like. I guess we have some work to do to fully support these things. At the moment working on these issues would kill our time to improve the game in all other areas. How important is this to you? Is the Steam Controller your preferred controller? Do you often play using Big Picture Mode? Doesn't button mapping in the options menu work at all?
EDIT: And to confirm the gamepad is confirmed working elsewhere, such as in Big Picture navigation and other games.
What does the log say? Try posting them both here.
KeyConfig.ini
SessionLog:
However there's a new issue. It seems that when hitting what I assume is top speed or at least a high speed, a load of smoke puffs out of the tires similar to locking up, however the car does not seem to decelerate much if at all, and steering is almost entirely locked when this happens and I inevitably slam into a wall and the lock is gone and I can drive fine again. I suspect it might be related to the driving model, as during this race 2 AI racers also got completely lost in the trees and were unable to find their way out.
I've seen it before and it is usually because the physics engine can't keep up during low framerates. since physics updates are now based on refresh rates I'm suspecting that it auto-chose a low refresh rate.
Could you post from the log what it actually chose?
Does it help to set an explicit refresh rate in the ini like before?
If that does not help, does it help setting explicit refresh rate AND resolutions in the ini?
Thank you so much for testing, this would've been bad if we set it public.
Frame rate in general was terrible. Setting refresh rate manually didn't help, but setting resolution AND refresh rate fixed it.