Unity 2021 LTS Is Now Available

[YUTA-LEQUIOS]

@gmgannon

It appears that 2021.3 is not available as an option in Cloud Build. Is this going to be updated soon? Thanks.

2021.3.0f1 is now available for selection in Cloud Build.

[PutridEx]

@TropicalVoxel

Hey, I have a question. Hopefully it’s not offtopic, but does anyone know what happened to the forward renderer? I was following a tutorial before realizing I couldn’t find it. I tried googling it, too, but couldn’t find an answer as to why it was missing. Was it removed in 2021?? What’s the new equivalent to it? The screenshot below is where it would be- and the one below it is what I see.

You can switch between deferred and forward through your URP asset file, go to project settings > Quality > and look at what URP asset you’re currently using, click on it and it’ll select it for you in the content browser. There you can use the inspector to switch between renderers.

[DetroitBrian]

Hi everyone, thanks for flagging the Hub issues with the LTS release.

We just released a patch for Unity Hub. With Hub v3.1.2, the LTS tag is now applied to the 2021.3 LTS and the Editor version will now show up in the LTS category of the install flow. Get the new version here.

[atomicjoe]

@DetroitBrian

the LTS tag is now applied to the 2021.3 LTS

That’s great. What about my bug report about the editor constantly crashing and forgetting variables on Unity 2021 LTS though?
https://fogbugz.unity3d.com/default.asp?1420506

[Recon03]

@DetroitBrian

Hi everyone, thanks for flagging the Hub issues with the LTS release.

We just released a patch for Unity Hub. With Hub v3.1.2, the LTS tag is now applied to the 2021.3 LTS and the Editor version will now show up in the LTS category of the install flow. Get the new version here.

Thanks for the heads up

[LeonhardP]

@atomicjoe

That’s great. What about my bug report about the editor constantly crashing and forgetting variables on Unity 2021 LTS though?
https://fogbugz.unity3d.com/default.asp?1420506

It’s with QA and being processed. They will reach out to you via email if they have updates to share or follow-up questions.

@keeponshading

Shader Compiler is still broken in 2021.3.0 and 2021.3.1 LTS

This crash happens on all my DXR projects.

…
(Filename: Library/PackageCache/com.unity.render-pipelines.high-definition@12.1.6/Editor/BuildProcessors/HDRPPreprocessShaders.cs Line: 775)

d3d12: upload buffer was full! Waited for COPY queue for 0.001 ms.
Crash!!!

Have you submitted a bug report for this already? If not, could you please do that?

[LeonhardP]

@Vectorbox

Having installed Unity 2021.03.0f1 LTS and tested it with a copy of an existing 2D 2020.3.33f1 project, I found that the project’s sprite animations are not displayed and the relative custom inspector settings have been reset to zero.

Whilst I appreciate the fact that I can manually reset the many animations, I’d like to know what has caused this issue.

Could you please submit a bug report with a reproduction project so we can have a look?

[Vectorbox]

@LeonhardP

Could you please submit a bug report with a reproduction project so we can have a look?

Thank you for replying. I’ll submit a bug report and example project asap.

[keeponshading]

@LeonhardP

It’s with QA and being processed. They will reach out to you via email if they have updates to share or follow-up questions.

Have you submitted a bug report for this already? If not, could you please do that?

Sorry. In this case i cannot support this behaviour.
Investing more private and buisness time it s simply not possible.
Releasing an untested LTS version where you cannot build and operate the common Unity Github examples. SpaceshipDemo, Raytracing Examples… all of them.

The Shader Compiler issues are clearly visible in every of these projects.

The QA for the LTS is not done. Don t upload it to your users.

[keeponshading]

I strongly recommend to build an mid size real world project with mostly needed packages like Addressables before releasing an LTS.

Have a look in your auto bug report statistics since LTS release. This will give you an detailed report.

Alone from my side (different users) you should have received around 70 the last week since LTS release.

[iMer]

