I'll committed a modified version of this.
I think it was only for TH_NODE because that is also the node background color, so the header is made a bit darker than that.
The same file being open so many times is definitely a bug.
See the other report, cause is known but solution is not so simple.
This option and associated code should be removed. It was only supported by Blender internal which is no longer available.
That render time difference is really quite odd.
The error message sounds like file handles are leaking, or at least an unexpectedly high number being open. The maximum number of open files on Windows is lower than other platforms by default, so this would be noticed quicker on Windows.
When committing this, please see the notes from:
We need a .blend file to investigate the issue though, ideally simplified as much as possible to remove things that do not affect the bug.
Cycles: OpenCL on macOS has been disabled
There was a growing payload of bugs in Cycles related on OpenCL on macOS
platform, and those issues were caused by a compiler bug, which we have no
Surely, it is sometimes possible to work compiler bugs around from a
source, but we are facing some of the issues which are not solvable in this
way. Also, such solutions are usually short-living,. since adding more
features are often kicking compiler to provide buggy binary again.
In this case compiler will not get fixed since Apple decided to discontinue
OpenCL on its platform.
So the decision was made to drop support of OpenCL, keep official features
of Blender stable and predictable, and focus on things we have control over.
P.S. Older Blender releases are always available. Surely, this sounds like
using an ancient software without neat features. But we can't push Cycles
OpenCL on macOS measurably beyond that anyway.
Please specify the operating system and graphics card used, as well as the exact Blender version tested.
Please provide all information requested in the bug submission form.
.blend files were uploaded to the new wiki now, links are working again.
Mon, Feb 18
The original purpose of pixel size is retina screens, where everything is scaled up exactly 2x.
Sun, Feb 17
Please create one report per bug.
I don't think we decided to drop support for these cards yet, will keep the report open until we either fix or decide to drop support for them.
- Please attach a .blend file to reproduce the problem.
- Please mention if you are using CPU or GPU rendering.
For user feedback, please see here for the right place to post it:
For feature requests or design proposal, please see here for the right places to post them:
The properties editor only works on a single active object, not multiple objects. There is T54862: Multi-Object Properties Editing to make that possible, but the current behavior is intentional.
The outliner does not take into account settings that are specific to one 3D viewport, that is by design.
Sat, Feb 16
Fri, Feb 15
Re-opening, I used the wrong task number in the commit.
There's a bug report in T50831: Texture Paint 'Bleed' is angled along UV edges about those spikes. Some kind of pixel space bleeding to figure out how far to bleed would avoid them.
Looks good to me now.
This is how it always been implemented, my patch does not influence menu title positioning.
Right, it's just a consequence of the patch that the title is now at the bottom most of the time instead of the top. Which I think is acceptable, but it's a slight downside.
Also for the commit message, no need to mention that it reverts some specific commit. That commit was two years ago, it's just a change by itself.
Fine with me, but we should test this on Windows before committing still.
Putting the enum menu title at the bottom is a bit odd, but seems fine to me anyway.
If we hide instance and render visibility by default, I think we should still communicate to the users when these settings are off. When instance visibility is off we can replace the viewport visibility icon as we do already.
For future reference, there's a few things in this commit message not following the guidelines:
Thu, Feb 14
- Fix mixed space/tabs indentation.
- Fix Python memory leak.
- Show cleaner terminal output.
- Refactoring string parameter passing a little.
Thanks for the suggestion, but this is outside the scope of the bug tracker. It's more for the user feedback forum:
Thanks for spotting that, fix in rB9886ae63311d: Fix T61470: incorrect saturation clamping in recent bugfix..