Every time I download a new version of Unity (recently LTS 6000.0.24f1) and when I whant to create a new project, Unity Hub set Editor Version to an old version I have in my PC (2022.3.23f1). The information is in small at the top of the screen, exactly at the opposite of the “Create project” button. So every time I miss it and I create the project on the wrong version. Why do you remove the arrow next to “New project” and the previous “Preferred version” ? Or maybe add possibility to add a popup to avoid this problem ? It’s really frustrating.
The “Create Project” version defaults to the most recent LTS version.
I suppose there hasn’t been a Unity Hub update since 10 days ago when Unity 6 LTS was released for the first time. Current version is Hub 3.9.1. Maybe 3.9.2 will make Unity 6 the default choice.
I just updated to 3.12.1 and it still defaults to an older version. I’m trying to go through the Unity Learn tutorials with version 6000.1.0f1 (I am a noob) and I have to remember to change it every time. Seems like this option was perhaps available at one time because I’ve found guidance on how to change it, but that guidance is no longer valid.
Creating a new project will default to the latest LTS version and that still is 6.0 not 6.1. The 6.1 and 6.2 releases are “supported updates” but not LTS versions.
Yes, I’ve seen the explanation of how it currently works several times. It’s my opinion that this is annoying. Especially true when the option to set your preferred default previously existed and was later removed. It looks like folks have been bringing this up for years.
I saw one thread where the ‘official’ response was essentially “give me a reason why you need this”. Mine is, I have a preferred version to go on this learning journey with and the tutorials have me creating multiple projects, so I find it annoying to have to remember to change the version. (as an aside, why is the version selection all the way at the top? I would expect it to be closer to the other project properties)
Seems simple to have the option of creating a preference and in the absence of such a declared preference, perform the current behavior. Perhaps even prompt the user after installing each new editor to remind them of their choice and ask if they’d like to switch.
Let’s see… probably a nullable string?
string? preferredVersion = // load from configuration
if(preferredVersion == null) // assign most recent available LTS version
else //assign preferredVersion
There you go! Feel free to copy my pseudo code and fill in the blanks. Invert the logic if you prefer. You’ll just need a new config value to hold the preference and a simple UI feature that allows the setting and clearing of preference based on available editor installs. Bonus points if you store it on the user’s account and use that to recommend learning courses but that’s being way extra.