Why… Why on earth…
Why on earth did the Unity editor application make 50 GIGABYTES OF DATA for F##### EDITOR LOGS?!
(And why on my precious way to small C:// drive…?? ;-; )
Like Why?
Does anyone know?
Editor logs only become this big if:
Check what‘s in the file and you‘ll see what the most common log entries are. Notepad+ I think can open large files without loading everything into memory (don‘t try Notepad for that reason).
Or simply check the Console window - everything in that window goes into the editor.log plus internal logs.
PS: you can decrease the log size by enabling compression for that folder (right click — properties — and then i don‘t know but shouldn‘t be hard to find). Requires elevated access.
there is something wrong here. 50Gb, we are talking about an enormous amount of text.
is that even possible?
If you never close the Editor, the log will just keep piling on. Closing and reopening the editor should clear the log.
I didn’t know the console log of a editor session was saved to disc lol, Yes, i use Debug.Log a lot, also have a few of those running in OnDrawGizmos causing them to generate outside playmode, for debugging purposes and temporary variable readouts.
Besides, would anyone happen to know if there might be a possibility of making the editor save these logs to a folder on a different drive / user specified location? It would help a lot if i leave my editor open for longer periods of time, (my C:// drive only has 51GB left… its a crappy tiny 128GB SSD drive :/)
I believe you can instruct Windows to use a different location for things like user folder, AppData and such. At least it used to be possible with MS PowerTools (or Toys?). However, this is brittle as frick, I wouldn‘t recommend doing that. Especially if for some reason the D drive is unavailable or drive letters are being swapped then you are in a hell of pain.
The better alternative is to move some of your Program Files to another drive. Unity for instance, or Steam Epic Origin etc default locations also end up on C: by default.
One thing you can try is using Junctions / hard links / symbolic links (google it for instructions) making the „Unity“ folder under User/AppData point to another folder on another drive. That should be relatively save considering the folder contains only .log files (I believe).
Actually it will rename Editor.log to Editor-prev.log and create a new Editor.log file so there will still be GB of prev logs around.
Thing is, my C drive has 128 GB of data, 118 of which is available, 20GB which is used for the inevetable developer environment files to be able to use unity and some other utilities, and 28 GB is used by the windows folder… The rest of all files on my C drive are a couple MB for the sake of running windows stock applications (Like MS paint, microsoft edge etc…)
This leaves me with ~ 52 GB on my C drive (Developer environment + Windows + stock applications = ~65GB out of 118 used leaves ~52), so i don’t really have anything on my C drive to move around (Program files is only 6GB, Most of program files are folders with windows or microsoft in the name, i don’t want to move those)
I will look into “Junctions / hard links / symbolic links” to see if i can make unity put the logs into my other drive.
And i will also look into buying a larger SSD drive lol.
I think you 100% should find out why your logs are getting this big. It indicates the shit has hit the fan.
For example my log is currently 524KB and I often log every frame when testing.
When having to live with a small C drive this program is invaluable:
https://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
It adds Explorer menu shortcuts for creating junctions/symbolic links, so you “pick” a source then drop a “link” at the desired location. This way you can move pretty much anything to another drive.
