0 Stud Underside Baseplate 0 Name: studbp1.dat 0 Author: J.C. Tchang [tchang] 0 !LDRAW_ORG Unofficial_Primitive 0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt 0 BFC CERTIFY CCW 0 !HISTORY 2009-12-02 [tchang] For Hight Quality Underside Baseplate 0 !HISTORY 2010-04-04 [tchang] Rename t16i3333 to t01i3333
Size: 629 bytes
Submitted by: tchang
t16i3333.dat is missing on the PT as is it also not official.
I wonder why the top stud hasn't been added into this file.
Leaving it out from this file doubles the size of the
parent parts (they have to each time add the top stud
and the bottom stud separately). Would the stud.dat be contained
in this file, then the size of the parent parts would shrink
to ca. 50%.
I think that the reason for leaving away the stud.dat was
that some baseplates need a normal stud there, and some
need one with the central white dot pattern.
This issue can be solved more easily and efficiently by
creating two variants of THIS file, one containing a normal stud,
and one a patterned one.
I'd rather have no top studs but instead use stugN.dat files in the baseplates. Not sure, but there might be baseplates out there that have an understud and no top stud at certain spots. You never know.
(my above suggestion implicitly implies
that for baseplates, also stug* parimitives get created
that both contain top _and_ bottom studs)
This is physically not possible, see the geometry of this file:
the bottom stud has a depth that pokes through the top surface.
Oh yes, of course. Someday I should go get my brain accelerated..
Let me summarize my refacturing proposal for the current
p/studbp1.dat ... p/studbp3.dat:
(A) Replace the current p/studbp1.dat ... p/studbp3.dat
by a single file
which contains the top as well as the bottom stud.
which is the same as studbp.dat, but has a white spot pattern.
This way, files studbp.dat and studbpp01.dat
become analogous to stud.dat vs. studp01.dat
(C) Optionally, add a "coarse" version of (A) and (B).
That "coarse" version could leave out the bottom stud detail
to speed up rendering time.
(D) Add baseplate stud group files like
which would be the studbp.dat analogons to the normal stug files.
(E) Refactor JC's *h.dat baseplate versions as follows:
- delete the *h.dat duplicates of the normal baseplates
- refactor the normal baseplates to use the primitives
created in (A)-(D)
This way the following is achieved:
(1) the memory storage structure of the baseplates is much more effective
as JC's current solution
(2) the redundancy of the current p/studbp1.dat ... p/studbp3.dat is avoided
(3) the user can still choose whether he wants to see/render the bottom
studs or not
(4) the baseplate studs have more systematics with the current files
As JC has created his baseplate versions using a script,
it should be fairly easy to refactor them to use the
new, proposed primitives above.
I like the suggestion of Steffen. It is consistent to our other stud primitives.
Works for me.
Submitted by: tchang
Sorry for tore name.
Existing certification-votes were deleted.
restoring hold for mentioned issue above
This concept needs more thought.