Stop game from logging into Player.log

[stars☆]

I just noticed my disc randomly ran full and the game crashed just to see it created a >30GB Player.log file located at AppData\LocalLow\Ludeon Studios\RimWorld by Ludeon Studios

[Hoki]

thats an engine related bug caused by some mod-incompatibilities.

[stars☆]

Yeah i noticed and im doing some digging to find the issue since it seems to be caused by one mod alone.

[azrael502]

im having a similar issue can i ask what mod was the issue

[stars☆]

for me it was ore yields mods which was outdated: https://steamcommunity.com/sharedfiles/filedetails/?id=2036872981&searchtext=ore+yields

You can also send me a screenshot of the errors showing up in the ingame console so i can try to backtrace it

[azrael502]

thanks i got it sorted

[test]

it would be good because the log file will always be on app data which is always on ssd if windows is installed on ssd, so it wears out ssd. And unfortunately in rimworld enormous log files are something you should expect when building a mod pack. I've seen reports of people getting a 1 TB log

[Khan Boyzitbig of Mercia]

A log file above a few mb is a log filled with errors that bypassed the logging limiters designed to prevent multi-gigabyte logfiles.

[test]

Originally posted by Khan Boyzitbig of Mercia:

A log file above a few mb is a log filled with errors that bypassed the logging limiters designed to prevent multi-gigabyte logfiles.

stupid too many sound sources error bypasses this limit, and opengl errors related to game loosing focus when you close it, those are not even errors they are opengl and the unity sound bugs

[BlackSmokeDMax]

There is also the modder only issue (meaning nothing to do with the Unity engine) that they leave their logging turned on by accident when publishing the mod.

Basically some modders turn on non-limited logs when testing their mods and forget to switch them off before compiling/releasing the release version of the mod. It is an easy fix on their end, but only if they know about it. So if you find a mod doing that, make sure to report it to the author!

[stars☆]

I figured out writing a script that removes those files or limits their size causes rimworld to crash. So I guess you have to live with it.

Im only annoyed that it has to be located on appdata and not somewhere else so its not doing that many writing operation on the medium that also handles windows

[Vattende]

It's simply mostly a mod where the modder did forget to turn off logs, this can spam your folder. That's why installing full mod packs isn't still a smart idea.
Knowing the mods you use, but also testing each after install avoids lot of this stuff.

[Astasia]

Have you tried disabling verbose logging? In options turn on dev mode and a few new options appear, one of them is verbose logging which causes the game to log like everything, and some mods will cause some issues like that if you leave the setting on. Turn the setting off then turn off dev mode and it might fix your issue.

[Razor 2.3]

Originally posted by nico:

I figured out writing a script that removes those files or limits their size causes rimworld to crash. So I guess you have to live with it.

Im only annoyed that it has to be located on appdata and not somewhere else so its not doing that many writing operation on the medium that also handles windows

You can override that. From the game's documentation:

Originally posted by readme.txt:

OVERRIDING:
You can override the save data folder. This is useful, for example, if you want to install the game on a USB stick so you can plug and play it from anywhere. To do this, add this to the end of the command line used to launch the game:

-savedatafolder=C:/Path/To/The/Folder

So it'll look something like this:

C:/RimWorld/RimWorld.exe -savedatafolder=C:/Path/To/The/Folder

If you don't start the path with anything, it'll be relative to the game's root folder. So you could do this, to have the game save data in a folder called SaveData in its own root folder:

-savedatafolder=SaveData

If there are spaces in the path, you'll need to surround the command with quotes:

"-savedatafolder=Save Data"

Be sure the game is running with permission to modify the folder. It may not work properly if, for example, you run the game under default permissions on its own install folder.

[test]

Originally posted by Razor 2.3:

Originally posted by nico:

I figured out writing a script that removes those files or limits their size causes rimworld to crash. So I guess you have to live with it.

Im only annoyed that it has to be located on appdata and not somewhere else so its not doing that many writing operation on the medium that also handles windows

You can override that. From the game's documentation:

Originally posted by readme.txt:

OVERRIDING:
You can override the save data folder. This is useful, for example, if you want to install the game on a USB stick so you can plug and play it from anywhere. To do this, add this to the end of the command line used to launch the game:

-savedatafolder=C:/Path/To/The/Folder

So it'll look something like this:

C:/RimWorld/RimWorld.exe -savedatafolder=C:/Path/To/The/Folder

If you don't start the path with anything, it'll be relative to the game's root folder. So you could do this, to have the game save data in a folder called SaveData in its own root folder:

-savedatafolder=SaveData

If there are spaces in the path, you'll need to surround the command with quotes:

"-savedatafolder=Save Data"

Be sure the game is running with permission to modify the folder. It may not work properly if, for example, you run the game under default permissions on its own install folder.

it stores saves at specified location, but the log is still being written and stored to appdata on C drive

[[Unknown]᠌]

To stop logging, you can do the following::
Clear the file and set the "read-only" attribute
for files:
Player.log
Player-prev.log
----------------------------
Для прекращения логирования можно сделать следующее:
Очистить файл и установить атрибут "только для чтения"
для файлов:
Player.log
Player-prev.log