Unity Unity 2019 LTS Is Now Available

Thank you, I was really looking forward the LTS release!

Spoiler

 

Cool! Is there like a changelog between 2018.4.X and 2019.4.0? For deprecations etc.

Nevermind, just found this site:
https://docs.unity3d.com/2019.4/Documentation/Manual/WhatsNew2019.html

 

Nice! Does that also mean that 2020.1 is coming out of beta soon?

 

Quick question - starting with Unity 2020 there will only be two TECH Releases per year.
What will the LTS release look like then when it comes to version numbers? 2020.3 or 2020.4?

 

^ Lucky guess 2020.3 LTS

 

I have been sticking with 2019.2 for LWRP, but now that my favorite post processing supports URP I think I should give another try. Is the upgrade/crossgrade path easier now? Any suggestions other than https://docs.unity3d.com/Packages/c...universal@8.0/manual/upgrade-lwrp-to-urp.html to consider.

 

Is the Input System verified for 2019 LTS or will be verified in the near future? If it's still preview, doesn't that mean that due to the removal of the resolution/rebinding dialog there is no way to rebind keys without third party assets?

I guess I'm fine with using Input System in preview since it seems so close to completion but it'll be great if it could get officially verified too.

Edit: Seems to be out of preview but not verified yet: https://docs.unity3d.com/Manual/pack-safe.html

 

@LeonhardP I totally missed this announcement because it wasn't posted to the LTS announcement feed! Will that feed discontinue now or was this simply a minor oversight?

 

Me too, I hope they will add it later to that thread, it was very helpful for me for the past releases

 

