rebase on master

Committed rB8df968d69f07: "Show Texture in texture tab" button: full support for Sculpt / Paint

@Richard Antalik (ISS): did you have a chance to give this another look?

Ah, OK, there is indeed an issue with some blend modes (Overlay being one of them)

Yeah, it is the same as T75844: Blend modes are broken, will merge these reports.

Yes, the owner is sometimes not clear if you are looking at a tab or panels.

There has been another fix for this today, see rB09a8f5ebcab4: Fix T86384: Click detection fails in some cases with modifiers, so please give tomorrows build a chance.

Ha, nice find!

Not exactly sure if I understand correctly:

Can confirm

Can confirm, this was working in 2.79.

In D10401#269348, @Sybren A. Stüvel (sybren) wrote:

I accepted to soon.

This clearly is a mistake in the code, as it's indeed inconsistent with the other uses of the frame range. I'm just wondering how many files there are now that have set their modifier frame range slightly differently than they'd actually want, basically to counteract this bug. If we now fix it, that means potentially breaking the animation in those files.

OK, will leave that up to the module to classify/decide.

Can confirm [only with Left Click Select though]

In D10646#269296, @Hans Goudey (HooglyBoogly) wrote:

Yikes, thanks Philipp.

Will set to high prio since you cannot pick colors in a couple of nodes now

Fix is in review

Can confirm, will check

Could you attach both source .blend files?
(I know this does not take super-long to set up, but it ensures we are all on the same page and it might be multiple devs looking at this, so time adds up...)
Thx in advance!

Please attach both the .blend file where this has been modeled as well as the resulting .OBJ file.

I have had similar "issues" with pie-menu on drag sometimes last week (but did not have enough time to investigate)
@Campbell Barton (campbellbarton) made some changes to WindowManager event handling during this time, maybe this has caused some of it? (just a shot in the dark)

I am seeing this crash in glDrawElementsInstancedBaseVertex being reported often now.
It is always on MacOS.

• view3d select has Deselect and Toggle selection
• uv select does not have these

• move "comment" into ui description
• move check for camera projector up (so we can deactivate the sub layout right away before using it)

Btw. change in default naming happened in rB7a6b46aac56b: Fix T62163: Duplicating particle system results in crash 2.79 did not do this.

The thing is: the vertex groups are properties of the ParticleSystem, other settings (such as count) are properties of the ParticleSettings

Thx getting back, will close then.

the last thing I remember when I tested 2.92, at the moment the collection was turned on, it crashed

In D10574#269021, @Robert Guetzkow (rjg) wrote:

@Philipp Oeser (lichtwerk) You're raising good points and I very much appreciate your input. If this is a more general issue that happens in other parts as well, perhaps this is something that should be discussed with the modeling module, so that we can decide how to solve this consistently?

OTOH, doing it like I suggested would probably need Addons to be updated? [ afaict, Blenderkit uses bpy.ops.uv.cube_project -- but already complains about the size of a unit cube as well ;) ]

This report does not contain all the requested information, which is required for us to investigate the issue.
Please submit a new report and carefully follow the instructions. Be sure to provide system information, Blender version, the last Blender version which worked, and a .blend file with exact steps to reproduce the problem.
A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

added Core tag, will leave classifying to the module members

This has to do with the fact that blender primitives are always of size 2 by default, but that often needs to map to 1 somewhere else.
Just had another case today where this could cause problems, see D10632: Fix T86347: Add Primitive Tool fails for 1x1x1 scale

Just noticed there is a duplicate report for this, see T83271: Displace modifier with Image Texture causes scene slowdown, no need to have two reports open for this, will merge them.

@Dalai Felinto (dfelinto) : can we consider just saving this file with the solidify modifier tweaked (see above for why this fails) and reupload?

Hi @Ludvik Koutny (rawalanche) , looks wrong indeed, will check.

Size 2 is actually correct here (it is the default for prims in blender), scale is what is handled wrong, there is an exception in rB16943c01464c: Object: add scale argument to creation operators especially for the 1x1x1 scale case.

Can confirm, it is not only an issue with the add tool, python is also inconsistent, check:

Yes, this should be handled by T73360: Fast highpoly mesh editing, feel free to continue discussion there [you might also want to share your findings from stackexchange there]

This seems to be the same as T85886: [2.92.0 RC] Rotate Tool and Adjust Last Operation - angles inverted, will merge these reports.

Thx @dupoxy digging up the duplicate(s), will merge with T85745.