Unity Visibility changes for preview packages in 2020.1

Why not hiding them from the main view but still allow searching? It's clear from other packaging hosting solutions that a plain list won't scale.

How will we discover these packages?

 

I agree with @capyvara, and I'm not convinced by the idea of getting updated from a newsletter.
Why not just create a new category (called "Experimental Packages" or something else) to make a distinction with Preview Packages ?

 

Just showing my support for that idea, that makes things way clearer about whether or not it is an "experimental" package or a "preview" (closer to released state) package.

But I have one question/request: for installed "experimental" packages, will it still show when there is an update for it? This is extremely helpful as many of those packages (including Entities one) does not have a dedicated thread for new releases announcement (so I, and probably many more people, rely on the Packages Manager to know when there is a new version to try).

 

Wow I use multiple of these and wonder now a bit. Thanks about the transparency. One feedback to the editorcoroutines: I use it permanently and would just slap a version 1 label on it to be honest. I never had a single issue.

 

Please consider to replace blamed preview label with worldwide used stage labels (alpha, beta, rc) so we will know how far package from release

And please add prototype label for packages in list above and option in package manager to see them, not your "great" idea to manually modify manifest

 

That's a fairly important distinction you just glossed over.

It would be nice to say which ones are abandoned and which ones might just take a while longer to mature.

The other problem here is what happens when you add a new package to this list? Where's the single canonical URL I can visit to see all the packages that are available but currently hidden?

 

@LeonhardP, thanks for the information. How you achieve this? By introducing a new field to the package.json or it's something magical happens inside the UPM.

 

Don't want to reject this idea without knowing precisely what solution you plan to offer, but at the moment I can't see any good reason to not take advantage of the package manager. Why spend time to create another tool or scatter packages informations in different places ?

About the risk of confusion, what about addding a "Show experimental packages" (or "Show prototype packages") inside the Advanced menu of the package, disabled by default, and each time user enable it you display a dialogue pop up explaining precisely the nature of these packages and asking a validation from the user. You think it wouldn't be enough ?

 

So basically DOTS is not coming in 2020.

IIRC, it was promised in the Unite Roadmap talk to come out of preview this year.
Now it is removed from the package manager...

 

I totally understand the need to do this and I support this decision. No sarcasm. I don't wanna see not-ready-to-use packages in the manager which confuses me and others working with me. Like AAA games need to be ready to play on release day without major bugs, Unity packages must be included in the Unity experience when they are "almost" ready.

 

For most of the packages I kind of get why they're being hidden from the package manager but I did not expect to see

com.unity.vectorgraphics

in the list. I've been using it without many troubles throughout Unity 2018 & 2019. Vector Graphics are used in the UI Builder as well.
Is this because there is no development going on in this package?
I consider this package as quite usable but also a must for crisp UI on any resolution which SVG is designed for.

Having to edit the manifest manually to add these packages is a step backwards. I'd rather be able to see these not ready packages as being marked as something else than preview. Like "Experimental" or "Alpha"

 

So, no DOTS in 2020 LTS?!

 

Actually, this decision infuriates me. This is why we can't have nice things. Always the bending over backwards for the lowest possible common denominators.

Because of a handful of people cannot decide for themselves to use or not use clearly tagged packages we cannot have them accessible in the editor by default.

Thank you people, I hope you know who you are.

I'm seriously pissed off by this.

 

Better package filters would be a better solution than removing packages from the package manager.

There is a massive difference between a package coming in year or two or three and those that are not being developed anymore. People using packages that are no longer being developed should be made aware of this in a clear way.

It would be much clearer if packages being developed were rated as prototype, alpha, and beta rather than preview. The packages that are no longer developed should be marked as obsolete or deprecated and removed from the package manager and the package repository after giving people using them time to transition to a suitable replacement.

 

This was already the case and people still enabled it and then got angry/frustrated that the preview packages aren't finished, stable, or working as they thought it should. In 2020.1 and 2020.2 they added extra steps to enable preview packages. Maybe that's not enough and this other solution will help

 

Not helping anybody!
I really hope Unity reconsider and undo this.

Having modal warnings/confirmation every time we try to install, and flags to display preview and abandoned would be good enough.

Someone suggested color codes (green for verified, yellow for preview, red for abandoned), I support that.

 

This is why preview is not good spelling. It do not have understandable meaning. Prototype is mutch better. And if Unity add alpha, beta, rc and release stages like for UnityEngine itself then community will be notified than package even not reach alpha state yet.

For now we have many packages labeled as preview that is actually in beta or rc state.
We have use Entities package that is maximum in alpha stage and have no problems with it at all.

The only good thing from Unity I see is idea to label packages plans to support nearest future LTS. But solution for this label is ugly. I think good way for this can be just separate field in manifest with planned release date or release Unity Version

 