(coming from 2020 LTS)
The increased shader build times are extremely painful for testing… especially since it doesnt seem to cache any shader results when a build fails which is very easy due to URP using too many samplers in some configurations
Not quite sure how this passed QA or if QA doesn’t have enough say in this to block releases until its fixed… spending ~10 minutes on a Ryzen 3600/3900/4800 to figure out which URP/Lit variants to strip (not even building shaders! just filtering which ones to build! it seems to do this for every build!) just seems insane to me, it gets even worse since most project will be using more shaders. Its also single threaded btw, cause of course it is
“Forking” URP and other asset store shaders and editing shaders to remove variants you won’t use (have fun searching yourself which keywords do what for the more obscure ones) just doesnt seem like a good solution when everyone is expected to do this themselves

[kogi_rc]

@iMer

(coming from 2020 LTS)
The increased shader build times are extremely painful for testing… especially since it doesnt seem to cache any shader results when a build fails which is very easy due to URP using too many samplers in some configurations
Not quite sure how this passed QA or if QA doesn’t have enough say in this to block releases until its fixed… spending ~10 minutes on a Ryzen 3600/3900/4800 to figure out which URP/Lit variants to strip (not even building shaders! just filtering which ones to build! it seems to do this for every build!) just seems insane to me, it gets even worse since most project will be using more shaders. Its also single threaded btw, cause of course it is
“Forking” URP and other asset store shaders and editing shaders to remove variants you won’t use (have fun searching yourself which keywords do what for the more obscure ones) just doesnt seem like a good solution when everyone is expected to do this themselves

I see the same thing, build times jumped from 4 minutes to 20-30 minutes with progress bar being stuck at 99% for most of the time. Also tried 2021.3.1, same thing.

I don’t know how shader cache works because it registers cache hits:

Compiling shader “Universal Render Pipeline/Simple Lit” pass “ForwardLit” (vp)
120 / 13824 variants left after stripping, processed in 1.11 seconds
starting compilation…
finished in 0.00 seconds. Local cache hits 120 (0.07s CPU time), remote cache hits 0 (0.00s CPU time), compiled 0 variants (0.00s CPU time), skipped 0 variants

Warm cache is 25 minutes build and cold cache (deleted Library folder) takes 35+ minutes. It used to be 4 minutes in 2021.1. Something has changed for the worse and no amount of “you’re using too many shader variables and quality settings, causing too many variants” responses explains this behavior to me. It used to work fine in previous version, it is nearly unusable now.

[altepTest]

They forgot to add some flags inside the editor. It did this long process just one time. then was faster. if now it does this every time is just some option that was not properly set when building the editor

[YegorStepanov]

Small URP 2D-project with no custom shaders:

2020 LTS: 10-15 seconds
2021 LTS: 60-90 seconds

[ImpossibleRobert]

The incredible shader processing times are the exact and only reason why I am stuck with 2021.1.28 2022.1.b16 is still the same and even slightly worse. I really hope that topic is worked on at Unity with very high priority.

[keeponshading]

@iMer

(coming from 2020 LTS)
The increased shader build times are extremely painful for testing… especially since it doesnt seem to cache any shader results when a build fails which is very easy due to URP using too many samplers in some configurations
Not quite sure how this passed QA or if QA doesn’t have enough say in this to block releases until its fixed… spending ~10 minutes on a Ryzen 3600/3900/4800 to figure out which URP/Lit variants to strip (not even building shaders! just filtering which ones to build! it seems to do this for every build!) just seems insane to me, it gets even worse since most project will be using more shaders. Its also single threaded btw, cause of course it is
“Forking” URP and other asset store shaders and editing shaders to remove variants you won’t use (have fun searching yourself which keywords do what for the more obscure ones) just doesnt seem like a good solution when everyone is expected to do this themselves

enabling debug mode in buid player setting double or tripples the compile times even further.
so average experience:
10 to 20 min before 2021.2.15
2h to 3h after
6h to 8h when debug enabled

