Unity 2.6 Project Doesn't Load

Unity Engine
1

I have a Unity 2.6 project that I have developed on the Mac and am trying to run on Windows 7. On opening on Windows it process the assets but then seemingly hangs. Looking at the task manager shows its using about 25% of the processor and increasing memory usage very slowly. The interface is non-responsive while doing this. Is there anything I should try or test?

2

Try turning off any real-time virus scanners you may have.

3

do you load it in Unity 3 or did you transfer it through svn / with metas?

if so it will have to import the stuff / reimport the stuff and it will not do anything else but that.
the loading bar shows up if you hover over the symbol in the task bar potentially.

4

Thanks for the reply. I have it in 2.6 on the Mac and transferred via thumb drive to Windows 7 so no SVN involved. I’m trying to load it in 2.6 on Windows. There’s some issues with some new script errors when I run in 3.1 so I haven’t gone there yet with this project.

5

You didn’t load it into 3.1 and then tried to open it in 2.6 did you? Once converted to 3.1 it won’t load into 2.6 anymore. If it isn’t that, my money is on it either being a file sharing issue (permissions), the virus scanner, or a corrupted asset.

6

Thanks for responding. I’ll have to check the 3.1 thing because its not out of the realm of possibility, but I’m pretty sure I copied the 2.6 version from my mac source because the 3.1 version has script issues. I’ll try it without the virus scanner. What would I do or check with the file sharing issue?

7

In Windows 7 I sometimes get a “couldn’t write xxx file” error while running Unity. I don’t fully understand the issue as I’m also new to Windows 7 (from a Mac) so I still haven’t sorted that one out. There are a couple other threads here regarding issues with virus protection and Unity. My particular issue was that I was using Microsoft Security Essentials which would cause Unity to either lock up my system and/or cause a hard disk “dirty” error. Turning off the real time scanner fixed it for me (and another fellow with similar issues).