Found the issue. It's the subdivision on the body. It's set to 1 for the viewport but 2 for rendering. When I set it to 1 it works. Case closed.
So 4.1 lets me render a sequence but the hair completely go crazy. They are OK in the viewport in cycles but as soon as I do Render Image or Render Animation I get completely broken results.…
Release candidate was OK but looks like everything broke for the official release. I need more testing. Working on it now.
This issue was opened 5 years ago. I wonder which feature in the Cycles development is more important than this one. If it was my call, it would be on top of the list. This is such a big issue for…
OK so it's closed but does that mean this has been flagged somewhere in you system and be looked at later or it will just stay like this?
So turns out it's the motion blur that makes 4.0 crash when rendering a sequence.
I will try in a few hours. I was trying to install 4.1 on my laptop too and got an error message that the path was too long. I'm sure this doesn't help ;-)
blender-4.1.0-candidate+v41.b9ef66693a…
I thought the problem could be because we are using an addon to have geo node hair with dynamics.
I've tried 4.1 again and it's seem ok this time. Maybe it was something else before when it crashed.
blender-4.1.0-candidate+v41.b9ef66693adf-windows.amd64-release
I answered too fast. I crashed after a few frames
Ok, I have been able to try in 4.1 and it's working!
I'd love to but 4.1 doesn't like me. Took about 3 minutes to launch. Then I ask to use my settings for 4.0 and it has been a few minutes and it's seems jammed. 4.0 is also very long to open.…
Ah! I figured out what happened. The mocap system exported my files in ASCII, which is not supported by Blender. So I opened another file in Maya that did have fingers in it, for conversion. Then…
There's already the code to select the border edges. So if all vertices are selected, select everything but the border edges and that's it. Easy fix. :)