Well, these artifacts are not exactly the problem of the blender or cycles. This is a common artifact of all simple geometric tracing algorithms.
I know for a fact that Redshift doesn’t do it.
1 Like
Papercut:
There’s no UN-crease menu option? 
I had to google how to remove creases in 2.8 since I rarely use them. I thought 2.8 would have made that option easily-accessible by now… but it’s still buried.
To be fair, being able to control the amount of the crease is nice and great for the user to discover (once he googles it), but this should be a visible “Edge-Marking” tool on the shelf that lets you mark edges as sharp or creased etc. (if you want the user to happily discover why there is no “uncrease” option when there clearly IS a “crease” option…)
4 Likes
You cannot use empty in edit mode.
Also, it is used in object mode very often.
3D cursor is a great tool, that replaces any kind of pivots in any kind of operations.
But it is nice if someone have possibility not to use it.
2 Likes
“New Scene,” should be created with default startup file settings
Currently when a new scene is created from scratch, it loads all the default settings that launch with Blender, meaning Cycles GPU performance settings are reset, as well as render window preferences and other things.
I know that I can create a new scene using “copy settings,” but sometimes there are certain things that I actually do want to change from scene to scene.
I’ve already told Blender what I want my “default,” to be when I created a custom startup file, so it would be nice (if not expected) if Blender could create new scenes with my default settings instead of the ones that come with Blender.
EDIT: For some clarification, my startup file is working fine when I open up blender. The issue is that when I add a new scene using the “new scene,” button in the top right corner of the screen it the new scene starts off with factory defaults instead of my default startup file.
2 Likes
Cancel button missing for baking / generating point caches
Please consider adding a cancel button to bring the baking and generation progress in line with the rendering progress in the statusbar.
Problem:
Progress bar for generating point caches is missing a cancel button / cancel UI element.
Solution:
Add a cancel button as used in the render progress bar
Examples:
with UI element to cancel the task
without UI element, can be canceled via pressing ESC only
9 Likes
Dropdown triangle in Properties > Physics > Dynamic paint need a bit of spacing
Problem:
The dropdown triangle UI element in the canvas or cache list of dynamic paint is very close to the lists content. Therefore making it hard to see and understand that it reveils a seach / filter function.
Solution:
Add a few pixel more top spacing in order to bring it in line with the top & bottom spacing of the other drop down triangles. As show in the following example:
Alternative options for the UI layout:
- Add an additional toggle button to show / hide the filter on the right below the add / remove buttons.
- Add some more space to the list view in general. Two lines would be enough to let it breath a bit more.
2 Likes
And maybe give it more room by default…
1 Like
Both Edge Rail and Boundary are options for the inset tool where remembering them comes in handy. Thus I propose to expose them in the Active Tool and Workspace Settings in the Properties Panel.
Here is a patch that implements it:
https://developer.blender.org/D5534
2 Likes
Render Region should be in Viewport Shading 
5 Likes
Here are proposals about global functions in outliner for heavyweight (~1000 collections) setups.
A) Normal state - initial state of outliner
B) Ability to use ctrl+LMB outliner isolation as toggle, with restoring previous global state.
First ctrl+LMB press remembers inital state of scene visibility, and isolates collection, second - restores previous state of scene, stored by firts ctrl+LMB.
This will allow to quickly figure out what is stored in any collection.
C) Ability to invert visibility - to figure out what is hidden in scene. Red line is drawn in UI.
D) Ability to swap any column with visibility. This will allow to view and edit render/other state of objects of entire scene as visibilty for better scene handling and control. Column, that was swapped with visibility column became purple.
E) Ability to make everything visible via single toggle hotkey (maybe * key), to make sure what it contains during setup.
Here is GIF:
3 Likes
Placing the 3d cursor with shift + right click should inherit the properties from the tool settings (e.g. orientation set to geometry in tool, should orient to geometry with shift + right click as well).
Thanks 
7 Likes
Title of this menu is opposite of what it do
maybe Collection visibility
1 Like
…is anyone related to development reading still?
Big thanks for the prudence of whoever figured out that layer (collection) number hotkeys should be kept! Adds up to a huge amounts of man-hours saved across the globe by maintaining eficiency.
One important time saving bit of it was left though - “Move to layer” now is not synced due to “Scene Collection” being #1.
So it’d be great if Scene Collection (as view all) would be made #1, or, even better, if possible -
given that fast, repetitive object/collection shuffle is primarily used between collections, not for removing from all collectiond (that probably happens, but doesn’t compare to the bulk of key presses) Move To Collection -> Scene collection should be excluded from hotkeys or changed to something else, like “~” or “0” or “-”, if natural menu choice hotkey order can technically be broken at all.
Edit: Yeah, the second option opens a can of worms with sub-collections… So probably just shifting general collection hotkey by 1 and making #1 something like “view all”, would be a better idea.
Do I need to report this, or post here?
X-ray in edit mode. X-ray = 1, but I can still see backface geometry.
Perhaps this should work like this:
X-ray =1 - full solid, non transperent.
X-ray =0.999 - as it is now at a value of 1
X-ray = less than 0.999 - becomes transparency, linearly
i think it’s a bug… report it
1 Like
I think this is the last time I send a bug report, or do feedback here or on rightclickselect, or somewhere else. It is completely useless.
this is not a thread about bug reports. and please don’t forget you are not the only one sending bug reports.
1 Like
And not the only one to have this kind of answer from devs who don’t use the software 
I sent a bug a couple of days ago and received a similar response. If you click very fast with the left click keymap you can lose 30-50% of the clicks and not select anything.
IT’s because a conflict with Box Select, just change a parameter that basically does not create problems, at least not as serious as losing up to 50% of your selections and put a huge lag to the input. But it was decided that way and it will stay that way.
We have that lag also in the context menu, by design, of course.
Time to solve the problem 3minutes. God knows how much, a couple of years, to annoy well the UX of thousands of users and that blender seems laggy.
PD: It remember me when I send my first bug, years ago, and I talked about mirror tool, that invert the normals (something that nobody will expect) and the response was the same.
1 Like