- User Since
- Nov 28 2009, 10:22 PM (378 w, 1 d)
Seems something went wrong with compilation of numpy. Did a fresh git clone of numpy, checked out to v1.10.1 branch (currently official version we bundle) and the issue is now gone.
Fri, Feb 24
Thanks for the report, but the issue was already solved in latest Git version, which you can get from builder.blender.org.
Thu, Feb 23
Woops, my bad. Mixed with other reports :S
The noise is coming from caustics i think. Usually using Filter Glossy will help, but it has no effect on Sharp distribution. Doing something like D2416 will help here.
@Dalai Felinto (dfelinto), is it something simple for you to have a quick look at? :)
Does this issue happen with the fixed build: http://download.blender.org/release/Blender2.78/blender-2.78b-OSX_10.6-x86_64-fixed.zip ?
This is not relevant to GPU or CPU, you'll have such behavior in all render modes.
Wed, Feb 22
There you find few builds with various patches applied: http://download.blender.org/ftp/sergey/tmp/T49465/
It's same as the other report I'll merge it to that one. Please follow the discussion in T49465.
Ok, ignoring the crash report. For the future discussion please follow the issues which are related on CL_INVALID_BUILD_OPTIONS only. All other issues are to be reported separately.
This is more a feature request than a design discussion, which we do not accept here in the tracker.
Please fill in all requested information in the bug submission form.
Uh, fglrx was discontinued..
Please grab latest build from builder.blender.org and run it with --debug-cycles command line argument. Attach the output as a file here.
Mon, Feb 20
Ah, you're right. We use mediawiki template for the link which adds T (which i always forget). Fixed now!
This issue slipped into 2.78b but it is fixed in current git. Will be ported to 2.78c which is planned tomorrow.
I am not convinced at all we should expose such things. Those are fully internal guts and exposing them must not be done as-is. I'm also not convinced with the reasoning you gave. There are following issues:
Can see two cases here. First one is the bevel not being orthogonal in the first case. This is caused by the bevel object rotated according to the curve twist, which is currently set to Minimal Twist. Using Z-Up with some manual control over the bottom CV will fix this issue.
Sun, Feb 19
Try removing ~/.cache/cycles to see whether driver fails to restore OpenCL kernel from a binary dump.
Fri, Feb 17
Main questions here are: