 | | Re: POV in Part
|
| (...) Here's a small program to dump the file out as text so we can examine the unknown 8 bit value. It looks to me like it contains some flag bits. Only 3 bits seem to be used (0x01, 0x02, and 0x80). From the output it appears as if bit 0x80 (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
| | | | | Re: POV in Part
|
| (...) Yes, L3P would automatically support new LGEO parts if they were added to the binary l2p_elmt.tab. (...) You can use the -d option to L3P to see the contents of LGEO's *.TAB files: l3p -d -lgeo somefile.dat | more (mentioned a couple of years (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
| | | | | Re: POV in Part
|
| Could folks please trim lugnet.admin.suggestions from this thread? Frank (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
| | | | | Re: POV in Part
|
| (...) Are there any significant differences between the two libraries? I assume they both use solid modeling, not surface modeling. I don't think either library offers rounded edges on bricks (something I still miss from the L3G0 library). I've only (...) (21 years ago, 21-Jun-03, to lugnet.cad.dat.parts)
| | | | | Re: POV in Part
|
| (...) My library is currently being rebuild and all buttons on the bricks are getting a selectable rounded edge, they take up a whole extra amount of rendering time so I've made them an option. Also, I've always looked at new Lego(TM) and there are (...) (21 years ago, 20-Jul-03, to lugnet.cad.dat.parts)
| | | | | Re: POV in Part
|
| (...) I might be imagining things, but the macro'ed baseplate parts seemed to render *excrutiatingly* slowly when I working on the LDraw2Raves wrapper. This was in low-quality mode. I'm assuming that in model files, rendered in higher-quality modes, (...) (21 years ago, 29-Jul-03, to lugnet.cad.dat.parts)
| |
