Make 2D Rhino 6 Clipping Plane issue

Grasshopper
22

Filed a bug to look into it.
RH-58607 Make 2D Rhino 6 Clipping Plane issue

1 Like
23

:slight_smile: my first bug ever found

3 Likes
24

Hi Seghier,

I appreciatte your script, itā€™s very usefull. Iā€™m triying to keep some information structured as a tree and I donā€™t find a way to do it. Itā€™s possible to extrac transform information in your script ?? Since Iā€™m not able to keep the input tree structure, at least I can repeat your component and apply the same transformation to the remainder geometries.

Thank you for your attention to this matter, and have a nice day!

25

Make 2D donā€™t have transform output

1 Like
26

Thanks for your answer, I think Iā€™ll use an auxiliar wireframe from the object bounding box in order to have a defined bounds to transform 2d drawings. I think it will work.

Thanks again!

27

Hi @rajaa,
I just wondered if you could give an update on this topic for Rhino 7 - are there still considered to be issues with parallel Clipping Planes for the ghMake2D component (on RH-58607 it shows that it was fixed Jan2024 for R8, but Iā€™m wondering about R7)?
I came to this thread yesterday when I tried out ghMake2D and discovered that it didnā€™t seem to work for clipping planes parallel to the viewing plane (!!). But I later figured out that its logic is the opposite to Rhinoā€™s Clipping Plane (i.e. in ghMake2D, the clipping plane needs to face the part of the scene you want REMOVED, not kept) - since making the adjustment (with FlipPlane), I havenā€™t be able to get any buggy behaviour; so far it seems to work well even with a Front & Back Clip Plane, provided they each face the correct way and are passed to the input in the right order.
Can you (or anyone users that experienced problems) please give an update? Thx

28

@DavidRutten are there plans to update this for V7?

29

Hi @rajaa,
While waiting for David to respond, could you just tell me what the bug/issue is so that I can test for it? As I said in my last post, since flipping the plane orientations, I havenā€™t been able to trigger any more unexpected behaviour, but adopting the ghMake2D component would involve a lot of changes to my scripts, so I want to be sure it is stable beforehand. Thx
(for clarification: from what I can see in RH-58607, in 2020 David identified that dirty/invalid geometry was coming out of HiddenLineDrawing and adjusted his code to deal with it. Maybe that solved it (?) but then there must have been something else going on until it was declared ā€˜fixedā€™ in R8 in Jan2024 and I canā€™t identify what that is. Please advise)