- User Since
- Dec 26 2013, 7:53 PM (165 w, 3 d)
Fri, Feb 24
This is caused by rB87cb3f8519: Since the length function always returns 31, fluid.memory_estimate has trailing zero bytes to bring it to length 31. These zeroes are preserved in the formatting step in properties_physics_fluid.py and therefore end up between the "MB" and the closing parenthesis, which then causes the C interface code to ignore everything after the "MB".
Please try running Blender from the console with the command:
blender.exe -b --python-expr 'import _cycles; print(_cycles.available_devices())'
Baking is working as designed. Since you're baking as a texture, you want Blender to stay in scene-referred values here.
Considering that the same build of Blender works on a different driver, I'm pretty sure that AMDGPU is to blame here, not Blender.
Wed, Feb 22
To be precise, the RGB numbers are in the Scene Linear colorspace, which with the default OCIO config is Linear sRGB aka Rec.709.
Mon, Feb 13
Sun, Feb 12
I'm merging this into the denoising branch now, and it looks pretty good so far. Three minor things noted inline.
Fri, Feb 10
Thu, Feb 9
Sat, Feb 4
I don't really agree that it should return a reflection - after all, it's explicitly called refract, not bounce_off_glass. So, when refracting isn't possible, the function shouldn't attempt to guess what you might want instead.
Another consideration is that you'll probably want to use fresnel weighting between reflection and refraction anyways, and in the case of TIR the refraction weight will be zero anyways.
Wed, Feb 1
Tue, Jan 31
Thanks for the report, but this bug is already known and fixed - unfortunately, it was fixed after 2.78a was released.
So, to get GPU rendering working you can either download a build from https://builder.blender.org/download/ or wait for 2.78b, which should be released sometime this week.
Jan 22 2017
This isn't a bug, SSS behaves exactly as it's supposed to.
Jan 20 2017
Hm, right, it was too spammy in headless mode - fixed now.
Jan 19 2017
Okay, the two issues you mentioned are fixed.
Jan 17 2017
Jan 16 2017
Jan 12 2017
Jan 4 2017
Yes, that's definitely a good idea - even if this was revived at some point, it would be a completely rewritten patch anyways.