Yep, I can confirm here too on windows, the moment you enable Ambient Occlusion, it doesn't matter if you're in material preview or Eevee, accessing the viewport shading leads to a crash.

In T74133#878590, @William Reynish (billreynish) wrote:

Should be resolved by the commit 39d0bf90444ef42246f50c5346989780d01e20f4

Okay, I didn't know it had other implications, hopefully when it's part of the mesh then it can work.

Thank you @Brecht Van Lommel (brecht) for the answer.

In T68891#877586, @Paul Kotelevets (1D_Inc) wrote:

In T68891#877510, @Zino Guerr (Zino) wrote:

Can you, please, post a couple of screenshots (object mode / edit mode) with instances from Maya to clarify the issue?

I can do that but the last time i tried Brecht said it's not okay to make such posts

Well, okay then. Thank you for GIF.

The only trick i know is you have to join them with the last selected object that has the modifier, apply it then separate them again.

EDITED
Yes, the ability to set subd directly on mesh level should make subd inherit through all instances.
Seems you are using 2.81, such weird modified instances behavior was fixed in 2.82.

In T68891#877468, @Paul Kotelevets (1D_Inc) wrote:

In T68891#877409, @Zino Guerr (Zino) wrote:

Coming from Maya i always was able to have smooth preview with subdivisons on instanced meshes(duplicated linked)

Can you, please, post a couple of screenshots (object mode / edit mode) with instances from Maya to clarify the issue?

This option is best to put it in the Shading Popover for quick use, but thank you Pablo for adding it nevertheless.

A quick stupid question.
Coming from Maya i always was able to have smooth preview with subdivisons on instanced meshes(duplicated linked) but in Blender since you have to use the subdiv modifier, then the linked duplicated meshes don't "instance that modifier", so you only have the preview the original mesh until you exit edit mode.

I want to point out a limitation of the symmetry tools in Blender.

In T73771#871952, @Hans Goudey (HooglyBoogly) wrote:

This isn't a bug, and it's actually a bug fix that caused this change. There shouldn't be "individual origins" because all of the vertices are connected by at most one edge.
The technique you brought up still works, just use a different bevel offset to change the size of the holes rather than scaling them. That said, the profile value of 0.1 doesn't create a circle, 0.088 is closer, but the way bevel is coded means you shouldn't rely on the profile to be perfectly circular.
Thanks for the report anyway.

In T68970#871939, @Paul Kotelevets (1D_Inc) wrote:

In T68970#871878, @Zino Guerr (Zino) wrote:

I personally had to change every tool and operator event to make my own custom keymap

For sure. We also do this every time, (but we change operators only from version 2.8)

and keep that consistent across Blender's version not matter how small or big the updates.

That would be nice, but it will bring too much limits to a development process.
Requests cause structural changes to the key map, the toolkit is constantly changing, so these changes occur.
To make viable solid keymap core, devs should at least take into account every workflow, including complex one, that will be a years of research and hundreds consultations, and develop to its final stage every tool that will require keymap.
Not sure if this is possible.

I personally had to change every tool and operator event to make my own custom keymap, the problem i faced everytime is whenever there are new changes added to Blende, they affect the keymap and you have to re do it all over agin.

@Stanislav Blinov (radcapricorn) But it worked in previous versions though! if you bevel a row of vertices and scale them on their "individual origin" in 2.80 or 2.81, in the master branch even when extruding includes that contiguous edge where before it wasn't that case.

In T69728#845523, @Pablo Dobarro (pablodp606) wrote:

The issue reported was fixed for Windows as far as I know. If there are any other bugs in this feature, please open another bug report describing them.

You should use English to communicate the bug & with better steps, also this has nothing to do with imported meshes from Maya..was going to report similar but the bug seems to be fixed by the commit that Steffen has menitoned.

It also creates weird geometry inside the mesh.

This seems to be fixed in the latest build so this report can be closed.

I too have this with my custom setup,Preserve Sharp is the one that gives me two non-manifold tris with the default Cube even with the provided blend file.

If Pinch can give us this kind of sharp Peaks and Valleys then i am all for it otherwise we'll need another draw sharp brush for this type.

Hi @Germano Cavalcante (mano-wii) sorry but this bug is back in the latest build, I think it's caused by this one '3a08153d7a84'

Really strange! I have updated the graphics driver to the latest, downloaded the latest Alpha build, reset to factory settings and it's still the same.

In T69728#777688, @Jeroen Bakker (jbakker) wrote:

Hi @Zino Guerr (Zino)
Can you update your graphics drivers there are almost a year old, might be a driver issue.

Hi @Jeroen Bakker (jbakker), for me it's still the same with a clean new build, i have to use the Viewport Gizmos shortcut to get out of the locked state, is this a hardware specific issue?.

Hey Eitan, I tried your patch and it's nice but i really don't understand the point of changing wireframes opacity in the UV Editor.
can't know what the request is about since RightClickSelect is down.

@Germano Cavalcante (mano-wii) Yeah, I no longer see this bug probably got fixed in the past few days.

In T69928#776884, @William Reynish (billreynish) wrote:

buttons disappear when used and only reappear if you exit the filed

Exit the filed what? I don't follow this sentence.

Fixed by this 'fd5c1972cd5'

There isn't exact steps it is factory settings,wireframes on top is clearly wires on solid for both Overlays & Object's tab.
Hotkey or the tool, maybe you are on a different OS or not up to the latest commits, this bug is not in the buildbot yet.