# BUG extracting edges from SubD

**URL:** <https://discourse.mcneel.com/t/bug-extracting-edges-from-subd/175772>\
**Category:** Rhino Developer\
**Tags:** windows\
**Created:** [February 15, 2024, 4:39pm UTC](https://discourse.mcneel.com/t/bug-extracting-edges-from-subd/175772 "2024-02-15T16:39:46Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![maje90](https://sea3.discourse-cdn.com/mcneel/user_avatar/discourse.mcneel.com/maje90/32/762888_2.png) [@maje90](https://discourse.mcneel.com/u/maje90)\
**Post date:** [February 24, 2024, 1:18pm UTC](https://discourse.mcneel.com/t/bug-extracting-edges-from-subd/175772/4 "2024-02-24T13:18:26Z")

</div>

> [@dale](#):
>
> > [@maje90](#):
> >
> > SubD rhinocommon methods are stil far behind…
> 
> Sorry, I have no idea what this means.

Rhinocommon. C#.

* * *

I’m used to the GREAT accessibility McNeel gave to users/developers to a wide set of classes and methods to virtually do anything with c#. Everything’s perfect!  
Everything but SubD’s. As said [here](https://discourse.mcneel.com/t/any-progress-in-subd-methods/165226/36).

SubD normals? (as said, I’m extracting edge curves becase no avail normals… 🤕 )  
SubD parameter + EvaluateAt?  
SubD.Faces.Add?  
SubD ToNurbs custom packing?  
Still no iterator for SubD.Vertices. (looping .Next for thousand of vertices is slow)  
GH Pointdeform sill has no idea what is a SubD.  
an so on…

Maybe the situation via c++ is totally different, but from c# the difference of SubD methods from the rest of rhino libraries is huge. … like, done by someone else with different “motivation”…

* * *

I feel like the only idiot screaming at a wall trying to make up stuff around SubD.  
There are any plugins for more editing tools for Rhino SubD? Any kind of tool. Edit. Freeform, etc…  
Are those made with c++ or c#?

---

_[View the full topic](https://discourse.mcneel.com/t/bug-extracting-edges-from-subd/175772)._