Thu, Dec 6
If I change the render layer in the compositing tab to sceneB and then back to sceneA, it works as it should in 2.8.
However, if I then save the file and open it again the same problem occurs until I update the node again.
Wed, Dec 5
Mon, Dec 3
Sun, Dec 2
This is a limitation of Cryptomatte. While it does produce accurate masks, it does not have the information to separate colors this way. For that something like Deep EXR would be needed.
Fri, Nov 23
Change the value of CMP_NODE_DISTANCE_TRANSFORM from 323 to 324. 323 was used for CMP_NODE_CRYPTOMATTE.
Wed, Nov 21
assigning to @Brecht Van Lommel (brecht) then
Tue, Nov 20
Technically, @Brecht Van Lommel (brecht) is the boss of render pipeline.
Can confirm this.
Mon, Nov 19
Sat, Nov 17
Mon, Nov 12
I am utterly sorry if this was the wrong place, I didnt see it as a feature request.
My bad! Thank you for doing what you do!
That's indeed a limitation. We don't use this tracker to handle such feature or improvement requests though:
Nov 9 2018
Agree it could skip writing if the Composite node is removed (or has nothing linked), and that making it do that would be a To Do.
Agree this is a little weak.
It is not a bug though, it is still working as intended.
Not having a Compositing output Node used to complain and refuse to render, but that rule was softened in the fix for T35269.
Nov 7 2018
Working around it would be easier if the dilate/erode node had an input for step value.
I guess this is known limitation of the compositor (but I am not sure).
Workaround is (as you said) to first do the erosion first, then the scaling.
Nov 5 2018
Nov 3 2018
Rebased on the latest master.
Nov 1 2018
Sep 28 2018
Sep 27 2018
Sep 24 2018
Sep 23 2018
Tried undoing some changes done in snode_set_context() but no success so far. @Lukas Stockner (lukasstockner97) this falls on your desk am afraid. ;)
Bisecting points to rB4cf7fc3b3a4d032f0c0db632a46d40806e906cf1 as breaking commit. Not sure what went wrong there, that is rather large commit :/
Confirmed, would guess something went wrong in the update notifiers…
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
@Sergey Sharybin (sergey), I guess that one is for you? ;)
Sep 22 2018
It does work when you are using the Defocus Node, using the Z-Buffer of the current scene. Could be that this is the only node that does actually trigger a render update, but then the Auto Render button would be quite misleading indeed.
Sep 17 2018
It’s not saved because there is no data at all (as can be checked with a viewer node), for both volume passes, when Save Buffer is enabled. @Brecht Van Lommel (brecht), guess that one is for you?
Sep 14 2018
Sep 12 2018
Thank you! As usual I can help with testing.
If new color management will not get into 2.8, this will surely make it more flexible.
Thanks for the report, but this is a known limitation. One day we would need to implement more proper color management and such for file output (including manual saving from the editor, render output, nodes...). For until then considering it a TODO.
Sounds more like a TODO and/or known limitation, @Sergey Sharybin (sergey)? Also, do not see anything specific to 2.8, afaik 2.7 does not have that option either.
Sep 6 2018
This is interesting, for sure. I'm not sure that in a typical compositing workflow if it would be extremely useful, but from the examples posted, it certainly looks like you can do some very artsy, creative stuff with it.
Sep 3 2018
Thanks guys :)
This is indeed a feature request, that is planned to be solved in the future with overrides in 2.8. The other thing is that we should add support for a world position pass at some point.
Well, this is like trying to simulate data pass with a light setup, which is already kind of weird. So probably this is something to look at as well.