Wouldn't it be so much easier to just add an "Show experimental packages" checkbox somewhere (maybe even hidden so just people that know what they're doing edit it and no beginner can accidentally activate it) or - even easier - display a warning like "This is an experimental package with a high chance to change in future and break your project. Are you sure you want to install it?" that has to be actively accepted before installation.

Removing it from the Package Manager is no good idea imo and will slow me down. I don't want to check some other sources when it should be right where it is now. And I use quite a few of the packages like DOTS, Hybrid Renderer and what belongs to them.

@LeonhardP If that's really what you're going to do, will the packages then at least be updateable via Package Manager when they're already added to the manifest? Otherwise this change will really suck and is a major inconvenience.

 

Why add the qualifier "that are actively looking for feedback"? Why not list all packages that are hidden in the package manager?

If you want to actively deprecate some then say so. You imply that there will be packages that are a) hidden from the store b) hidden from your off-app list. Surely that's as close to deprecated as you can get!

 

The problem was caused by multiple definitions of the word "experimental". Unity had hobby projects that had been mostly abandoned mixed together with packages that were part of a major strategic initiative.

However I think this is an overreaction and a way of avoiding clear communication about each package's prospects and status.

 

On a certain level I'm already using package manager like this. I browse Github repos for interesting stuff and often the install instructions are just "add the Git url manually to your manifest" There's already repos on the Unity account I use this way.

But what bothers me about this is the lack of clarity over why packages have been demoted in this way and what future plans there are for each one.

 

Have been following the DOTS forum has been a long time and I can confirm that the issue is not due the word "preview" neither due to the lack of clear communication. The issue is that a lot of people just see those packages in the package manager and downloads it right away without even reading the landing page of the documentation (which becomes the main issue of a lot of help requested in the forums, even though there are pinned posts too with the documentation link).

Well, even for packages not in the package manager (like the DOTS VS) I see people complaining about the instability, even though it is stated clearly as far from production-ready. So I agree with the idea of making those packages not accessible directly from the editor, but also would like another way to find those or at least get notified when a new package/new version is available to try.

 

This would have been a lot simpler if:

1. you dropped the nonsense naming and called alpha, beta etc what it is for packages
2. stopped marketing unfinished or outright abandonned packages in unite talks, videos etc
3. stopped pushing DOTS like it will fix and save the world when really its for certain things and certainly not ready for majority of uses and is in serious flux all the time


Ultimately doesnt matter, developers who want access to these can manually add them to a manifest but it still seems like a weird way of doing things.

Just admitting "these X packages are no longer developed BTW" would have been nice too, right now people still dont know what is what on that list.

 

I agree with Alpha, Beta and RC labels. Unity uses them in other areas already, so users should be able to understand and these are standard terminology in software development.

However, I would use "Experimental" rather than "Prototype". Mostly because "Experimental" is used in several Unity areas already, but also because other engines use "Experimental". So we all speak one language when we jump between engines.

Spoiler

https://www.unrealengine.com/en-US/blog/experimental-early-access-and-beta-features-in-unreal-engine

 

I just noticed that some of the packages that listed as being hidden from the package manager are listed as verified packages in the 2020.1:

com.unity.assetbundlebrowser
com.unity.editorcoroutines
com.unity.mathematics
com.unity.multiplayer-hlapi -- obsolete
com.unity.render-pipelines.lightweight -- replaced with URP
com.unity.test-framework
com.unity.xr.arcore
com.unity.xr.arkit
com.unity.xr.arkit-face-tracking
com.unity.xr.legacyinputhelpers
com.unity.xr.oculus
com.unity.xr.windowsmr
com.unity.xr.magicleap
com.unity.xr.arsubsystems
com.unity.xr.interactionsubsystems

Are these no longer under active development? Why are they in both categories?

 

What? Why?

The Package Manager already has the ability to add external sources. What is the benefit of ignoring that and fragmenting things further with yet another way to get stuff?

I propose that instead the default Assets/Packages/manifest.json have an optional line:

Code (csharp):

1. "com.unity.modules.experimental": "1.0.0"

People who want to use that stuff can add it to the Package Manager and then access it in the unified approach you're trying to standardise.

 

I would prefer better wording instead of simply hiding the preview packages. For example, use words like pre-alpha, alpha, beta, release candidate, etc. The word "preview" could mean nearly anything. If Unity added more details, I would know to treat "pre-alpha preview" differently than "release candidate preview".

 

That is great news, I didn't know it was possible at all.

 

Why not just leave the packages where they already are but label them better? For example, instead of calling all of those packages "preview", you could use more descriptive words like pre-alpha, alpha, beta, release candidate, etc.

 

Also, it would help game developers if we knew the status of various packages. This list indicates that Unity will be hiding some DOTS, networking, and XR packages. Some transparency about the actual status of each package would help more than hiding packages. For example, does Unity consider DOTS to be pre-alpha, alpha, beta, release candidate, or something else? This would be very helpful when deciding whether or not to use DOTS in game projects. Simply calling it "preview" does not give game developers enough information.

