 | | New part: Train Single Buffer [DAT]
|
|
0 Train Single Buffer 0 Name: x.dat 0 Author: Niels Karsdorp 0 BFC CERTIFY CCW 2 24 -10 0 -28 -10 0 20 2 24 -10 0 20 -10 4 20 2 24 -10 4 20 -10 8 12 2 24 -10 8 12 -10 8 -20 2 24 -10 8 -20 -10 23 -20 2 24 -10 23 -20 -10 23 -28 2 24 -10 23 -28 -10 0 (...) (21 years ago, 17-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: Patterns as subparts?
|
|
(...) Some patterns are like this already (the fire logo comes to mind immediately). However, finding these patterns can be difficult, as they're generally named after the first part that uses them. Could a file naming convention be setup so that (...) (21 years ago, 13-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Patterns as subparts?
|
|
I was thinking that certain patterns that are used often on many diferent pieces could be made into subparts. Something like the clasic space pattern (p90?) could be turned into a subpart and given a name coresponding to the pattern number. (21 years ago, 13-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | 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
|
|
(...) 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
|
|
(...) 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
|
|
(...) I agree to that, but since POV-code will be between IFPOV and IFNOTPOV codes will it matter that much? (...) There I disagree: the reason I ask is because of the macaroni-brick. I tried (fairly succesfull) to write the main part as POV-code (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts)
|
| |
| | Re: POV in Part
|
|
(...) Since L3P already supports the LGEO part library, is it possible to just add new LGEO parts and have L3P automatically use them? The only problem I see with this is that the .tab files in the LGEO library are binary files, but the format of (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, lugnet.admin.suggestions)
|
| |
| | Re: POV in Part
|
|
(...) I'm not too keen on this idea. While POV-Ray is a nice tool and freeware, I'd like to avoid dedicating ourselves to one tool, not to mention the size increase on all the files. If all you want is nice looking parts for POV try a combo of (...) (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts, FTX)
|
| |
| | Re: POV in Part
|
|
Steve Bliss <steve.bliss@earthlink.net> schrieb im Newsbeitrag news:70ncevsg5a3ulag...4ax.com... (...) I think we could, but where can I find the POV-code expressions? CU Bernd (21 years ago, 11-Jun-03, to lugnet.cad.dat.parts)
|
