A Unity ID allows you to buy and/or subscribe to Unity products and services, shop in the Asset Store and participate
in the Unity community.
Discussion in '5.3 Beta' started by Alex-Lian, Oct 7, 2015.
There have been some changes on the package import pathway that are documented here.
This will probably take some getting used to but overall it looks like good improvements.
I'm glad that some thought is being put into the asset update process. I have many assets (lost count but I think it's around 200) and I maintain a demo project for each that I update whenever the asset is updated.
With Unity 5 I've had a lot of problems updating the projects. I delete the relevant folders before importing the update but often run into an issue where string variable values in bundled demo scenes are set incorrectly. Like a string hash is being set instead of the actual string.
The only solution I've found so far is to set the project to hidden meta files and mixed asset serialization, delete the folders, exit unity and delete the project's library folder. Then I can import the updated asset correctly and reset the meta files and asset serialization settings for my SVN.
If I could make a suggestion (one I think I've seen before a few times), change it so that Unity categorizes any "Editor" subfolder below the "Plugins" folder as part of the "Plugins/Editor" project. In other words, make "Plugins/SomeAsset/Editor" compile in the FirstPass-Editor project. This would work well with the new path system because people could just move their assets into the Plugins folder, without having to manually go in and find all Editor subfolders first and move them all into new folders within Plugins/Editor, which seems to confuse the importer greatly if you ever need to update.
Already fixed for beta 2
Awesome! Same for StandardAssets?
Yes, "Editor" folders inside of "Plugins", "Standard Assets", "Pro Standard Assets", and "iPhone Standard Assets" should now work the same way regardless of whereabouts they are inside those folders. I believe the fix may have landed in 5.2.1p3 today as well.
Oh wow awesome; I was just used to it being this way for so long that I assumed it would never change. Glad I asked!
This is great news! Maybe I'll switch to 5.2 soon, then.
The changes are welcome! Right now we have many 0 bytes .cs files in our package to avoid trouble when the user is importing. I see that those problems will be solved with the "Re-Install" feature.
Although I think that the "smart" approach you are following will possibly not cover all the scenarios. I think it would be easier if you allowed us to have an autoexec.cs (or something similar) inside the package that enables executing code just before importing the package. Even better if you passed the installed version number to that autoexec. Right now we have to implement that, to allow user from all past versions of noesisGUI having a good update.
What happens if I move the package into Plugins folder. I split the editor scripts into the Editor folder manually.
I think that feature is great! I got a strange problem today though when importing LeapMotion through their custom package. It basically proposed to delete my whole project. Not really what I expected or wanted. I opened bug 736337 for that.
I really like the idea of an autoexec.cs that runs before importing the package.
It would also be useful to have a script that runs when you open the package. E.g., to show a popup window with important info BEFORE the user imports the package, giving them a chance to cancel if they want.
Maybe the autoexec.cs could serve this purpose if it's allowed to show a window and cancel the import.
One other thing: It would be good to move the Standard Assets so that they are all under the "Standard Assets" folder. For example, currently the editors for the Image Effects go under a root "Editor" folder instead of "Standard Assets/Editor" which means they actually compile in the wrong step.
My friend !, this was ridiculous ! I imported a package, and it was showing all my files in project to be "DELETED", so, I thought -Man ! this is really interesting, let me see; I Did a backup and imported the pack, the result is that ALL THE FILES was deleted, i mean, what is the purpose of this ?
Having the same issue wanted to import a package into an updated project (from 5.2) then when I went to reimport the package in 5.3 unity wants to delete all other files in the project that aren't part of the package? What is this crazy behaviour?
This behaviour is defined to handle the common case where people want to install an update to a package and do not have any other their own changes inside the package. This allows moved / deleted files to be cleaned from the destination package.
When you say 'all the files', do you mean all the files in the package folder? (yes, this is correct. If you dont want this, dont select it)
I can make the re-install option unchecked by default for entire project packages if you wish.
yes wkaj, thanks for answering, but why the manager was selecting all the other project files ? i did a test and it deleted all the project folder, more than 25GB data.
This dont happens anymore in latter betas like b6, thanks for fixing that.
Unity3D its a marvelous Game Engine! Thanks for the good work!