In T74967#1020169, @Brecht Van Lommel (brecht) wrote:

We will most likely keep the modifier stack, from recent discussions regarding particle and geometry nodes.

We want users to be able to turn node groups in custom modifiers with a high-level interface. And I think the modifier stack is a good place for that kind of interface, where you don't have to open the node editor, but can just quickly add a modifier and tweak a few settings.

Thanks for the reassuring,that's really great news.

It makes sense to have nodes for Particles,Rigging, Grooming...and i understand that people want to do more procedual modeling, Blender is known for it's powerful modeling capabilities more than anything else & that's thanks to the modifiers stack and the other tools/addons.
Keeping the modifiers stack is essential to many users, and also much more easier & straightforward workflow , this is how 3ds max team has done it.

the same problem for me but it's random, if i keep relaunching Blender they might show up sometimes but if they don't the sidebar gets this drawing glitch.

@Harley Acheson (harley) Hey man i want to say thank you for putting up with us, we have flooded your patch with unnecessary comments which should have been more thoughtful including mine.

In D7410#180956, @Harley Acheson (harley) wrote:

@Zino Guerr (Zino) - Unfortunately the stats are too cramped togather best to remove the forward slash and add some spacing for better readability.

Wouldn't that also be helped by adding some padding around the forward slashes?

In D7410#180948, @zebus3d (ofuscado) wrote:

In D7410#180947, @Zino Guerr (Zino) wrote:

Unfortunately the stats are too cramped togather best to remove the forward slash and add some spacing for better readability.

In my addon looks good:

Unfortunately the stats are too cramped togather best to remove the forward slash and add some spacing for better readability.

In T74416#916053, @Brecht Van Lommel (brecht) wrote:

This should be fixed by {a68bd94}, if not I can reopen the report.

Unfortunately it's still happening the first time with the xray, but once you switch to Material or Render preview modes then the issue is gone.

This can be closed i think.
It seems to be fixed on the latest version at least for my setup, so thank you.

In T69577#910581, @Paul Kotelevets (1D_Inc) wrote:

In T69577#910522, @Zino Guerr (Zino) wrote:

Hi, is there away to disable the QCD in the header?
I like the addon but i don't want those 20 collections crowding it. Thanks.

For sure, a checkbox in addons preferences in addons section.

Hi, is there away to disable the QCD in the header?
I like the addon but i don't want those 20 collections crowding it. Thanks.

I tried the Patch and i have some suggestions that i think would make it nicer if you guys don't mind.

In T74905#894487, @William Reynish (billreynish) wrote:

This is not a bug AFAIK. The code explicitly sets the opacity to factor 0.6 and then to 1.0 on rollover.

IMO, I do find this to be too much - the gizmos become too unclear in many cases. However, it doesn't appear to be a bug.

Updated the driver, still the same.

In T74416#884734, @Richard Antalik (ISS) wrote:

@Zino Guerr (Zino) Textures are missing, please pack them in to file

I updated the file with the packed texture.

In T74251#881550, @Ankit Meel (ankitm) wrote:

as you might have received an email about a fix for T74227, have you tried 57bd1a0ae18b ?

Still crashing here with a GTX 1050 TI, only when enabling Ambient Occlusion.
I have opened a new report here T74251.

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 on the original mesh until you enter 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 Blender, 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 works, 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.