Surface error after filletEdge

After making filletEdge on the edge between the single-span surface and the ExtrudeCrvTapered product surface I have 100 errors like this.

This is a filetEdge product.

What is that?
How to prevent that error?
How to fix them all at once without manually rebuilding each separately which consumes a lot of time?


bad_srf.3dm (101.5 KB)

Hello- please post the input for this fillet. The problem is there are (nearly) stacked control points at the end of the fillet and it folds on itself.

-Pascal

Do you know something about giving surface like that to production for CNC. Will it work?

Hello- I do not know specifically but I would not be surprised if these caused trouble. Please post the input, or send to tech@mcneel.com

-Pascal

1 Like

Thanks, I will do that later.

Do you know maybe how to detect it in other way than by eye?

I think I`ve found what causes that. It is because of G0 (lack of tangency) across patches produced from
ExtrudeCrvTapered - that thread: ExtrudeCrvTapered problems (please fix it) - #22 by mdesign

It causes those problems in fillets.

The problem is logged as RH-83398 Stacked controlpoints after filleting edges

I added this thread

3 Likes

Finally! Thanks for adding that bug to the pile! I reported it many times over the past years, showed the issue on several videos, yet nobody considered it a bug up until now. Lets hope that it will be resolved for the all people who use Rhino 8 (I know that Rhino 7 will keep the bug).

The manual fix of that bug is to remove (“Remove knot” command) all the doubled end control points and leave just one of them.

1 Like

@Rhino_Bulgaria Thanks for your reporting up until now. I have - I think - made a fix for this. It would help greatly if you could point to some of these topics, or models you were working with that have this issue, so I can test more and be more confident that the fix created will work across the board.

2 Likes

That was years ago, so I have no idea how to find the topics. Most likely I don’t keep the 3d models either, because I simply fix the bug by using the ! _RemoveKnot command. However, I think that some of these videos are still on my YouTube channel, but since I don’t remember the exact videos, it will take a while until I find some examples. Some videos are over a hour long and it’s not easy to find the exact moment where the bug appears. But I’m pretty sure that I fix that bug on at least 5 of my old videos.

Ok, anything that you can find will help - no pressure, I understand that things you worked on many years ago may be hard to find.

1 Like

Good news. I just found one of the videos after a search on my YouTube channel. I will check if I still keep that 3d model somewhere.

Check the 5:35 minute of the video to see the bug with weird shading that indicated a bad geometry there:

After some search on the forum, I also found one of the topics where I reported that bug 3 years ago. That same topic also contains the 3dm model from the video (post #3):


I have to correct myself. Looks like Pascal added this to the pile and the bug was supposed to be fixed for Rhino 7 SR11. However, it was left unresolved and I have seen it in Rhino 8 as well.

https://mcneel.myjetbrains.com/youtrack/issue/RH-65216


I just found two more topics where I reported the bug:

And another video posted by me in the topic from the last link (check the 1:28 minute):

Here is the 3d model from this particular video. The weird looking fillet is also included:
Random bug.3dm (5.7 MB)

1 Like

The first linked model seems the same issue and works well in current build of the day.
The latter is a different issue.

1 Like

You mean that the bug will never be fixed in Rhino 7, but is not present in the latest Rhino 8 release?

no, what I mean is that the bug with the fillet that goes haywire is a different issue. I haven’t logged that one yet

Looks like we talks about slightly different issues. I meant the bug with duplicated end control points, which is shown in my videos above and reported in 2021. Will it be fixed for Rhino 7, or it will be left unresolved there, focusing only on fixing it for Rhino 8?

Ah, sorry I misread…
No. Rhino 7 development is closed.

RH-83418 BlendEdge curls up

1 Like

I read it this way: Fixing of critical (for the modeling work) bugs in Rhino 7 is closed. :slight_smile:

Hopefully these will be resolved in Rhino 9, because I may jump from Rhino 7 to 9.

I wish you could search through your images somehow on this forum, because I’m fairly certain I’ve uploaded images of a few surfaces with these darkened areas over the years…