In my development setup, I do everything on my Mac Mini, except for coding. The coding I do in Visual Studio on my Windows XP box. All the project files are in a local folder on the Mac. This works fine, except for one annoyance:
If I edit a script on the Windows box, save it and then run the game in Unity on my Mac, I’ll usually get error messages because the script hasn’t been reimported in Unity yet. To have it reimported, I either have to wait until Unity reimports automatically - which can take anything from a few seconds to several minutes - or arduously select each of the changed scripts in the project pane and then choose Reset from the import settings menu for the script in the inspector. Only then can I run the game in Unity with the updated scripts in effect.
This is a minor annoyance when editing one or two scripts, but quickly grows in aggravation levels whenever I’m doing larger refactorings that span several scripts.
I’m assuming this reimport delay is related to my editing the scripts across the network, since I never saw this issue when coding in the hideous MonoDevelop that was installed alongside Unity on my Mac.
Is there anything that can be done about this, or do I just have to live with it? Any setting in Unity that affects this? Any Mac OS X tricks to alert Unity to the fact that the file has changed?
Just to clarify: it’s just Unity that’s slow to realize the files have changed, so this is not general network slowness. MacHg, for example, sees the changes instantly.