Amputating a Guy Without Edit Mode

I want to chop off this guy’s leg.

However, I can’t do it in edit mode. Blender keeps crashing when I try to get into edit mode. Any ideas on how to get through this, because I’m way too tired to think right now.

Unhiding all the hidden face sets solved the problem. My question now is why?

Hmm… maybe your amount of vertices is a bit too much for blender / your specific computer specs or whatever ??

You got 3mil vertices just in that one mesh… and at least 5 more sculpted meshes…So sounds to me like you are just trying to work on meshes that are just too much for your rig…
I think it’s time you append the parts to a fresh Blend and re-topo!

1 Like

Yes, there’s 7.5 million vertices in this project as a whole, so appending probably would be a good idea at this point. However, I’m still curious as to why hiding face sets pushes Blender past the limit. If anything, Edit Mode should be opening up easier because of the reduced number of vertices it needs to show.

My computer has seen worse. It wasn’t any faster, but it didn’t crash either.

Did you actually set it not to render meshes ( TV icon)? ( actually, NO, I just checked your screenshot)
The eye Icon only hides them in the viewport…TV icon stops them from being included in the calculations…
Give it a try…

It’s working fine now. I fixed it by unhiding hidden face sets. My question currently WHY that works. For example, I’d imagine that your solution works by reducing the number of calculations and thereby reducing memory strain and chance of crashing. I don’t understand why my solution worked.

At this point though, I’ve noticed running multiple actions while Blender is operating over my maximum memory will crash Blender, while running only one will make Blender keep trying. Once, when I tried running a fluid simulation, my computer had to force Blender to give up when the memory estimate reached 10 times over the limit (I didn’t understand the importance of retopology that time and ran it on a 5 million vertex mesh).

Could it be that Blender just gives up when trying to add another operation will push the running requirements over the memory limit of a system?

Well… there is not just the needed amount of memory to store the data… while processing it there is also the need for using memory for this… Some operations might just use additional 15% (a bit more) and other 400% ( four times more !) … so it depends how much your memory monitor shoes you :person_shrugging: :question:
Also bear in mind that blender initially wasn’t made for sculpting like some other apps which are more optimized for that. So the workflow used to do so might differ from them.