Im trying to figure out custom shader for UI Image and when I use Canvas template (which seems like is way to go) Im hitting issue with Z sorting - I was hoping it would use same sorting mechanism default Image uses but for some reason it does not - I suddenly have to set Pos Z in Rect transform to some value for it to be in front and to different value for Game view. Any way I can force that shader/material to use same sorting mechanism default Image without material is using?
#ShaderGraph - UI shader and Z order
vapid ridge
winter dune
Im trying to figure out custom shader for UI Image and when I use Canvas templat...
I believe it's supposed to be the same sorting, and other Canvas renderer features too
vapid ridge
I believe it's supposed to be the same sorting, and other Canvas renderer featur...
I would have thought so but no, as soon as I assign material with canvas based shader (even most simple one) it dissapears from order and I have to use positive Pos Z to bring it back :/
winter dune
I would have thought so but no, as soon as I assign material with canvas based s...
Which version are you on
vapid ridge
Which version are you on
6000.3.2f1
winter dune
6000.3.2f1
I would try do a quick test repro of the issue in a new project in 6.3. to try rule it out being project related, then in 6.0. to try to rule it out as 6.3. issue
Releases past 6.0. are very buggy as of yet
vapid ridge
I did tested in a new scene but ok I will test blank project as well tomorrow but I would prefer not to need to install another version - Im quite light on space so Im trying to keep only one.
Sigh, and somebody would thought LTS was supposed to be stable 🙂 
winter dune
I did tested in a new scene but ok I will test blank project as well tomorrow bu...
That seems to be a common belief but nowhere does it say that
LTS means it'll get updates for a long while
So it has time to become stabler than non-LTS releases
vapid ridge
That seems to be a common belief but nowhere does it say that
LTS means it'll ge...
Ok in new project it seems to work, it even works in my project in new scene if the sceene is what I open my project on but as soon as I open scene where I have issue with it it stops working even if I return to that new scene it works "in vacuum" - it no longer works there ... I have no idea why
winter dune
Ok in new project it seems to work, it even works in my project in new scene if ...
Seems to indicate there's some human error in the first scene's setup, but could be a bug in the scene just as well
Simple enough to move your objects into a new scene
If the problem follows with them, that would indicate the error is somewhere in the objects or how they're set up, rather than in the scene internally
vapid ridge
It will not be easy to untangle it seems but when I open different scene nothing should be retained from previous one but this bug somehow jumps from it to scene where it worked if I did not opened the one where it did not ... thats baffling
winter dune
The last loaded scene is retained in memory so it's technically possible a bug can still propagate from it
vapid ridge
I do think I know what is causing it to not work but Im not sure why yet and why it propagates outside its scene - on that scene where it does not work I have composition manager and use multiple cameras to render different parts ... without it it seems to work
_That will sadly require much more fidling than I can commit to atm :/ _
winter dune
Haven't ever seen that happen though, or bugs in scenes to begin with
vapid ridge
Im starting to have some idea why it leaks across scenes I suppose ... it seems it was component before but now its window ... Im confused ... I hope its not some depreacted feature again after some time I did not worked on this part of project ...
