I am working on a project that currently has 75 meshes with textures. The number of meshes and textures will continue to grow over the next few months.
Every time I add one new mesh and texture, the project starts "(re)importing assets" and takes forever (15-20 minutes sometimes). Even unchanged assets already loaded in the Hierarchy will reimport.
The files are not large (.ma files - Maya ASCII and each texture is less than a megabyte. No Maya Binary files are used so I do not believe the hangup is with FBX conversions). All paths are relative, so the import duration is not caused by pulling files from all over the place.
It is becoming somewhat of a momentum killer. . .
Any suggestions on how to speed this up?
Specs - Unity 2.6.1 Pro, MacBook Pro 2.5 GHz Core 2 Duo, 4 GB Ram, 512 Video
Does anyone know if the file management structure in Unity 3 going to change? It would be great open large projects with many assets quicker.
There is an option to stop Unity from automatically checking if files have changed and and reimporting them. Might be useful if you don't need to see any update of your work in Unity, like when you just add your assets without wanting to work with them right away. But this has the big drawback that you will have to manually refresh it. Not too good, but you get to decide yourself when the reimporting and all runs and schedule a meeting to fill in. ;)
It would be great if one could mark folders with "don't automatically refresh" flags or something.
answered Feb 18 '10 at 08:46 AM
We also feel this is an issue that needs to be addressed.
answered Feb 09 '10 at 03:58 PM
You should certainly contact email@example.com or else file a bug report for something like this.
answered Feb 09 '10 at 04:45 PM
Try disabling "Compress textures when importing" in the Unity Preferences (Edit/Preferences).
If that doesn't work maybe you could try contacting the Unity team directly, as 15-20 minutes is a first for me.
answered Feb 09 '10 at 12:55 PM
This only works in very specific situations, but if you have assets that you load procedurally (for example, you load a file and use Texture2D.LoadImage to convert to a texture), then those assets probably don't need to be processed by the asset importer.
You can prevent them from importing normally by changing their file extension -- my project has 100's of ".jpg.x" files which are loaded procedurally as individual frames of texture animations. The phony extension means they get imported very quickly with the default (do-nothing) importer.
answered Jan 09 '11 at 07:04 AM