- Home /
4x longer compile times in Unity 3.1 (compared to Unity 2.6.1) - is this normal?
I have a 8.000 lines C# script in my project (mostly declaration and GUI code): it compiles under 5 seconds with Unity 2.6.1, but takes 23-24 seconds with Unity 3.1. This poses a serious workflow problem, as I work on the script all the time.
- Is this something all Unity 3.x users have to deal with, or is it just my case?
- Is there anything I can do about it? (editor settings, ...)
P.S.: To run the Unity 3.1 editor I use a PC with Win 7 64-bit on a quad core CPU and use MS Visual Studio 2010 to write my scripts.
Answer by Skjalg · Nov 25, 2010 at 09:41 AM
You could take advantage of the new DLL linking that game with 3.1 (secretly in 3.0) and divide up your 8000 lines of code into different projects so you dont have to recompile everything all the time.
It will most likely structure your code better as well as you get a clear overview of your dependencies :)
Thank you for your answer, I'm aware of these options. I'm still curious weather other users experience a similar compile times rise when migrating their projects from 2.x to 3.x
Your answer
Follow this Question
Related Questions
MonoDevelope and Unity 1 Answer
Compiler error with MySQL connection in Unity 3 (System.Drawing) 2 Answers
force refresh / reimport of all script files in a Unity project 0 Answers
Can Unity 3.1 be configured to watch scripts and recompile immediately, like Unity 2.6? 1 Answer
3d Application compatability 1 Answer