Vegetation shadow casting in LTS - won't fix?

Unity Engine
, ,
1

I’m very surprised to notice that alpha clipped shadows in builds, will not be fixed in U2022.3 LTS.

It can’t really be an LTS version, if we will be unable to actually build and ship any games with this version. It’s not an edge case, since a huge percentage of games have some kind of alpha clipped surfaces (for example trees, foliage, grass and more).

Can somebody from Unity please give some clarity about the decision to ignore this bug and to potentially condemn 2022.3 LTS completely? It would be easier to swallow the Won’t Fix status if there was a clear a robust work-around described… but there isn’t… it literally just says Won’t Fix with no explanation.

Unity Issue Tracker - Shadows alpha clipping is ignored and shadows rendered without details in Player (unity3d.com)

3 Likes
2

let’s hope that this is not an emerging pattern to migrate all users to 2023 LTS aka “the new terms” asap…

3

For a long time, I don’t know what the actual meaning behind LTS is. More appropriate (and valid) is Lasting Technical Stumbles.

1 Like
4

Since this is a new week and I’m feeling optimistic, I’m reviving this thread just one more time :wink:

I’m hoping that somebody from the Unity team will be able just to clarify this situation? To recap - the bug is marked as Won’t Fix, which means that it’s not feasible to do any release builds with 2022.3 LTS and it won’t ever be feasible.

The only possible way the bug can remain unfixed for 2022.3 LTS, is if we had an official work-around, which we don’t :face_with_spiral_eyes:

3 Likes
5

This seems like a really big oversight.

1 Like
6

That you for raising this again.
I took a look and I can indeed still see the issues in the latest 2022.3LTS, but not with latest 2023.3.0a12. So, a fix or change that fixed the issue landed in between and needs to be backported, the bug case has been falsely closed, I will reopen it.

5 Likes
7

do you have any PR numbers for what was changed so we can look closer at making any workarounds

8

It is not obvious to my eyes, but some devs comment in our internal bug tracker suspect that this commit fixed the issue : https://github.com/Unity-Technologies/Graphics/commit/397ab285d55ceab87d57673d5a96374c761d77fe