When testing, I came across this assert:

BLI_assert failed: ...\source\blender\modifiers\intern\MOD_solidify_nonmanifold.c:2441, MOD_solidify_nonmanifold_modifyMesh(), at 'loop_index == numNewLoops'

In D8943#219699, @Hans Goudey (HooglyBoogly) wrote:

On one hand I think this is a really handy operator that could speed up this workflow a lot. However, I wonder if this is solving the problem in a way that's too specific to this situation.

It also doesn't solve a few similar problems with this workflow: setting the render or viewport visibility.

Here is a more general way this could be done:

1. Add this in the right click menu for collections in the outliner.
2. Add a shortcut on these ID selector buttons to take you to its location in the outliner.

And another would be adding this to the existing right click menu for ID selector buttons, which already contains "Jump to Target".

I don't necessarily think these ideas are better, just that more similar solutions should be considered.

Made requested changes.

Oops, I forgot the "T" in my commit message

On one hand I think this is a really handy operator that could speed up this workflow a lot. However, I wonder if this is solving the problem in a way that's too specific to this situation.

In T80839#1018680, @Sergey Sharybin (sergey) wrote:

@Germano Cavalcante (mano-wii), not sure how performance is related to the out of memory exception?

Thanks for the report! I can already guess what it's doing wrong, the fix should be simple.

In D8934#219328, @Germano Cavalcante (mano-wii) wrote:

Looks good.
The description of the commit can be a little more explanatory, for example:

The transform convert of type TC_POSE was not being defined if the object mode was OB_MODE_WEIGHT_GPENCIL.

Looks good.
The description of the commit can be a little more explanatory, for example:

The transform convert of type TC_POSE was not being defined if the object mode was OB_MODE_WEIGHT_GPENCIL.

I am looking forward to the Simple Mode. Currently your Simple Mode is kind of implemented in complex solidify,
but due to T80897 I started thinking about removing it. Also adding a good fallback value in the spot in the code where no
zero edges are allowed.

In D7622#218952, @Clément Foucault (fclem) wrote:

I want to remove the edge discard threshold and make it system / scene wide (not per viewport like what we have now) to avoid some overhead in wireframe batch computation.

In this case, the wireframe slider would become an opacity slider and we would have a checkbox to show all edges or not. This would avoid too many options.

I think we are going into a direction where the wireframe slider will effectively be an opacity slider.

Thank you for custom normals preservation ability!
https://www.blender.org/wp-content/uploads/2020/08/290_normals_preservation.mp4
But is it possible to support Split selection (Y key) as well?

I confirm that the Percent mode messes up the entered value.

This is in fact an issue drawing caused by rB4212b6528afb07d9b2962566ae9c4251282d387f, (the join is working). Notice face-dots are drawing properly when face-mode is selected.

not a bug, caused because you had 0 scale on z, and was solidifying to the z (local) direction

It seems to be a problem related to the one described in T73344: Modifiers disabled in viewport are not rendered if the object is in edit mode.
But perhaps the cause is entirely different.
So I am confirming this as another bug.

Slight amendment to the code I posted above (forgot to check if it's a mesh). If this is run from the text editor prior to export, then the fbx error disappears

Setting to hig prio since it is reported so often.

Thx reporting!
Mind sharing the .blend file where this happens?

@Richard Antalik (ISS) In our case Blender 2.83.3 was used when the bug occurred. No add-ons besides the ones that are active by default. The artist extruded (E key) the arch above the door into the wall of the building like so:

Ugh, didn't see there are changes request from my side.

I will fix this in the upcoming days hopefully. I would rather change complex solidify to fit simple solidify even when the behaviour of simple solidify was strange. Otherwise older files using that feature would need versioning to be converted to the new version. (which would not be that big of a deal, if someone has a strong opinion on this let me know).

All History:
Ctrl-N
1
X
Shift+A 21
RY90
RZ90
TAB
Select TOP Point Segment With Handles
SX0
Object Data Properties - Bevel [0.14]
Select only TOP Point without handles
Shift+S8

The problem is that this operator is being called in a 2D context (without a 3D view).
So it is to be expected that it does not have a defined orientation (if the orientation was VIEW, which 3DView should the operator choose?).

Thanks for the report. There is indeed a corrupt mesh (it is indeed from the windmill.001 object) in that file, if you run the following

I think having this functionality is fine.

Vertex Colors get totally messed up too, see the picture.