Not entirely sure if this is a bug, but it’s certainly not behaving as I would expect.
I’m working on an image effect shader but my results on the graph versus the results being ouput by the shader are inconsistent. See the following gif to get an idea of what’s going on here:
Occasionally the effect will “catch” in the output and I’ll see the proper results of the glitch effect on my rendering cam, however it only catches a frame or two, behaving as if essentially frozen for around 10 seconds before reverting back to it’s un-glitched state. (The editor itself isn’t locking up, it’s still as responsive as ever with the preview in the sampler node running at a consistent framerate.)
I have a few sub-groups of effects in this shader, everything else works perfectly fine. But as soon as I plug this one into the pipeline it breaks the output. Not sure if it’s worth mentioning but if I plug a different sub-group into the frag, save, then plug this one back in, the Main Preview window will render it properly. Until I save. Then that locks up as well, as seen above.
I’m using URP, in case that’s relevant. Does anyone have the slightest idea what’s going on here?
Been messing around with this for a couple hours but still can’t figure out what the issue is. I have been occasionally getting these errors spit into my console but I have no clue whether or not it’s tied to the problem I’m facing. Using Unity 2022.1
Incompatible keyword states```
I set this one aside and have been working on a couple new image effect shaders and am experiencing what I presume is a related issue. Occasionally I’ll have a sub-group of nodes that cause the output to fail to update at a consistent rate unless I interact with the editor (e.g. click inside the game tab, for example.) I.e. the output becomes quite sluggish in its updates, grabbing a frame here and there instead of fluidly playing the animation. To ensure this wasn’t some kind of blit problem I pushed these sub-groups into their own regular old URP Lit/Unlit shaders, the problem persists.
After getting frustrated I pulled open Unity 2020.3 and rebuilt the shaders in that version. They work perfectly. So this seems to be a problem specifically in the 2022 version of shader graph. Which I’ve submitted a bug report for. (Edit: Although maybe this is a URP problem, I have no idea I haven’t tested that yet.)
Edit #2: Alright, I’ve tested this in 2021.3.4f1 URP and it works perfectly fine here as well, so this is probably specific to 2022.
So this thread probably belongs over in the 2022 forum instead. If a moderator wants to move this over there, please feel free.