Standalone Problem

Target Platforms Desktop
1

Hey,

I’m having a weird problem, I published a project either as standalone and as webplayer, I tested them and they function well. But when I burned a CD and click on the standalone unity file I receive a explorer message that the app stoped working and will close, even before the player loads. The weird part is if I copy those cd files to my desktop it works fine !!!

I tested to burn even in a cd and a dvd media, used 2 different computers to burn and tested in 3 different computers (1 with 1G, other with 4G and other with 8G ram memory)and have always the same problem, and also tried to publish again.

The webplayer files works just fine…

Just to let you know the standalone folder have 215M.

Any ideas on what might be causing it or solution for this problem ???

A Morris

2

Unity needs write access to the device its executed as standalone (to store the log) or it will fail

3

but I do have another project that worked fine when executed from a cd !

4

Is that other project a web project where you start double click the html?

Or no 2.5 windows project?

5

No, it was a Windows Standalone either !

6

was this made with 2.1 ? since 2.5 it will crash because it can’t write the log file.

7

2.5, but again, I do have another project that works just fine when played from a cd our dvd, and I also made a test with some other project and worked as well …
And if this log thing is true, what sould I tell a possible client, that he can not burn a cd because it will not work ???

8

Compare the scripts.
Potentially the log requirement is related to the usage of Debug.Log

Also you would tell the client to do what you always have to do with games: install them as the harddisk is 10++ times faster (I’ve a 4 disk RAID, pushing through 240mb/s, a CD / DVD is a joke compared to that)

9

Sorry, didnt quite understand. Are you suggesting to compare the projects scripts to see if there is a log requirement in the one that is presenting problems?

10

Hey, now the other project is crashing as well… I see that a output_log file is genarated and modified every time that I run the file !!!
Question: Is there any script that I can add to the project that makes the output_log file to be created and modified in the user’s HD instead of the driver that is executing ?

Is this problem will be fixed in future Unity versions?