 | | When is the next parts release?
|
|
Even without Steve going over the 30+ parts ready for him to certify, this looks to be the biggest release ever in terms of total file count. If all the redone primitives get certified, that will at least another 15 files that were already certified (...) (23 years ago, 12-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Implicit face winding (was: [Parts Tracker] More BFC Primitives)
|
|
(...) My bad- I guess I wasn't following the thread closely enough. (...) If I understand correctly, that doesn't really work for a huge percentage of parts. Parts will often have two surfaces in a row that both face away. Look at the breakdown of a (...) (23 years ago, 12-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Implicit face winding (was: [Parts Tracker] More BFC Primitives)
|
|
Tony Hafner wrote: > In lugnet.cad.dev.org.ldraw, Kyle McDonald writes: >> >>Well I don't know that I thought it would be 'minimal' effort. I'll >>bet it would be a lot of work for parts that are already done. I >>did think that it wouldn't be that (...) (23 years ago, 12-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Implicit face winding (was: [Parts Tracker] More BFC Primitives)
|
|
(...) I recently went over some old primitives and brought them up to BFC certification. I found it very handy to have the flexibility of doing it whichever way had more "correct" surfaces. It wouldn't be so bad if Notepad had the ability to reverse (...) (23 years ago, 12-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: [Parts Tracker] More BFC Primitives
|
|
Hi Travis, (...) Well I don't know that I thought it would be 'minimal' effort. I'll bet it would be a lot of work for parts that are already done. I did think that it wouldn't be that bad for new parts, because I figured the author knows best what (...) (23 years ago, 11-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: [Parts Tracker] More BFC Primitives
|
|
(...) Despite being the author of a rendering program, I agree with this whole-heartedly. Each rendering program only has to get it right once, during the initial coding. If we make it easier for the program, but harder for part authors, the part (...) (23 years ago, 11-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: review: Radeon 7000 for BrickDraw3D, low-end Mac
|
|
(...) Cool! If you can clearly show where you make the changes, I might be able to port this back into the other versions. I've never been all that happy with the rendering speed myself. You can see in the code where I tinkered a bit with display (...) (23 years ago, 11-Apr-02, to lugnet.cad.dev.mac)
|
| |
| | Re: Parts as volumes (instead of surfaces)
|
|
(...) "marking up" would be better done by machine algorithm, and would encompass the Connection Point proposal at the same time. It would indeed yield a separate definition of the parts. A lot of high-end CAD programs read polygons (like we have) (...) (23 years ago, 11-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Parts as volumes (instead of surfaces)
|
|
(...) Maybe I'm missing a technical distinction, but it seems he used bounding boxes *for* collision detection, as opposed to using exact volumes. (...) True. My point was, marking up the LDraw part files for volume decomposition would either: a) Be (...) (23 years ago, 11-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | review: Radeon 7000 for BrickDraw3D, low-end Mac
|
|
Upgrading my stock Apple G3/233 with a Radeon 7000 gave BrickDraw3D an 85% speed improvement. In pure OpenGL mode the improvement is 60% over the existing OpenGL advantage. The 2002 ATI Retail Card Update worked on G3/233 with 9.1 but BrickDraw3D (...) (23 years ago, 11-Apr-02, to lugnet.off-topic.geek, lugnet.cad.dev.mac)
|
| |
| | Re: matching pattern numbers???
|
|
(...) Sure, send it on. Steve (23 years ago, 10-Apr-02, to lugnet.cad.dev)
|
| |
| | Re: matching pattern numbers???
|
|
(...) That seems perfectly reasonable. (...) Cool! Thanks! :-) (...) [snip] (...) Very nicely done, sir! ;-) I've got some of the new (2002) 'figs, so would you mind if I give you more info for this list, or else use your info in a list of my own? (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev)
|
| |
| | Re: Parts as volumes (instead of surfaces)
|
|
(...) Well, I can have a twisted mind sometimes. I know these moments when the best idea today, will just be plain stupid tomorrow. Thanks to Eric Olson for more precision: he used bounding boxes, not collisions. Also I still think, whereas higher (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Han Solo "gunbelt" hips/legs (was "matching pattern numbers???")
|
|
(...) As promised: Minifig Hips & Legs with SW Gunbelt Pattern (Complete) (URL) Hips with SW Gunbelt Pattern (URL) Leg Right with SW Gunbelt Pattern (URL) (23 years ago, 10-Apr-02, to lugnet.cad.dev, lugnet.cad.dat.parts)
|
| |
| | part(s) posted... (set #4817)
|
|
I went with pattern number "4f", since "4b" has been taken by some other torso. Minifig Hips & Legs with Leather Armor Pattern (Complete) (URL) Hips with Leather Belt (Red Studs) Pattern (URL) Leg Right with Leather Straps (Red Studs) Pattern (URL) (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev)
|
| |
| | Re: Parts as volumes (instead of surfaces)
|
|
(...) That was only bounding boxes (minus the studs). The piece in question was matched against all other pieces, any pieces in a line above or below were put into a list. In case one of them intersected the piece in question, a new place would be (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: Parts as volumes (instead of surfaces)
|
|
(...) So stud4 would be decomposed into 16 trapezoidal prisms? That sounds like a fair amount of mark up. (...) Nod, true. But I'd rather decompose a 1x1 brick into 6 volumes (4 walls, 1 top and the stud) than 46 (one volume for each surface (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev.org.ldraw)
|
| |
| | Re: matching pattern numbers???
|
|
(...) When reasonable, yes, we should. If I make the Johnny Thunder face today, but don't make his torso for a couple of years, I wouldn't expect that the same pattern number will necessarily be available later. There are too many patterns for that. (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev)
|
| |
| | Re: matching pattern numbers???
|
|
(...) This sounds like a sensible suggestion. The change should of course be made, so there are only minimal (if any) changes to the names of already published parts. Jacob (23 years ago, 10-Apr-02, to lugnet.cad.dev)
|
| |
| | matching pattern numbers???
|
|
For patterned parts that occur together in a set -- say, for example, the various patterned parts from a Han Solo minifig (from the Star Wars theme) -- that have been or are being encoded as LCAD data files, shouldn't we be co-ordinating these (...) (23 years ago, 10-Apr-02, to lugnet.cad.dev)
|
