ic, so if that is normal geometry i guess it should just work there either. i am sure @menno will figure it out, he is on it, i am really stoked that general shapes besides elipses work now without having to break a leg. though there are still slight advantages in the general shape when you use the old patch but i might get to that at a later time.
also it would be really good if the command could close with space.. pls pls pls.
Sometimes changing the degree of the surface makes a big difference, despite that the geometry is 100% identical as a shape. “Blend surface” is very sensitive in this regard.
I’m experiencing a slowdown not only during the command selection phase, but also after the command has been executed. I encounter a temporary freeze where I’m unable to orbit around the object for a short time before navigation resumes.
@brvdln does that happen always, or after some time? Does it happen again if you close and reopen Rhino?
If I restart Rhino, the problem does not occur.
I’m not sure, but this slowdown seems to occur more often when the document has a lot of layers, especially sub layers.
In that case, after selecting a constraint, it takes ~1 sec. to show the label.
Thanks for that, I have made a ticket here RH-94426.
This is really solved, no delays anymore in here.
@brvdln still curious about the delay on adding the result to the document. Please let me know if that keeps happening.
@menno Now everything is okay, I’m not experiencing any slowdowns. 
Hi @menno,
Thank you so much for the amazing rework of the Patch command in Rhino 9—it’s a game-changer for our workflows!
I have a quick question about the Grasshopper Continuous Patch component: it currently only accepts Brep input, while the Rhino command works directly with curves, edges, and points. Could you confirm if this is intentional?
It would be incredibly useful if the GH component could also accept Curve input (matching the Rhino command’s functionality) to create G2 patches directly from wireframes without needing intermediate surfaces.
Thanks for your time and great work!
I am sorry, I miss understand the component. It takes curves.
Thank you! @nxakt
————————————
New patch looks awesome!
Am I the only one noticing the speed still feels sluggish? There is no doubt this is a massive leap forward over the older patch, a genuine qualitative improvement. It’s fair to say Rhino’s native patch is now comparable to third-party xNurbs in terms of core quality. That said, it still falls behind noticeably in processing speed. Too slow.
@Quan_Li I also notice some slowdowns. It’s strange though—sometimes it lags, other times it runs smoothly.
