that’s bad sign, never have i seen so many errors in urp8
what i did here is reimport the faulty vfxgraph, that didn’t fix anything
- Unhelpful and inflammatory post title
- No detail about Unity version or package versions
Quality post. 
Are you looking for help or just venting? May I suggest Twitter is more suitable for the latter?
Hi!
Which versions are you using?
That error message reminds me of something that was recently fixed. When using a “Position (Depth)” operator, or any other that uses camera buffers, in URP 2021.2 you can get that error.
I agree that the message might be misleading (like I said I believe that was fixed), but the root of the problem is using those operators in URP; they are not supported yet.
https://docs.unity3d.com/Packages/com.unity.visualeffectgraph@12.1/manual/Operator-Position(Depth).html
I hope that helps!
You’re good! yep it was urp 2021.2
I see there is a .1 release, I’ll install that, thank you!
Now I’m wondering if urp 8.3 was ignoring or adding the node in the conversion to compute shader. If it added unsupported access to the depth buffer, do you think that could cause “MMU fault” faulting unity: Texture Cache on a Switch?
When that compilation error is not present it will just sample from a default gray texture.
It should not cause any kind of crash in any platform, but I can’t confirm if that is currently the case, sorry.
Please use descriptive topic titles as it will be taken more seriously going forward.
you know what, you both are right that title is too incendiary and no longer applies, changed.
Good to know it handles it safely, I’ll look elsewhere then.
I know that providing clear error messages is not easy but if you could ping the faulty node when we click the error message that’ll help, especially in the heat of release.