Happens with a new shader in a project that is empty except for shader forge for me... here's a video:

Same here, still the same in 1.21. Sorry Joachim!

Thanks Joachim!

Any progress on this? Still happens in 1.20. You can't use the RGB to HSV outputs because of this. :)
Thanks!

Happy to report this is fixed in the 5.2.0p1 patch release. It was on their side. :)

Here's an example video. Sorry about the choppiness - my old MBP was struggling to record the screen and run the editor at the same time. Also notice the console error message (no stack trace):

Sorry to bring it up again, but in a published build the shader works fine. I think Unity changed something in the way the game window reports its scene UVs to you in the editor, because the problem is only when playing in the editor. I know they changed they way the game preview window works somewhat, so the problem is probably there. But my SceneColor / Scene UVs behave erratically when playing in the editor - the offset is different depending on how you resize the game window.

Here are some different size game window examples:

Maximized:


My standard game res:


Half-res:

Sorry about that, after investigating further I think it has something to do with my replacement sprite shader, which I also can't open. But if I use the default sprite material, everything is not shifted. Anxious for 1.19... is there any way to get an early dll with the fix? :)

Hmm I can't really open the shader in question due to the code node + 5.2 issue. It's possible that if I can open the shader and re-save it, Unity will display it correctly. I'll try making one from scratch.

+1. Careful if deciding to update to Unity 5.2 (which is now public), because you can't really open/edit any shaders with a code node.