There needs to be a way to copy components and game objects from one instance of Unity into another. The “Select Dependencies and Export Package” method is a lousy way of doing things. It should be as simple as pushing copy and then paste. Don’t tell me any other reason why this shouldn’t be a thing. It should also be done without any missing scripts! I also want to be able to drag it gracefully from one open editor of Unity into another without any problems.
What is unity supposed to do in situation when you’re copying an object that relies on scripts that are not present in the target unity instance?
3 Likes
You heard him. Without any problems.
Now, you might assume “just copy all the dependencies.” Then you wonder, what if those things already exist in the target project? Or what if they exist, but with different GUID .meta files? Or what if other things with the same name exist but have different features? Or what if the copied object refers to addressables, or has Asset Path strings? Or what if the target project has a different licensing seat context? Or what if …
6 Likes
Yeeees, and this is why I asked that question…
Well put.
If only there was an already existing manner in which to transfer assets from one project to another…
Oh yes, that’s right, it’s called packages.
2 Likes
Anything’s possible… in the world of MAGIC!
2 Likes
@JGameMaker92 it seems from all recent threads popping up, that you just really need to follow some tutorials on unity. All the stuff you are asking for so far either is not well thought out at all, or already exists.
Stop complaining about random unnecessary features and actually learn to use the engine - its much more fun that way and you actually get something done.
lol now the other ranting thread has some context.
You have to know at least 1% of what you are doing. You can’t just push buttons and expect things to work.
When you “Select all Dependencies” and export them as a package you usually end up getting a lot of other useless files from other assets you have imported into your project tied into it. It’s just a mess sometimes. I don’t think it’s an unreasonable feature to ask for things to be a little more smooth and streamlined when copying between Unity projects.
2 Likes
You have to write your code in such a way that useless things are not dependent on each other.
Lol what. ‘Dependencies’, you know, means something that something else is dependant on. They’re not useless.
Once again it feels like your projects need an organisational overhaul.
Based off of his feedback from the other thread I’m inclined to believe it’s much more severe than we’re thinking and that he may need to just start over with most if not all of his code. It feels very much like he’s trying to build Dwarf Fortress with just the knowledge he got from Roll-a-Ball.
2 Likes
Agree! There can be many time consuming and not always accurate options to choose.
This should be simpler. It’s annoying to be ticking off things that are obviously not connected in any way to the prefab I’m trying to save. Things like Camera options/Fullscreen etc or even character controllers (!) or skyboxes or other prefabs or assets not even vaguely associated with the prefab. Fair enough that you have a choice but it’s not a helpful method or an intuitive one in any way.
1 Like
You are doing it wrong.
- Select the prefab in your project and choose “Select Dependencies”
- that will select all the actual files required
- with those selected, right-click and select “Export Package”
- in the export window DESELECT “include dependencies”
That will create a package with minimum requires to run the prefab.
This method works. If it doesn’t work, the problem is your architecture. Or a really messy project. You will need to clean stuff up, and as others pointed out, spend more time learning the proper way to do things. Moving stuff between project is very simple, as long as you doing things correctly.
3 Likes
“Include Dependencies” is a mess, I know it has been indicated in many other threads too. A lot of the times it’s very easy to miss certain scripts, or get too many junk files from other assets. Ya’ll are acting like you’ve never had a missing file reference in your projects before lol. But yeah it can cause the Prefab Editor to not agree with you on just about anything and you try to save your Prefab and it’ll just simply tell you that you cannot save it.
1 Like
I usually make a new folder, move the assets I want to export to that folder, then export that folder. Now in the project I import it into, everything is in that folder and I can move it to the proper place while not having a nest of crap everywhere.
You say that but then you only link to your own thread…
It’s not “a mess”, you just don’t understand what you are doing or your project is a mess. That other thread was closed because it was largely nonsense.
Closing this one too.
Before starting any new threads in the wrong places, go the Learn section of the Unity site and start going through the tutorials. Doing things wrong and then complaining the tool is no way to get a game built
https://unity.com/learn
1 Like