The Python module indeed always starts with "factory settings" by design. This is what you would normally expect from a programming API I think.
Removed sentry-cli from the svn libs, doesn't seem easily build-able, platform maintainer will just needs to obtain it him/her self have it in the system path
There's a more extensive patch for this in D3539.
We still need to update the libs in the studio, will be done soon. But seems no bug in Blender itself.
Thanks for the report but there is no information in here. If you think you found a bug, please fill in all the requested information. If this is a user support question, try one of the community websites:
Please follow the bug reporting template and provide all the requested information:
We can only investigate this if a .blend file is provided though, the dump does not give us enough information.
Thanks for the report, but any issues with the Renderman addon should be reported to them, since we the Blender projects does not maintain it:
Sun, Sep 16
For OpenCL no extra work is needed, the kernels are compiled at runtime.
I guess you built Cycles standalone yourself. Did you configure CMake to build CUDA binaries, and if so wat are the relevant CMake variables set to?
Sat, Sep 15
Possible solutions are:
- Upgrade your 10.8 installation to a newer macOS version.
- Replace principled volume with a custom volume shader with volume scatter and absorption nodes.
- If you believe the crash is a bug (and not due to running out of memory), report it with a .blend file attached so we can investigate.
Fri, Sep 14
Ok, thanks for testing, I don't think there is anything we can do here on the Blender side.
I don't really have the time to debug a complex shader like this, and it's not obvious that the bug is in Cycles. You really need to narrow it down more.
Seems generally fine.
It would have been good to discuss in advance the strategies to reduce memory. It's certainly an interesting experiment to see how much room for memory optimization there is, 30% is a great result.
Great to see this tackled!
Also seems downgrading both libdrm and openc-amd works for some people :
See T56791 for a newer task on this error, let's continue there.
- Running clinfo from the command line and seeing if it works.
- Try for example LuxMark to verify if your OpenCL installation is working at all: http://www.luxmark.info/
- Uninstalling all non-AMD OpenCL installations (e.g. pocl, beignet) to ensure they don't interfere.
- Installing the Pro driver from the AMD website, since this is not a consumer card.
Thu, Sep 13
Mainly posting this for Campbell to review the overall approach, if this is somehow breaking the application templates design.
Wed, Sep 12
Thread 0 and thread 21 seems to be calling locale functions at the same time, from copy-on-write depsgraph code.
The dopesheet header has a bunch of options to filter what is shown, did you check if anything there is accidentally enabled?
I couldn't reproduce the crash on macOS.
This appears to have been a temporary issue that was solved in rB8f1027a58b50: Fix Cycles issue moving versioning to blenloader, the next build will work again.
I added the missing requests module, and with the new bundled SSL version it all appears to be working now.
Please specify which graphics card you are using.
- Try running Blender from the terminal, are there any errors shown?
- For CUDA support you may need to install a CUDA package for your Linux distribution, though if Cycles is missing entirely that's not likely the problem.
- Are you using the build from builder.blender.org/download or another one?
The change was done almost a month ago, you must have already updated your repository since then.
This was an intentional change:
Tue, Sep 11
So I guess this means:
- Each tool only shows the matching brushes in the list.
- If no matching brush exists, it will use some kind of default brush settings or automatically create a brush.
- Shortcut keys would be bound to tools, but not to brushes.
- Quickly switching between brushes within a tool would need some other mechanism, or is not considered very important.
I'm not sure about this, why can't we have both brush and other tools in the toolbar?
This will be fixed now in the latest daily builds after rBcd5db907261e: Build Environment: updates for macOS..
Ok, for feature requests see:
I suspect it's another case like T56739, which Linux Mint version are you using?
For questions on how to use Blender, please use one of the community website:
Mon, Sep 10
I will commit it.
I didn't review the whole patch, just some higher level comments.
Looks quite good, some comments.
Changing unit settings in the render does affect the render, unless perhaps you are using an addon or importer that takes them into account. It only affects the display and editing of values in the UI.
Right, I suspect this is happening due issues with an older version of OpenColorIO, which the Linux studio builds and macOS buildbot are still using. The Linux buildbot on the other hand was upgraded and so would not have the bug, if my theory is right.