Grasshopper two lines overlapping don’t understand why

Hello, I dont really understand what i’m missing why there is two line overlaping ? If you see any problem in my script i would be happy to understand why !
Thanks (11.2 KB)
Menuiserie.3dm (2.9 MB)

Simple, once I determined what parts of your code were relevant (I deleted the rest). You need to graft the Move ‘Geometry’ output in this image: (9.2 KB)

You could have internalized the curve instead of requiring the 2.9 MB Rhino file. If you don’t know what “internalize” means in GH, please ask.

P.S. Your other recent thread was also about grafting - I guess you don’t understand it yet?


Ahah i was not that far but couldnt find out what was the problem :D.
I ask then i dont know how to internalize and i didnt know it was even possible !

3. Attach minimal versions of all the relevant files
If you have a gh file you have a question about, attach it to the post. Do not expect that people will recreate a file based on a screen-shot because that’s a lot of pointless work. It’s also a good idea to remove everything non-essential from a gh file. You can use the Internalise Data menu option to cut everything to the left of a parameter:

Oh thanks really cool !

I’m still trying to developpe this script and when i sweep1 around this curve its not working :confused:
Menuiserie_1a.3dm (3.3 MB) (10.0 KB)

There are so many things wrong with your recent GH file… Please stop throwing mud at the wall. :man_facepalming:

  1. As before, you could have internalized geometry instead of requiring a 3.3 MB Rhino file.

  2. Boundary makes no sense when you already have a surface.

  3. Then you use Explode Curve which converts the surface to a curve, which you already had.

  4. I see no reason to graft Move ‘Geometry’ output.

  5. DivLength works as expected only because each curve fragment is evenly divisible by length.

  6. DivLength ‘t’ output produces four branches, one per ‘C’ input. You then pass those branched ‘t’ values to Shatter without grafting its ‘C’ input.

  7. Scale works to shorten the line fragments but a better (?) way is Extend Curve with negative values for ‘Start’ and ‘End’.

  8. After the purple group, you are grafting the branched curves for no reason. Examine the data trees before grafting!!

  9. The square section curve is wired to Deconstruct Brep for no reason.

  10. You are grafting both ‘A’ and ‘B’ inputs to Orient for no reason. In particular, it never makes sense to graft a single geometry (the section curve square).

  11. On the other hand, it is necessary to graft the ‘R’ (Rail) and ‘S’ (Sections) inputs to Swp1.

  12. Adjusting the Seam value to make Swp1 happy is tricky. Some values work and others don’t. (16.7 KB)