- User Since
- Dec 26 2013, 7:53 PM (290 w, 4 d)
Some info on what I have found so far:
Sat, Jul 20
Thu, Jul 18
Sun, Jul 7
Fri, Jul 5
Jun 13 2019
Jun 12 2019
As far as I can tell, this issue is somewhat misleading - at first glance it appears to be a color management issue, but what actually happens is that enabling the Gradient option disables the Color Picker controls. Note that by toggling the Gradient checkbox, you can swap which of the two colors appears dull and that the Color Swap button changes along with the colors.
Already fixed by rBfb03f50e069d.
Jun 7 2019
Jun 6 2019
Jun 5 2019
Jun 1 2019
Add a missing call to initialize the CurveMapping and change the random parameter to be a percentage.
May 29 2019
May 23 2019
May 20 2019
May 19 2019
Update for formatting.
May 17 2019
Rebase to current master, added support for automatically translating picked values into names
May 11 2019
Another rebase to get to the newwest master, also squashed to a single commit now.
- Rebase patch to latest master
- Fix merge issues caused by formatting commits
- Adapt the fix for T60973 to the new baking implementation
- Fix two bugs in render_result_from_bake: In the case where the object_id doesn't match, the code was doing a real cast instead of a bitwise cast to -1 and didn't increment to the next pixel
May 10 2019
Update to latest master (and therefore clang-format), no functional changes.
May 9 2019
May 7 2019
Apr 9 2019
I'm just going ahead and updating this with my fix, the history should still be there so we could go back to your fix.
Apr 6 2019
Mar 27 2019
Mar 18 2019
Mar 17 2019
Mar 14 2019
Mar 8 2019
Updated to latest 2.8
Feb 26 2019
@Ludvik Koutny (rawalanche) Good point about baking multiple objects - to be honest, I'm not really sure why I just removed it in the first place, it was broken in the previous version of the patch but fixing it wasn't hard.
Obsolete, we have proper Cryptomatte support now.
- Baking multiple objects at once by selecting them is supported again
- The progress bar works as expected now
- The margin filling of a pass doesn't overwrite results of previous passes anymore
Feb 23 2019
@Ludvik Koutny (rawalanche):
Roughness should be supported in master already, the others aren't though.
This patch does not add any new types, but with it we can easily add them in the future without touching Blender's code or worrying about bitflags (adding roughness took up the last available bit, so now's the time for an overhaul, similar the the RenderPasses a while back).
I also just pushed the updated version to the experimental buildbot, builds should be up soon at https://builder.blender.org/download/experimental/ (check the date, should be Feb 25th).
I've made some improvements and fixes to the code.
Feb 22 2019
Updated to latest master.
Or rather, manually transferred the changes to latest master - turns out that almost a year of 2.8 development is kinda tricky to merge.
Feb 19 2019
Feb 18 2019
Feb 12 2019
Feb 5 2019
Regarding integrating the Cycles denoiser into the Compositor node: I'm not sure how we would implement that - the animation denoiser patch adds support for standalone denoising, but we'd still need to call that from Blender somehow, and adding a function to the Renderer API specifically for that seems far from ideal as well.
Feb 2 2019
Jan 25 2019
Rebase to current 2.8 master.
Jan 18 2019
Dec 13 2018
Can you try running blender with the arguments -b --debug-cycles --python-expr "import _cycles; print(_cycles.available_devices())" from the command line and posting the output here?
Dec 9 2018
Dec 8 2018
Dec 7 2018
I can reproduce the problem, I'll have a look.
I think you forgot to attach the file?
Dec 6 2018
Rebased to current master, still works fine as far as I can tell.
Dec 4 2018
Nov 30 2018
Nov 29 2018
Nov 28 2018
Thanks for the patch, this looks really good!