("Task"... I feel like a boss. It's not a task it's a bug. "Bugs" are just ok, "Tasks" leads to overheating and so on. Sorry, someone should say it.)

Hello All,

@Luca Crisi (BugFinder) can you test if this issue is resolved in the experimental build ?

This is fixed in Blender 2.81, I believe this is the same issue as in T68340.

I can reproduce the problem in the stack trace when the collection is hidden in the viewport and Add > Mesh > Single Vert > Add Single Vert from the Extra Objects add-on is used.

By the way, not only that. A couple of subdivisions can lag a lot while mesh editing. 2.79 doesn;t suffer from that. A lot of people complain about subdiv performance on editing.

In T68744#754825, @Evan Wilson (EAW) wrote:

I must say upfront that UV editing is not something I know a lot about.
The fix (or one that I at least know of) to your issue (if I understand it correctly) is turning on proportional editing. It is in the center of the left window at the top. It is highlighted in yellow in this screenshot.

When it is on, the polygons remain intact when only one face is selected and moved.

Gavi Scott (Zoot) is ma MAN.

@Luca Crisi (BugFinder) You didn't mention an exception while using the Extra Objects add-on in your original bug report. Please try to create a complete bug report next time, we're not mind readers. I also have to agree with @matc (matc), if the screenshot shows the problem you're having, this doesn't seem to be related to extruding. It looks like there is a problem switching to edit mode within the AddVert operator. Are we missing any additional steps that you didn't mention?

Hi guys,

Thx for the help!

Sorry I never told you. It was an addon. Now fixed. I didn't figure out qwhich one though :P

Does this really happen "based on the default startup"? Your screenshot shows quite a busy file.

I thought that "ERROR" is a synonym of "BUG"...
Isn't it?

So... what about this?

Can't reproduce with Blender 2.8, extruding a single vertex works fine.

Worked up to 2.79b

This has already been fixed in master by patch D5479 and commit c047f6460486 for the issue reported in T68618. The fix is not included in 2.8 release.

That will be nice to fix that, because it is hard to keep concentration during modeling process, and shortcut rejection brings frustration.

Okay Thanks. understood the issue.

Okay thanks, that seems to have fixed it. Sorry if this is a dumb question, but can you also tell me why that worked? It's all still a bit confusing to me.

Go to Properties Editor > Scene > Keying Sets and remove all sets.

i found problem :)

I'm still new to animation, and I have never encountered this error before. Could you elaborate on what you mean, please? That link doesn't really help me to understand what to do.

i downloaded lastest version on site

I can reproduce. Keymap entries set to click won't activate on click-drag in general. A quick/temporary fix would be to use press events for the relevant entries when the drag pies are disabled.

here is another bizarre and interesting phenomenon …
the first ship is composed of many objects but all edited simultaneously … the second ship is a single object …
notice the differences …

The error with these files is in vertex indices, I don't think it's reasonable to support vertex indices written as floats, it would be better to report a bug to tinkercad.

excuse my basic knowledge of the subject but when you say "everything nodes" that does that mean also on the data block level where an object can have different atomic nodes like attributes node,shape node, transform node,..etc aka as DG & DAG nodes something like in maya or softimage this gives more granular control on the scene data and how the information flow for hierarchies and relations or is it something more high level?