output_log in appdata?

[akardam]

So, was doing a little troubleshooting with a bit of code, and was perturbed to find that my output_log.txt file was not to be found in its usual place. To make a long story short, I eventually discovered it being generated in the following directory:

c:\users\akardam\appdata\locallow\squad\kerbal space program\

Seems recent versions of Unity player will place it there if it thinks the game is being run in Windows low integrity level?

https://docs.unity3d.com/Manual/LogFiles.html

https://docs.unity3d.com/Manual/WindowsLowIntegrity.html

So, I beat my head on my desk for about an hour attempting to work around this. I tried:

• Using the -logFile command line argument to KSP_x64.exe - no joy
• Using ICACLS and MicEnum to set both the game directory and the EXE itself to high - no joy
• Spooled up a Win7x64 VM with fresh, default settings - no joy

For what it's worth, 1.1.3 x64 doesn't seem to have this issue, though I suspect its older Unity version didn't have this behavior. I don't use in Steam, I download and unzip and run.

If there's an obvious answer to this issue, it eludes me. Being one who maintains several different KSP installs, them all barfing over each other in the same logfile is problematic when trying to solve a problem. Anyone have any ideas?

EDIT: Sorry... KSP Build 1.2.1 016042016.11.01, freshly unzipped

Edited November 5, 2016 by akardam
Added KSP build ID

[sal_vager]

Hi @akardam, Windows puts it there when Unity tries to write to a folder it doesn't have permissions for, a Steam install has a registry entry telling Windows it can write to the folder in Program Files, but a zipped copy of KSP will need to go into a non-Windows folder such as C:\Games.

You can also have this trouble if KSP is started via a desktop shortcut, or by ckan on the desktop.

If you have unzipped KSP to a folder in Program Files please copy it to C:\Games and run the copy.

[akardam]

Well, amazing what letting one's mind chew on a problem over a little sleep will do...

Some early-morning goolgling has revealed that this appears to be a Unity bug, affecting KSP since v1.2.x is still on Unity 5.4.0p4:

http://forum.unity3d.com/threads/no-output_log-since-5-4.419879/

 

Followup question: Would it be proper and/or useful to submit a bug on the KSP tracker for this, given that it is a Unity problem?

EDIT 1: In response to above suggestion, my KSP installes already reside in a subfolder of c:\games

EDIT 2: When I used ICACLS to set the KSP_x64.exe to medium, now it dumps the output_log in the usual place within the game directory. I'd like to call this one confirmed, Adam.

EDIT 3: Yes, I am one of those ungodly people who likes to live dangerously and always run as an administrator. Don't worry, my gaming rig has no direct connection to the interwebs.

Edited November 5, 2016 by akardam
What a coink-i-dink

[sal_vager]

Nice find @akardam, thank you, also Squad intend to keep updating Unity versions so as long as Unity fix this the fix will end up in KSP as well.

[Majorjim!]

On 11/05/2016 at 1:01 PM, sal_vager said:

unzipped KSP

What is this Sal?

 I had an issue where my log in the usual place was old and my game was saving the log to c:\users\NAME\appdata\locallow\squad\kerbal space program\

 I am using steam. It seems as long as I don't have more than one KSP install this is not an issue though.

[sal_vager]

KSP is available as a zipped archive from the Squad store.

[Majorjim!]

12 minutes ago, sal_vager said:

KSP is available as a zipped archive from the Squad store.

Ok thanks. I am using steam and mine still saves to c:\users\NAME\appdata\locallow\squad\kerbal space program\

[sal_vager]

You may be suffering from the bug here, Unity itself doesn't seem to make any checks for Steam.