Bug HDRP/Lit 2023.1.6 error communicating with the shader compiler process

Hello please check HDRP/Lit for errors in Unity 2023.1.6

Code (CSharp):

1. Shader error in 'HDRP/Lit': Internal error communicating with the shader compiler process.  Please report a bug including this shader and the editor log.

 

@aleksandrk ^^ for info only
cheers

 

will check the new release 2023.1.7 first and send a report later if still needed
the cryptic screen shot above for fog in transparent would produce pink in scene

not certain if its related yet and also need to check if custom shaders do the same or if its just unity Lit

 

@aleksandrk

thanks

for info today unity just released Unity 2022.3.7 (api 14.0.8)
they never backported changes in Unity 2022.3.6 (14.0.8) and lower within the same api (LTS)

PR Internal/2022.3/staging by UnityAljosha · Pull Request #7940 · Unity-Technologies/Graphics (github.com)


it would be good if you can reach out to whoever in unity is needed to mitigate this.

 

yes thank you
after checking and testing i found i could backport them to the same api in lower unity versions for that case.

i think this could be a good discission about "Users are expected to use the latest patch release of a particular version" as SRP aka URP HDRP runs more in api versions such as 14.0.8 more than they care about a unity version when a change is made in api 14.0.8 i felt that the expectation is that it should be applied in every version of unity that runs in that same api cycle.

example
api 14.0.4 = Unity 2022.2.0 thru 2022.2.2
api 14.0.5 = Unity 2022.2.3 thru 2022.2.4
api 14.0.6 = Unity 2022.2.5 thru 2022.2.13
api 14.0.7 = Unity 2022.2.21 thru 2022.3.3
api 14.0.8 = Unity 2022.3.4 thru 2022.3.7

so, if a change is only made in unity version 2022.3.7 then version 2022.3.4 thru 2022.3.6 running in the same api are subject to be different code resulting in users needing two variants for the same api

i think the view that the latest patch release is only to one particular version should also consider the versions within the same api cycle for any backporting. In the past Unity always bumped the api version up when changes were made however just starting in the last few months for the first time, we are starting to see changes without bumping the api up and generating more variants that conflict with the same api in lower versions.