[Damien-Mayance]

I’m having a major regression with this LTS…

The EventSystem changed its behaviour regarding IPointerEvent handlers and it’s breaking the whole game.

(details here: EventSystem unexpecteldy calling IPointerExit in 2021.3.1f1 )

[keeponshading]

This Memory Leak is also common in all mx DX12 projects…
Editor crash after 5 to 10min working depending on project.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.

d3d12: releasing a resource which is still being referenced. It will be leaked.
d3d12: swapchain present failed (887a0005).
d3d12: swapchain present failed (887a0005).
Device removed reason (887a0006).
GfxDevice was not out of Local memory
Local memory usage:
Budget: 24725422080
CurrentUsage: 19692695552
AvailableForReservation: 67108864
CurrentReservation: 12496928768
GfxDevice was not out of Non-Local memory
Non-Local memory usage:
Budget: 67739316224
CurrentUsage: 762687488
AvailableForReservation: 0
CurrentReservation: 34003875840
Set -force-d3d12-debug for more information on device removal
d3d12 : CreateCommittedResource ‘BufferD3D12::CreateBufferResource() Buffer’ (384 x 1) format 0 failed (887a0005).
Device Remove Reason (HRESULT): 0x887a0006
Device Memory Stats:
Local AvailableForReservation: 11918 MB, Budget: 23580 MB, CurrentUsage: 18780 MB, CurrentReservation: 64 MB
Non-local AvailableForReservation: 32428 MB, Budget: 64601 MB, CurrentUsage: 727 MB, CurrentReservation: 0 MB
d3d12: CreateResource for buffer failed.
d3d12: failed to create a buffer of size 384
d3d12 : CreateCommittedResource ‘BufferD3D12::CreateBufferResource() Buffer’ (48 x 1) format 0 failed (887a0005).
Device Remove Reason (HRESULT): 0x887a0006
Device Memory Stats:
Local AvailableForReservation: 11918 MB, Budget: 23580 MB, CurrentUsage: 18780 MB, CurrentReservation: 64 MB
Non-local AvailableForReservation: 32428 MB, Budget: 64601 MB, CurrentUsage: 727 MB, CurrentReservation: 0 MB
d3d12: CreateResource for buffer failed.
d3d12: failed to create a buffer of size 48
BufferD3D12 : Unexpected null accessor on Buffer
Crash!!!

[keeponshading]

When i build my scene with Unity 2021.3.x LTS and start them
i get in DX11 Mode ~43fps

start /D .\HDPhotostudio_Bakery_2021_DX12 UI.exe -screen-fullscreen 0 -popupwindow -screen-width 2880 -screen-height 900 -monitor 1 -screen-quality High -window-mode exclusive -single-instance -force-d3d11

i get in DX12 Mode ~9fps

start /D .\HDPhotostudio_Bakery_2021_DX12 UI.exe -screen-fullscreen 0 -popupwindow -screen-width 2880 -screen-height 900 -monitor 1 -screen-quality High -window-mode exclusive -single-instance -force-d3d12

When could we finally use DX12 without loosing up to 75% of the framerate?

This behaviour is known since more than 2 years…

Why is DX12 so much slower than DX11?

For my project, DX12 seems to be much much slower than DX11. Any clue as to what would cause this? DX12: [5559982--573025--upload_2020-3-6_12-35-29.png] DX11: [5559982--573028--upload_2020-3-6_12-35-50.png]

[altepTest]

can you try verifying if your windows version have all the updates, and you have all the GPUs drivers (both intel and nvidia/amd) up to date? Also the chipsets and motherboards and all.

there is quite a chance that if you don’t have them up to date some functionality may not work correctly.

for example the unreal nanite will not work on windows versions that are not up to date if you use directx. it works if one use vulkan.

so the same system can use the GPU power just fine if you use vulkan but will fail on directx if the windows version is not up to date.

I suspect this may be the case at least in part, with unity struggling with directx12.

by uptodate I mean having windows 11