Hello, this problem seems to happen again in 3.2, could this thread be reopened?

Using UVs to attatch hair is a pretty clever idea, and pretty simple to comprehend, and even if someone wants to make an UV that overlaps(for symmetric painting for example) or wants to change the UV after attathing hair, they can use an extra UV just for the hair if they want.
Also, it sounds much simpler to transfer hair from one surface to another if needed using this concept.

I can confirm, its broken for me too

I have a more recent version of this file where these hangs are a lot less frequent, I just can't pinpoint what I changed to reduce the hangs, probably a change in the nodes.

does this happen when you run Blender from console with -t 1 argument? So it would be blender.exe -t 1.

sorry, I was having some problems with the debugging.

yeah, it looks fixed in the last alpha

Weirdly enough, while testing I noticed that if you save the file in 3.2 and try to open in 3.1, it starts working again, but then, even if you don't save, the next time you try to open it with 3.1, it hangs again.
In 3.1.1, it stops hanging after you save in 3.2 and stays like that until you save in 3.1.1

Speaking about 3.1, I'm not even able to open the file... (so I force stopped Blender instance)

I'm sorry I missclicked enter while typing the title

should be a911f075d7aa823b215d4e7baf91ea4f5bd6099c fixed this

With T96003 being fixed I tested to see if the problem here was also fixed, and it seems so.

I think this is intended since rigify needs the heel bone in order to generate a the leg.

I feel like most of the lag is being created by the realize instances, if you mute that part the viewport still a bit laggy but much less than with the realize instances, It just don't make sense why it doesn't lag on eevee

I'm also getting lag in the image editopr but I'm using an AMD card(rx5700xt)

I do not have the model that was crashing after the symmtry anymore. but the one that is contained in this thread still crashes in 3.2. If I manage to reproduce it again I will upload it.

This problem is similar to one I had some versions ago(T82093), I'm not sure yet if it had been broken in the viewport since then

Yes, the problem is because of the B-spline. but I'm not sure if this is intended behavior.

This is a visual effect of the b-spline, but I'm not sure if this is intended behavior of this option. I noticed this sometime ago but never reported.

Did you activate B-spline on the hair? this usually is what disconnects the hair from the surface visually.

Is there a Branch to test it?

There is something I think would be pretty useful for rigging animals, I can do it with the post-generation script, but It would be better to have as an option if possible.

I think there may be more than one bug interacting here and it may not be related to the original bug in the thread.

I really think there is something off with multires in 3.1, I remade the whole multiresolution and took care to not change the topology of the model, and I still got a problem.
I just tried to bake the multiresolution in 3.1 and it crashed the same way the broken one did. I then tried to do the same in 3.0 and It baked, but the result was this:

Reducing the spacing size of the brush seems to drastically minimize the problem for me, I usually like to keep it at a lower value like 2% .

sorry, that modifier stack in the video is a bit misleading. the bug still occurs even without those last two shrinkwraps. The .blend file don't have those, and also as said before, it doesn't occur 3.01 and before

I got no problems on 3.0.1

I have another problem with normals in sculpt mode but I'm not sure if its related to this one. I'm not sure what I am doing to make it but I'm guessing its something to do with dyntopo/wireframe view.

well, the file I'm working on is pretty heavy, but I managed to reproduce it just by using a high poly mesh.

It seems like it doesn't even need to be in eevee for the performance to be affected. If you switch to vertex visualization in the regular solid view and then switch back, it also reduces the performance.

Just noticed today that this glitch also occurs when using the Experimental Sculpt Vertex Colors, since its stored in attributes.

I decided to test this a little bit more and I found some things that might be what is causing the problem.

I just got the same problem problem with another file(blender 3.1 alpha):