| |
Leonardo:
> > So what test do you run to determine what studs get removed?
>
> Basically it checks if a stud primitive is close to a "inverted stud"
> (the cylinders under a plate for example) or to some predefined points
> added by me and remove them. The original idea was to make the bricks
> really connect when they get close to each other, but I never got that
> far.
So in "every" part you have put a "stud-slot-point" in all
the places where a stud from another part can connect with
this part.
So if a stud on a non-transparent part is at the stud-slot
of another non-transparent part, it is obmitted.
And if there are non-transparent studs at all the stud-slots
of a non-transparent part, it's interior can be obmitted
too.
It could be a bit heavy, but mostly on the computer, and I
think it will work correctly for all "sensible" models.
Good thinking!
Play well,
Jacob
------------------------------------------------------------
-- E-mail: sparre@cats.nbi.dk --
-- Web...: <URL: http://hugin.ldraw.org/LEGO/Huse/ > --
------------------------------------------------------------
|
|
Message has 1 Reply:
 | | Re: L3PLiTE?
|
| (...) It does take some extra time to load a big file but the speed increase later is well worth it. After doing the initial calculations, you only need to check the studs for the bricks you move so it's very fast. Leonardo (25 years ago, 29-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
|
Message is in Reply To:
| | Re: L3PLiTE?
|
| (...) Basically it checks if a stud primitive is close to a "inverted stud" (the cylinders under a plate for example) or to some predefined points added by me and remove them. The original idea was to make the bricks really connect when they get (...) (25 years ago, 28-Mar-00, to lugnet.cad.ray, lugnet.cad.dev)
|
19 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
