Corrupt SubD

Hi folks.

Version 8 SR5
(8.5.24047.13001, 2024-02-16)

had my first subd go corrupt today.
image shows a symmetry subd, the left side of image should match but doesn’t. This was working fine for me for over a week on this model, then just this morning effed up on me.
All the mesh points are identical. The creases are identical on each side.
I don’t get it.
Actually not even sure how long its been there as my recent backups have this as well.
Need a mcneel email to send the file to can’t post it here.

I’ve split and resymmetried with no success. Somehow this knot keeps showing up.

Hello- if you can post the object or send to tech@mcneel.com, with a link back to this topic in your comments, I’ll take a look and, no doubt, send it along to the larger brains.

-Pascal

thank you Pascal sending now.

Got it - thanks, I’ll send it to the developers for a look. For the short term, RemoveSymmetry and then Reflect once again seems to sort it out.

RH-80535 Reflect - not quite

-Pascal

weird. i tried removing and reflecting twice, no success. will try again on the file i sent you.

yah still doesnt work for me. strange. is there another setting for remove sym and reflect i’m not using?

You are correct - it does not work. At least I cannot repeat my initial test which seemed correct but maybe I was hasty.
ExtractControlPolygon then ToSubD does seem to clean up however… here at least.
-Pascal

1 Like

sadly i lose the creases with that.

@carvecream Removing the crease weight on the edge with the corrupt “bump” (with _RemoveCrease or _SubDCrease to set the weight to 0%), or on its symmetrical parent, will get you back to a normal SubD behavior. Anything else than 0% and the bump is back.

If you move the whole SubD so that this edge is closer to the origin, I think the whole corrupt behavior disappears. You may have to change the weight on the corrupt edge to something else than the current value and back so the display mesh updates.

I just fixed this bug. It was a simple typo in the code where an x coordinate was used in place of a y and z coordinate. Nothing to do with symmetry, distance from origin, or sharpness settings. It occurred on edges with sharpness not equal to 0%, 25%, 50%, 75%, or 100%.

2 Likes

A post was split to a new topic: SubD SDK request: SubD crease weight accessible in GH

thank you Dale can’t wait to try the fix, will it show up in next RC?

This fix will ship with 8.6.
The current release schedule is:
March 12: 8.6 release candidate 1 available.
April 9: 8.6 released.

I apologize for the long wait. I missed the 8.5 cutoff date by a week or so.