-
**For the love of anything, prioritize the fix (or internal workaround) for your breaking “Validation Failed” bug **, where Unity QA finally admitted it’s a Unity bug due to
sudo-promptafter years of letting people believe it’s their own fault by ignoring years of threads regarding this same issue [EDIT: Seems like a pending fix! Thanks @judesidloski ] -
If you are going to bloat the headers with things no one wants, at least allow us to hide/show what we want to see: Allow me to hide your proprietary collab and cloud stuff.
-
Allow me to resize the header bar: I have a bunch of projects, so they are nested and organized deep. All of my project paths are
c:/users/myUsername/repos/and… that’s it
-
Allow me to hover over a path to see the full path as a tooltip.
-
Do not opt us into your cloud services by default. Sure, show a tooltip when we first add a project to opt in if you want to push it, but don’t just attach it as if’s the obvious choice.
-
Often, we need to match projects 1:1 - even LTS patches. Let us download specific versions via an “Archive” tab – don’t lazily link us to a website to dig, often defeating the purpose of Hub. At least for the latest LTS! I know Unity doesn’t eat their own dogfood so they probably don’t know that most folks collaborating prefer to use the same exact ver for numerous reasons, not limited to being able to bypass updating scripts to your ver each launch.
-
When creating a new project, give us an option for just an “Empty Project” – it gets confusing what’s the “most empty” when I literally want nothing inside (eg: To wrap an embedded SDK for package testing – or to simply test importing certain things – or for any other reason). Not 2d, not 3d, not URP, just call it “Empty Project” with a (Not Recommended) option, if need, for the newbs.
-
Detect if I already have Visual Studio 2022 in any form and uncheck it by default – you’re causing issues! You’re not checking enough forms. I don’t know how you’re checking it, but perhaps use
dotnet- I bet there’s a way to check what VS is installed. Prevent issues before they happen. -
Add CLI call to accept “lts” as version like most others do (and defaulting to lts if version is left out): This is the universal standard for things like this.
3 Likes
I’d like to add one detailing #8 a bit closer:
- Even if I don’t have it; don’t check Visual Studio Community 2022 by default if it has been unchecked in a previous install operation. Have it remember the last user setting like all other modules please (e.g. hub remembers fine whether I desire WebGL and Android or not, but holy cow I must have more interrupted/trashed/accidental Visual Studio Community installs in my closet than Blender artists have deleted default cubes in theirs)
Rider and VS Pro / Enterprise users will thank you!!!
3 Likes
Can it also become much faster and less ram hungry?
1 Like