Prevent Unity from writing logfile

Hello all,

is there a possibility to prevent the compiled unity .exe from writing into the log file? Maybe via commandline? Any help appreciated,
Cheers
Moritz

Not right now. Why do you want that?

Due to some customer wishes we have to run the .exe from a read- only device, and as far as I figured out the only issue why it´s not running is because the .exe tries to write the log file. So any possibility to change the directory of the log file or to completely prevent it from being written would be very important. Is there any possibilty to reroute the logfile`s path?

Yeah, i think that’d be a good idea. Both options: deactivate and choose destination path.

Great idea. I just added it to our feature request database. ^^

nice to be added to the database and I really dont want to bother you guys, but it would be so nice to see it in the 2.5.1 bugfix release...maybe if its not too much work:-)

What does Unity do right now when being run from a read only devices? I would expect that it will just not write to the disk. Does it do anything different?

yes, unfortunately it does not start, it throws an system exeption before the display dialog is shown. I tried a rewritable cd rom and it worked, well of course it takes some time until the log file is written on cd…I´d say its not a really proper solution :-) btw. this happens with Windows Standalone compiled stuff, I didnt try with OSX compiled apps, but this should work - according to the forum.

It tries to write to the drive and fails with a crash. Haven’t experienced it personally, but dealt with a few cases where we narrowed it down to that.

Edit:
An alternative is to do it all as a webplayer, but that is not an acceptable solution in some cases, given the plugin limitation of the webplayer.

I had this same issue:

http://forum.unity3d.com/viewtopic.php?p=141616#141616

I posted a bug, #177471

I’m told this worked on 2.1, but not 2.5