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
Bizarrely, the latest set of Nvidia drivers appears to have improved but not totally solved the problem for me.
While not a problem, and we do it when modding because you ought to play like 10 minutes, so logs wont get obscene, but making it the default setting is absurd.
I had the same problem a while back, in which if I played for half an hour, no mods, regular medium graphic settings, the game would start crawling to a halt. And when ending the game, it would linger in memory.
When I went dig what was happening, I found out that the logs are MBs long, with lines like "patron hasnt found animation", or "emote line not found", or "table has X lines", and other messages that make sense in the deep code debugging, but not at all for players.
When I set my global log to stop, the game was even better than it was before.
[Core.Log]
Global=none
There might other settings to completely make logging get efficient, but given the number of messages it register and most of them are due to "oversight" on the core game, we should not be burdened to keep logging it.
Between that and the optimization from that guide, my game is running much better now.