 | | 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)
|