Thanks, good to know to stay in the 7.x family for LTS (I didn't get that from first read though).

Follow up question is, the guide is directions to go from 2019.2 and lower to 2019.3 to upgrade to URP. Should I follow those directions and then upgrade from 2019.3 to 2019.4 LTS or can I go direct from 2019.2 to 2019.4 LTS. (One path seems safer, but on my laptop will be several hours more watching the upgraders run ).

 

Am I the only one that does not understand why packages made by unity are tied to an engine version? I would have thought that new versions of URP could be ported to unity 2019.4 LTS with ease because its a stable base.

 

That was explained already in other posts across the forum and the TL;DR; version is that there are things that rely on the engine's native code, thus requiring a new engine version.

 

Perfect! Was just wondering when the lts was coming out, lol.

 

2019.4 still has this issue. I just came by. and felt like posting a report.
https://forum.unity.com/threads/req...itor-asynchttpclient-done-state-int32.203318/
> Request error (error):
> UnityEditor.AsyncHTTPClient: Done(State, Int32)
Quick Fix: disable Preferences -> General -> Show Asset Store Search Hits

 

Great news, just curious will 2019.4 show different available package versions for download under the package manager.
Eg: URP: 7.2, 7.1.... etc or just show only one version 7.2 verified
like in the few newer tech version of 2019.3 released

 

Two strange things going on here:

1. The date of the first post is June 1. But 2019 LTS didn't go live until June 9.

2. This thread will be closed to new replies on June 22. Why disallow continued discussion in this thread after only about two weeks? Usually version announcement threads stay open until a new release supersedes the older thread.

 

The post has been created earlier / prepared and made visible to users on LTS release date.

 

Unity 2019.3.15 was stable, Unity 2019.4 is a crash fest, it must be so bad that bug reports cannot be submitted because I and a few others have been trying all day. Bug reporter is getting frozen at 61% and just does nothing, even when the report is just crash logs. So for anyone thinking that this version is an improvement over the 2019.3 branch it is not yet.

 

You could try to use the Unity Hub Bug-Reporter, perhaps this one works:

 

Yeah that's not working either, getting a "Something went wrong" message and I hit Retry and nothing.

 

Right.

So, why did we need a package manager system then? What’s the benefit?

 

Oh been trying install 2019.4 from the morning, gave it up after the hub crashed a couple of times, Unity you should make progression bar for Unity HUB with percentage; seeing couple of the post here I'm going back to non LTS which looks to be stable than the non-lts lol; now I've removed 2019.3.7 want to know is there any more stabler version than 2019.3.7 and supports multiversion packages in package manager like 2019.3.7 (eg: URP 7.2.0, 7.2.1 etc)
would have shifted back to Unreal for desktop game, if not for the Asset Store and the Assets I've purchased, hope

 

Okay, back on topic.

Who thought it was a good idea to release an LTS version with tvOS support effectively broken (controllers don’t work properly)? How was that not a blocker and how does that not undermine the notion of LTS being higher quality, reliable software?

 

This wouldn't happen to be related to the horrible input lag I am getting when CPU usage is high?

(I let go of mouse/keyboard and GetKey/GetAxis/GetAxisRaw still register input regardless of gravity/sensitivity/snap settings, only started since upgrading to 2019.4.0f1 LTS)

 

So now that the 2019 LTS is released, when does the 2017 LTS lose support/get removed from Unity Hub?

 

2017.4.40f1 was the last LTS release:
https://forum.unity.com/threads/unity-lts-release-announcements.529171/page-2#post-5870182

Unity Technologies no longer maintains/updates 2017 and in that sense, the supported ended, if that's what you asked.

You can continue to use 2017 as long as it works for you. However, if Android/iOS/etc for example introduce new guidelines, that are not covered by 2017, you most likely have to update to a newer version, as 2017 receives no more updates.

 

Okay. I was just curious if the 2017 LTS was going to remain on Unity Hub since the 2019 LTS was released.

 

I've just jumped from 2018.3.8f1+ and things look very bad for me right now.

 

May I ask why the resolution dialog was removed from the player settings in 2019.4? I have quality levels but now I'm confused how players are supposed to select their quality level before they get ingame?

 

Please see the following thread, where it's discussed:
https://forum.unity.com/threads/whats-the-resolution-dialog-replacement.762551/

 

Hi there,

I upgraded my project from 2019.3.0 to this recent release, hoping to have some of the bugs present in that previous release fixed - but I ran into a larger issue. After spending a couple of days trying to troubleshoot, I'm not sure where else to about this.

Unity crashes when it's importing my prefabs. It spends around 2 hours importing everything else just fine, and many prefabs are actually imported successfully. But a lot of the prefabs (specifically, prefabs that may have been modified or created in 2019.3.0) crash it on import. Unity just flat out stops working, and as such doesn't produce a log with any helpful information. The last line in the editor.log is just that it starts to import the prefab, and then it crashes.

In an incredibly slow process I continually launched Unity after crashing on import, since it eventually would process all of them. I did get in-editor, but they were all reduced to dummy assets because they crashed the last time the engine tried to import them. Re-importing them caused the engine to crash again.

So far, in my testing:

I've found that I can open a new 2019.4 project, and copy/paste my prefabs into there. It imports them just fine, granted, they're missing their scripts & such.
Copying these correctly imported prefabs back into my main project doesn't fix the problem, it crashes on re-importing those.

I attempted to delete the library folder (backed up the previous one) and had it re-import everything (another two hours) and it crashed upon reaching the first prefab yet again.

So after having it completely re-import everything a second time and still fail, here I am. Not sure what to do. I can link some of the prefabs, perhaps? Send over the logs that I have?

Please help.

 

Hi Seth, I've spent my day doing the same steps thinking the library folder was the culprit. I'm in the process of recalculating my games library folder before moving ahead with an upgrade. Perhaps this may be helpful to try too.

My guess is things arent cleaned up, I've seen this as a common issue with unity. Several folders are filled with old data, for example: Umbracache(occlusion data) files I found 30gigs in my library yesterday!

 

The project certainly would benefit from a cleaning, but I don't think that would fix it. I know which prefabs it is unable to import, but I'm just not sure what I can do to fix them.

 

I'll see what I can do.

 

So, it occurred to me as I was rereading the blog post about 2019.4.
It uses the URP, while my project was started back in 2018 and uses the built-in.

I don't suppose that might have something to do with why I'm having difficulties importing a lot of my prefabs?
Would upgrading to URP in 2019.3 before moving to 2019.4 have helped?

 

Well, deleting my library folder inside the game folder and recompiling it before I migrated worked like a charm.

 

2019.4.0f1 Crashed when launch with an empty project

[Subsystems] No new subsystems found in resolved package list.
[Package Manager] Done registering packages in 0.00s seconds
Refreshing native plugins compatible for Editor in 0.04 ms, found 0 plugins.
Preloading 0 native plugins for Editor in 0.00 ms.
IsTimeToCheckForNewEditor: Update time 1592227416 current 1592270905
Initialize engine version: 2019.4.0f1 (ca4bfb872f47)
[Subsystems] Discovering subsystems at path D:/Program Files/Unity Editors/Hub/Editor/2019.4.0f1/Editor/Data/Resources/UnitySubsystems
[Subsystems] Discovering subsystems at path D:/XXXXX
GfxDevice: creating device client; threaded=1
Direct3D:
Version: Direct3D 11.0 [level 11.1]
Renderer: NVIDIA GeForce GTX 1660 Ti
Vendor:
VRAM: 5991 MB
Driver: XXXXX
Initialize mono
Mono path[0] = 'D:/Program Files/Unity Editors/Hub/Editor/2019.4.0f1/Editor/Data/Managed'
Mono path[1] = 'D:/Program Files/Unity Editors/Hub/Editor/2019.4.0f1/Editor/Data/MonoBleedingEdge/lib/mono/unityjit'
Mono config path = 'D:/Program Files/Unity Editors/Hub/Editor/2019.4.0f1/Editor/Data/MonoBleedingEdge/etc'
Using monoOptions --debugger-agent=transport=dt_socket,embedding=1,server=y,suspend=n,address=127.0.0.1:56516
ImportWorker Server TCP listen port: 50738
Begin MonoManager ReloadAssembly
Stacktrace:
at <unknown> <0xffffffff>
at (wrapper managed-to-native) System.IO.MonoIO.FindFirstFile (char*,string&,int&,int&) [0x0002f] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.MonoIO.FindFirstFile (string,string&,int&,int&) [0x00014] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.FileSystemEnumerableIterator`1<TSource_REF>.AddSearchableDirsToStack (System.IO.Directory/SearchData) [0x00028] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.FileSystemEnumerableIterator`1<TSource_REF>.MoveNext () [0x00095] in <437ba245d8404784b9fbab9b439ac908>:0
at System.Collections.Generic.List`1<T_REF>..ctor (System.Collections.Generic.IEnumerable`1<T_REF>) [0x00078] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.Directory.InternalGetFileDirectoryNames (string,string,string,bool,bool,System.IO.SearchOption,bool) [0x0000f] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.Directory.InternalGetFiles (string,string,System.IO.SearchOption) [0x00007] in <437ba245d8404784b9fbab9b439ac908>:0
at System.IO.Directory.GetFiles (string,string,System.IO.SearchOption) [0x0003b] in <437ba245d8404784b9fbab9b439ac908>:0
at UnityEditor.Modules.ModuleManager.LoadLegacyExtensionsFromIvyFiles () [0x000ae] in <23cedefa295047eea2d08a34071111a5>:0
at UnityEditor.Modules.ModuleManager.RegisterPackageManager () [0x00021] in <23cedefa295047eea2d08a34071111a5>:0
at UnityEditor.Modules.ModuleManager.InitializeModuleManager () [0x0000d] in <23cedefa295047eea2d08a34071111a5>:0
at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) [0x0001f] in <437ba245d8404784b9fbab9b439ac908>:0
=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================