# TSpline node ToBrep crashes when feeding it with a "bad" T-Spline

**URL:** <https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224>\
**Category:** Geometry\
**Created:** [September 5, 2025, 6:52am UTC](https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224 "2025-09-05T06:52:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![G-G](https://avatars.discourse-cdn.com/v4/letter/g/2acd7d/32.png) [@G-G](https://forum.dynamobim.com/u/G-G)\
**Post date:** [September 5, 2025, 6:52am UTC](https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224/1 "2025-09-05T06:52:55Z")

</div>

Hi folks,  
It can easily happen that you build curve networks that result in an “invalid” T-Spline body when using the BuildFromLines node. If you try to get the Nurbs surfaces from such an invalid body, Dynamo crashes:

 ![Crash](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/b/0/b0f0a92c9fbf415d12f3cefa4c2a030a977ccba0.png)

[crash-3.dyn](https://forum.dynamobim.com/uploads/short-url/IqrFxhZVQlCFRO8kytIAI32pLj.dyn) (887.7 KB)  
Please makes this node a little bit more robust. 🙂  
Thanks,  
GG

PS: If you should need the original nodes which created the geometry inside of the Remember node, please let me know.

---

<div class="post-metadata">

**Author:** ![G-G](https://avatars.discourse-cdn.com/v4/letter/g/2acd7d/32.png) [@G-G](https://forum.dynamobim.com/u/G-G)\
**Post date:** [September 9, 2025, 8:26am UTC](https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224/2 "2025-09-09T08:26:55Z")

</div>

@solamour seems that this didn’t get the attention from the T-Spline team yet (or must this be solved in some other part of Dynamo?), can you please ping one of them here, to get their attention?

---

<div class="post-metadata">

**Author:** ![solamour](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/solamour/32/153516_2.png) [@solamour](https://forum.dynamobim.com/u/solamour)\
**Post date:** [September 9, 2025, 8:27pm UTC](https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224/3 "2025-09-09T20:27:24Z")

</div>

We’re taking a look now @G-G 🙂

---

<div class="post-metadata">

**Author:** ![solamour](https://sea2.discourse-cdn.com/flex022/user_avatar/forum.dynamobim.com/solamour/32/153516_2.png) [@solamour](https://forum.dynamobim.com/u/solamour)\
**Post date:** [September 9, 2025, 8:38pm UTC](https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224/4 "2025-09-09T20:38:21Z")

</div>

@G-G so we took a look. There is indeed a bug 🐛 here that we’ll need to address internally, but from your graph perspective you have effectively a T-Spline with zero faces, so you cannot convert them to a BREP.

If you look at the output from your _TSplineSurface.BuildFromPipes_ node you’ll see it has zero edges and zero faces. Can you try play with that node first to ensure you get a valid surface? That should in theory not crash when plugging into the _TSplineSurface.ToBrep_ node.

TSplines allow empty geometry as “legal”, which qualifies as an Empty output. However, it shouldn’t crash. That’s on us to fix.

 ![image](https://us1.discourse-cdn.com/flex022/uploads/dynamobim/original/3X/5/0/50d29996f04d014b56b4b20fba1be2b7a9fdb349.png)

---

<div class="post-metadata">

**Author:** ![G-G](https://avatars.discourse-cdn.com/v4/letter/g/2acd7d/32.png) [@G-G](https://forum.dynamobim.com/u/G-G)\
**Post date:** [September 10, 2025, 4:46am UTC](https://forum.dynamobim.com/t/tspline-node-tobrep-crashes-when-feeding-it-with-a-bad-t-spline/112224/5 "2025-09-10T04:46:23Z")

</div>

Hi Sol,  
Yes, I totally get that the body is invalid. 🙂 as mentioned, that can easily happen when handling complex list structures of curves. I got a working script which creates a valid TS body, and there I also get my wanted Nurbs representation. So my post here was all about the crash, as this means potential data loss (I sometimes forget to save my graphs before feeding input into such dangerous nodes 😉 ). Thanks!
