I’ve recently discovered that every time I build a standalone Windows project with Unity 5.4.0f3, it never creates the output_log.txt file when run. The project setting Use Player Log is definitely checked. I’ve tested this issue with a separate project in the same Unity version and can reproduce it every time. Unity 5.3.5 does not have this issue - it creates the log file with no problem. I’ve even tried the latest patch version 5.4.0p3 even though the release notes mention nothing about logs and that made no difference.
I tried both the 32 and 64 bit versions of the 5.4 editor to no avail. The *_Data folder is not read-only, so it doesn’t appear to be a permissions issue. I can’t think of anything else to test. This is a significant issue for me since I’m trying to diagnose a completely separate issue in a project where it’s not progressing past a certain point in the built game but works fine in the editor.
Any insight into my issue would be greatly appreciated!
I faced the same issue and I learned that the location of the output_log.txt file has now changed in Unity 2017.
In Unity 5, it used to be in the game _Data folder (see Unity 5 documentation )
Now, it is stored in C:\Users\username\AppData\Local\CompanyName\ProductName\output_log.txt (see Unity 2017 documentation)
I find this quite an annoying change, so I added a suggestion to let developpers choose the destination folder.
If you’re interested, please support this feature here.
@Theodus Have you tried running the .exe as Administrator?
In my case (standalone Win app built with Unity 5.6.1) did make a difference. Don’t know if it’s a bug but AFAIK an app installed in “Programs Folder” should have accesss to its own folder, the rest of the folders that belong to others apps are protected. So, in theory, we shouldn’t need to use "run as administrator"for the app to be able to write the log.
