Rhino 8, WIP extremely slow - due to results of MeshSplit

[wim (Wim Dekeyser)]

Hi David -

@davidcockey

It seemed to work, and then Rhino closed. No error messages or anything.

Is that reproducible?
-wim

[davidcockey]

@wim

Is that reproducible?

It was six hours ago with the mesh that I used, but is not reproducible now.

I’ll continue to investigate when I have time.

[piac (Giulio Piacentino)]

@davidcockey

It seemed to work, and then Rhino closed

@davidcockey

I ungrouped the six meshes, selected the meshes, and then split them successfully.

Hey @davidcockey , thanks a lot for the live feedback.

If we cannot test it here, it becomes very hard to understand what could cause it. I’ll keep an eye if anything comes this way.

[davidcockey]

@piac

Hey @davidcockey , thanks a lot for the live feedback.

If we cannot test it here, it becomes very hard to understand what could cause it. I’ll keep an eye if anything comes this way.

@piac Perhaps you missed my follow-up post that I could no longer repeat the problem.

@davidcockey

@wim

Is that reproducible?

It was six hours ago with the mesh that I used, but is not reproducible now.

I’ll continue to investigate when I have time.

[piac (Giulio Piacentino)]

@davidcockey

I’ll continue to investigate when I have time.

Thank you!

Yes, I read that message above, but maybe other people encounter that same bug. Or it was fixed this week. There’s a lot of movement in all mesh boolean/intersection/split code for 9.