More Logs required for the Kingdom crash issue
Posted: Wed Feb 20, 2013 10:32 am
It seems like the Kingdom upgrade is stressing our memory limits again, at least, that's what might be happening if these Unity crashes are anything to go by. That means that we need Unity logs to be able to identify what's going on and see if we can fix it (unfortunately our bug-catching/notification system isn't able to record anything if the whole plugin crashes).
Please post your Unity Web Player logs in this thread. To get to your Unity Web Player logs, open up a Run dialog box and type in "%TEMP%\UnityWebPlayer\log" to open that folder in Explorer. Then open up the newest log file (sorting by date helps) and copy-paste that wall of text here. Don't worry, we can read that Also, please note that the log files are often deleted after you close the Web Player, so try to keep DD open in your browser while hunting down log files (it doesn't hurt to check that the newest log file is recent enough to be from your current play either).
Again, this isn't a discussion thread, this is literally only a place to store data that we can use to solve these problems, so I'll be moderating it quite heavily. Thanks in advance for any logs posted!
Please post your Unity Web Player logs in this thread. To get to your Unity Web Player logs, open up a Run dialog box and type in "%TEMP%\UnityWebPlayer\log" to open that folder in Explorer. Then open up the newest log file (sorting by date helps) and copy-paste that wall of text here. Don't worry, we can read that Also, please note that the log files are often deleted after you close the Web Player, so try to keep DD open in your browser while hunting down log files (it doesn't hurt to check that the newest log file is recent enough to be from your current play either).
Again, this isn't a discussion thread, this is literally only a place to store data that we can use to solve these problems, so I'll be moderating it quite heavily. Thanks in advance for any logs posted!