Merging two projects?

Unity Engine
1

Hi

tried to merge 2 projects - but when I wanted to import the package of the first project in my second project, I got the massage:

To shovel all the files from the one to the other project can’t be the solution.

Have anyone a better idea - or am I doing it a completly wrong way?

Thanks
Alex

2

Were both projects created with the same version of Unity? Just a thought…

3

jep, both are created with the only version I’ve got :slight_smile:
I don’t think it’s a pro-feature so my indie should be good enough

4

Hmmm, thats strange… we develop on different computers on different scenes and merge them via package import all the time. And we are using indi license as well. Cant think of anything, why it shouldnt work.

5

Hmm… I’d probably create duplicates of the original project folders, then dump the assets and scenes from one of the projects into the other and see how unity reacts on loading the project… then, see if the scene files from each project can be opened.

6

Doesnt manual import destroys the dependencies?

7

I’m not sure if unity tracks the complete path to project files or just relative paths. If it’s only the relative paths, it could still work, barring a name conflict in the files from each project or if Unity requires files outside of the assets and scenes folders to coordinate everything.

Then again, I’m still fairly new to Unity and haven’t had to attempt such a thing yet. shrug

8

@alpha-loup

yes - the dependicies were away.
Tried it…

So - will test now Bones3Ds proposal.

9

Oh I found a page on this in the unity documentation:

10

Hmm, that’s exactly the (one and only logic) way, I’ve tried it… :frowning:

Hmm, next try - anytime untiy is giving up - perhaps…
:lol:

11

If you create a .unitypackage like this and it then fails to import into Unity, that’s a bug. If you can, it would be great if you used Report Bug.app to report this to us, and naturally include the .unitypackage that’s giving you problems.

d.

12

—update—

After the reboot at the weekend and one last try before sending a report to davidhelgason finally it works.
Took the same way again (what Bones3D also wrote).
Don’t know the reason.
Could it really be the reboot of the mac?
Has anybody similar probs have had?

Alex

13

Yep, not in builds of Unity in the last year or so though. I recommend try it again and again, and you should find it works.

But It has been reliable in the last year or so, so just try it a few times. lots of things to do with computers need repetition for some reason. In my nutso world anyway.

Cheers
AaronC

14

I also found that sometimes Unity fails to do something with no given reason, even failing to put a gameobject on screen and then I just quite Unity, restart unity and suddenly it works.

So if something doesn’t work for you, maybe you could try that too.

I’m currently also looking into this way or saving scenes into packages since we make educational software with lots of activities and we want the to produce cd-roms with certain scenes on them and other scenes not. Seems like the .unitypackage way is the way to go.

15

Oh man, Iv’e just run into this issue and I’m a little worried that the only solution is to re-build the project… Did anyone find a good way to fix this? It seems like if I try to import an “infected” .unitypakage it makes it so that project can’t import any other .unitypackages :frowning:
I have a horrible feeling I’m going to loose a lot of time here…

16

Damn, Just happened to another old project of mine!! I’m cursed.

Is there a way to move assets to a new (clean) project without using unitypackage? (exporting doesn’t work with these corrupted projects).

At the moment it looks like I’m going to have to rebuild another project.