- Home /
Want to start blank project and transfer old into it. What problems can I expect?
So my current project is cluttered. Really no single hierarchy and it's hard to find stuff.
I want to start new project, set up hierarchy of folders then transfer stuff from old project into this one, such as textures, models, scenes, prefabs.
What should I be careful of and what problems can I expect?
Haven't tried that before, but I$$anonymous$$O it's better to transfer shaders, then scripts, then art and then your prefabs. You can expect compiler error during the shift, but be sure that you don't miss anything, especially a shader or a script.
I don't think you will have to re-link your prefabs, only if you import them last.
If you're using Source Control, there are extra things to consider, like if you want to make a branch first, or what will happen if a file is moved vs. copied.
Project-specific settings such as collision matrix, custom tags/layers, build settings and so forth should be taken into consideration.
Well, I would go 'export' from the old project and 'import' in the new one - I always have bad experiences manually moving/copying stuff over I lose my prefab connections. I don't think you need to worry about any particular moving order this one (someone correct me if I'm wrong)
Answer by Mosy · Jan 05, 2015 at 04:31 PM
I would recommend actually not transferring to a new project. That won't really solve anything that you can't solve in you already existing game project. Also There is nothing preventing you from getting into another hot mess with organization in a new project. It would be best to just organize what is already working. You should actually save time that way, because you won't have problems were you missed importing something properly and you are just doing the same work that you will have to do anyway. I would recommend backing up the original working project and doing this to one of the copies of course.