OK, Everything was fine until I tried to load in the new model I bought for my project. Now the ‘updating assets’ load screen never finshes. It gets about 90%-95% and then stops. So…
1- I removed the model (.obj file) and all referrences to it’s textures, materials, etc. I thought the model might be too big (16k polys), but It still won’t launch. It looks like it may have gotten a little further, but not all the way.
2- I removed anything from the working folder that I am not using for this project. Same thing.
3- Restarted, etc. I did all the other computer stuuf I know to do.
Anyone have an idea why the assets will not load? Any idea what I should do about it? This particular model is the basis of level 1 so I’d kind of like to get it in there one way or another. Thanks.
If you mean exporting from Unity, no since it won’t open fully. If you mean exporting from another 3D package, I think I already cleaned up everything except the basics.
There is really nothing in there I must have, so maybe I should just erase and reinstall it?
Does anyone know in what order Unity loads it’s assets? Maybe it isn’t a model that’s hanging- maybe it’s something else?
I haven’t changed anything since the last time it launched successfully, so I don’t think it’s that. I didn’t compress the textures before when it was working fine, though.
Unity loads assets in the order they’re needed = you don’t know.
If it’s importing, try running /Applications/Utilities/Console Unity prints the name of each asset before it imports, so if its barking on a weird mesh, you can see the offending file.
Regarding this problem: look at the Console output or zip the whole project folder and send via ReportBug.app (it’s next to Unity in Applications/Unity).
By the way: you can keep the Option key down while launching Unity - then it won’t open the last project but instead will offer a new project dialog.
Thanks everyone. I got it working- still haven’t tested the offending model- the one I purchased for this project. Hmmm.
I used the console to track down the file and it was, as I suspected, the new .obj file. I had deleted the file from it’s default location and Unity was getting hung not finding it. I used then option key to start a new project and I am good to go. I don’t know if this will fix the problem of it not importing correctly, but at least now I have options if it hangs again. I think the old project (with the funky mesh) may never open again because the file no longer exists and Unity keeps looking for it. Not a big problem for me now, but that might be a bigger problem down the road if it happens again and I am further along.
I dont know exactly, but the poly-limit per object is somewhat arround 65k Polys. And if its modelled in quads unity has to triangulate, so the polycount doubles up when importing. I stumbled upon the same problem while creating terrain for a level…
the model’s only 16k polys right? shouldn’t be a problem. did you open it in your modelling app and resave? i’d also look to see if it has any ngons, 2 point polys etc. maybe something like that. alot of what you get online isn’t optimized for realtime and needs clean up.