I create a prefab in Project A, then I start project B and go: “Ohhhh, that prefab would be great in this new project” so I go to project A and select the prefab and , as per usual, Unity decides to build me an asset containing absolutely every single file in my project.
Doesn’t matter if I click on a folder or a file, my export brings up every single file in the project…
WTF!?!?
Obviously we are going to have one or two very smart people who are going to suggest that I have 'Include dependencies" selected so before you think me a complete idiot, let me explain my latest attempt:
I have a game object with 0 components. it is the parent of another game object that contains:
Elipsoid particle emitter and Particle Renderer and nothing else…
So I click on it and hit the asset export option and it brings up a box with 300 Audio files, 460 Textures, 80 scripts, models etc etc etc… 95% of which are in Resources folders and not linked to anything that could make them “dependencies”. Hell, it even includes my scenes!
After raging for a bit, I found an obvious and simple work-around that should work for most situations.
Example:
If you want to export your playerPrefab, right click on it and select dependencies.
Right-click again and export package.
Uncheck include dependencies.
This should give the same results that you would get before Unity 4.(i.e. wont’ include all scripts automatically)
“Yes, but this is intended.
If exported object uses at least one script, all will be shown as dependencies, because in that script you might be using other ones and by default we want you not to lose any dependencies.”
Wow, seriously?? At least have a check box to include all scripts instead of forcing it. This is a horrible solution. I realize proper source control is ideal for multiple people working on different parts of a project, but it was quite manageable with the old export system. This new “feature” is going to overwrite files that have nothing to do with what’s being exported/changed.
This is a lazy and dangerous “fix” to something that wasn’t broken.
Confirmed. It is completely useless. (for exporting anything with a script on it , or a scene file)
Selecting and de-selecting dependencies does not help.
I have a scene with only models. absolutely no scripts. I select the scene export… it includes everything in the whole project, so try un-select dependencies… it removes the whole project except the scene file. absolutely useless.
You cant even batch select and de-select items in the file list, (which would be of great help)… or the check-boxes should work as a hierarchy so its easy to switch off entire folders.
Definitely a major item that should be fixed in Unity.
BUT, it does work to export a prefab and or models, as long as it doesn’t have any scripts on it.