With VR, Unity 2019.4 has some text saying we should switch to the XR packages because other VR packages (Oculus Desktop and OpenVR) are getting removed in Unity 2020. However, this thread indicates the XR packages are being removed in Unity 2020. That is inconsistent. What is the real status of those packages? Which VR/XR package should be used by game developers in Unity 2019 and 2020? In my own testing with Unity 2019.4, the Oculus Desktop package seemed stable, and the XR packages seemed completely busted.

 

Yes, but since they'll now be hidden, it'll be difficult to discover these packages in the first place if you didn't know about them before.
A lot of them work perfectly fine and can be pretty useful. I've been using editor coroutines for a while, but if they were hidden, and I couldn't see them in the package list, I'd spend some time working on a sub-par approach, not knowing there's already a perfectly fine solution at our disposal.
The new input system also worked more or less fine a year before it went out of the 'preview' phase.

Will users have to regularly browse Unity's git repository to discover these packages?

I'm also for better labelling – while still being able to see the full list of experimental packages in Unity somewhere.

 

Another difference is that we can't just see and follow the removed packages status and history unless we ADD it to the project.

It's good to be able to browe packages to see what's on the horizon and the progress of it all.

 

EXACTLY.



Honestly, this is just appalling.

Unity... You are going backwards.
You know how racing games usually have that "turn around" warning / notification?
GET ONE.
Because you seriously need it.

If you continue with this terrible decision, you will have essentially slapped everyone using one of the listed packages above in the face.
Not to mention you won't actually be solving the problem. All you did was just move it far, far away. But it's still there.

Instead of making people's lives harder (seriously though... How did you even consider this as a "solution"?), how about you pick three (count 'em Unity, THREE) amazing ideas from this thread -- integrate them -- and then pat yourself on the back for a job well done, and we all act like this never happened.

Capeesh?

 

They pick the current idea from another thread, they did go overboard though. Basically they are trying to stabilize the workflow for people who aren't tinkerer and got suck due to bad signaling. SO they move away the package into a place where the tinkerer would go on their own, BUT tinkerer like the ease of use, so they aren't please by the new workflow imposed on them, many have pointed they just need a sort of toggle somewhere BUT stay inside the editor.

They probably should focus on that, have a switch tuck in an obscure place, which is easy to toggle once you learn about it, and still come with many signal to tell you are in a special unsafe mode.

 

For the love of god no!

Sure, remove the packages that are no longer under development, it makes sense we don't want to start using them, but just move preview packages to another tab or leave it like it is. This just makes it harder to go find preview packages!

 

If the people you're thanking are not all Unity employees, then there's something wrong with your logic.

 

I personally don't see the big deal. I just had to press a plus button and type in the package name. That's not much. I preffered the old way, but this way it does draw more of a line in the sand, and maybe it will push package developers to get it over the line and become legit. And maybe it gives more clarity to users, that some of this stuff is going to require some effort and patience.

 

I agree with you that adding it manually is not a big deal. It is an effective way to make sure that advanced users (who are willing to deal with breaking changes and bugs) are the ones testing / using these packages. That being said I think Unity needs to clarify which packages are in active development and which are not. Additionally an improved labeling scheme on these packages in the package manager (even if they have to be added manually) would go a long way in clearing up what the status of a package is.

I think that adding a experimental section to Unity Hub that contains these packages (and a way to add them to one of your projects) would be a fine place to manage these packages. This section would not appear unless a user enabled a check box buried in the Unity Hub settings under the advanced tab. This would also allow Unity to include DOTS templates in the package manager for advanced users.

 

There is also a discovery problem, where do you have the LIST of all assets and follow their news? peaking the package manager was a shorthand.

 

Fair point. They do seem to be indicating that they will develop some kind of system for the cool beta users to keep up to date with this stuff. Then of course these beta packages could be considered a sort of entities.

What is concerning me now is that in the 2D Animation package, do i have to use Photoshop, or not, because they make a pretty BIG deal about this PSB format, but this is not the right forum for that.

 

Or just have a "Show deprecated packages" option similar to the existing "Show preview packages", under Advanced and defaulted to off. And like someone mentioned above, hit it up with some red warning colours and dire looking fonts or something to emphasise the point.

It's ridiculous of Unity to go to these overly cumbersome efforts to hide packages and make them harder for experienced devs to find and include just because of a few imbeciles who couldn't read the "preview" label and got themselves in a muddle. It's as ludicrous a state of affairs as how every coffee container these days has to have "WARNING: CONTENTS HOT" labels on them, in case - y'know - some potentially litigious cafe customer somehow wasn't aware of what might get spilled on their pants.

 

I don't know if you noticed, but that "Show preview packages" option is also gone...

 

It's not gone, it's been moved to the project settings window

 

Yep I did see that. A change for the worse IMO.

 

Keep shooting yourself in the foot Unity.