topic PRISM_ status codes are confusing in GDL

PRISM_ status codes are confusing

Laurentiu — Tue, 24 Sep 2024 08:22:20 GMT

Hi,

I'm trying to understand how status codes work and in general they seem easy enough in principle.

Yet when applying them to a PRISM_ they seem to work in a very non-intuitive way.

Here is a small test that I have made.

Firstly, we have a small circle.

I wanted to test how changing the status codes influences the edge visibility.

I quickly discovered that changing the status code from line 6 (the one where the circle is defined) doesn't do anything for the edges. Instead I have to change the status code at line 5, which should only define the centerpoint.

The reference guide (at Full circle using centerpoint and radius chapter) also suggests that the second SC is the one that refers to the whole circle, so I would assume that this is the one that influences the edge visibility.

So shouldn't it be the the other way around? The centerpoint status code shouldn't do anything and only the second status code should change the edge visibility?

Ok so secondly, even more confusing, is trying to cut out a circle out of a small prism.

In this case, neither of the two lines of code that actually deal with the circle don't influence it's visibility.

Instead, only the status code for the last edge of the prism (line 18) is that one that actually influences the edge visibility for the circle.

It feels like I am missing something about the way cutouts should be defined.

Can someone elighen me on how all of this works?

Re: PRISM_ status codes are confusing

runxel — Thu, 23 Nov 2023 21:34:22 GMT

It's not so easy with round things, as you already saw.

It gets even more complex if you have a round hole in a round plate:

put \ rad_, 0, 79, 0, 0, 900, 0, 180, 4000+79, 0, 180, 4000+79, rad_, 0, -1, !// end of round base plate rad_inner, 0, 600+79, !// start of hole 0, 180, 4000+79, 0, 180, 4000+79, rad_inner, 0, -1 prism_ nsp/3, ZZYZX, get(nsp)

The trick is to not use full circles but arcs (half circles).

This allows us to define start and end points, which are necessary to put in all the status codes in right order affecting the right things.

Hope that helps!

Re: PRISM_ status codes are confusing

Laurentiu — Fri, 05 Apr 2024 21:00:16 GMT

It took a while, but I did find my answers after watching this video from Barking Dog BIM.

So the answer to my question is that the previous coordinate line changes the way the hole is displayed, not the actual line that describes the hole. It's still a bit unintuitive for me, but that's how it works. Bruce explains it at about 7:50 in his video.

Another weird thing that I found hard to figure out is how to change the display of the first hole when multiple holes are defined in a prism_. You basically have to apply the same logic of changing the status code of the previous lines before each hole. He also explains and exemplifies it at about 18:35.

Lastly, because of fiddling with so many status codes you'll inevitably end up with a missing corner edge of the prism that can be restored by simply adding a dummy coordinate line that won't interfere with the prism's contour. Go to 20:30 for at the video for that explanation.

I hope this helps anyone else in the future that might also find status codes confusing for prism_ .