Some Unity things that should be packages, but aren't (yet?)

Will the following eventually be packages? If so, when can we expect them?

• Polybrush
• FBX Exporter
• Recorder

 

Everything besides the recorder is already in the stating branch of the package repository, so hopefully soon.

 

Yeah, it's all going to be packaged as the different teams get around to it. I'd like to add a list of things which should be in the package manager:

• The everything

 

Package manager in its current state is a broken mess of constant problems and messing about..

it works poorly if you have a bad connection, oh what's that your entire project cannot be fking loaded even though the packages it needs are already downloaded... nvm that the useless launcher said I could work offline.


it completely messes up if you have any sort of compile error meaning the rubbish gui part of it isn't even accessible nor does the menu show up, so you can't fix or remove any broken packages from the project via gui, meaning you have to go find and dig through the project folder to remove some package line from a json file.

and frankly the more stuff that gets thrown out of being built into the core unity editor and thus most likely to not be properly tested in combination with other unity core packages (with whatever testing unity do or do not do for releases) And with those added as a package will just mean even more shttt going wrong with projects for developers trying to juggle around various version of different parts... given unity's track record on getting something right in any meaningful time frame.. bug fix ready?.. wait another week for release etc.

the idea of sounded good, it was look Unreal Engine manages to put in a plugin system(heck they even put it in an area that makes sense.. unlike Unity lets dump a sub for it menu in the window menu. and lets move it around it, and lets not have it always be there for users. etc.. just a mess honestly and frankly should have been more polished before being thrown out beta user abuse.

My idea of it wasn't to gut out and lobotomize the F***ing the editor into everything is now a fking cloud package, our installer is now 100mb, but now you can have hours of fun picking packages from reading text with zero images and zero info really on a basic package gui, where things that used to be built in and part of editor you downloaded in one go.. yay.. enjoy future frustrations as our various departments all do there own things.. and you the user get to figure out how to make it all work together in your project.. just don't bother upgrading.. or do because you'll be forced too when package A no longer players nicely with Unity version B.. and package C just got a bad update which has F***ed package D.. and your project can't even be compiled..

I'm sure it won't be that bad.. oh nvm it already is, maybe it will get better in other 3months.

 

I mean I havent had a single issue you have talked about and have used 3 versions of it with 12 different unity installs so it might not be as bad as you think. Also please note that you can install the hub wrong just like any program. We had some of our developers here having issues and a clean + reinstall solved all.

Because this is beta software, I also would like to highlight something that the greater digital community seems to have forgotten more and more since early access became a concept:

Beta does not mean released. Beta does not mean finished. Most bugs in software are found and fixed via.....beta! So Yes it will have bugs, and the only way it will ever get released on time is if the community test it and report back.

So maybe try asking for some troubleshooting steps here before making a multi paragraph post filled with thinly veiled profanities, would be my professional advice. If that does not resolve it, actually post the symptoms of your bug in a way that most users do (and above all file a bug report and link the case number on the post).

 

2018.1 is out of beta.. however package manager is very much still in development and features.. is plenty of things about it that are just not how it should be if it was more fully developed and personally think it should have been more fully featured in design & ux beforehand.. otherwise its just gonna be like nuget which is S***..(only ok if you know what you want adding to a project.. otherwise its crap) its like the worst damn thing that somehow got picked up for installing packages, but as far as ux is garbage.. bare minimum amount of text that often barely describes a package, what it does, how it works, images nah.. not even direct links to help docs, source files, .. just MS quality garbage really... and that is something unity is inspired by? lets off load the problems of making sure everything works cohesively in a core editor, and hope end users using different combinations of packages report back with how it went.. great... i don't predict a mass exodus to UE but starting up Unity and having built in core things is actually a good thing.. the slowest thing about starting unity is actually teh damn launcher.. and with no project shortcut links made for a project that just get made automatically for end users to directly launch a project from the os/explorer etc for a version of unity it was working with last.. without even needing to go through the launcher at all would make that even less of an issue

It very much is as bad as I think it is, how long it remains this way is something I hope improves real fast. Personally though don't think it should even be out in 2018.1 in its current state.

And Unity's goal as mentioned in the blog post of gutting out the entire editor and features into packages in this current form and track record is just frankly scary. Unlike you I'm already experiencing a nasty side of using it.

And I have it's right here enjoy my experience: https://forum.unity.com/threads/garbage-manger-strikes-again-with-tmp-error.530704/