 | | 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 (...) (23 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 (...) (23 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 (...) (23 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 (23 years ago, 11-Jun-03, to lugnet.cad.dat.parts)
| | | | | Re: New parts - Aquanaut Door and Door Frame
|
| (...) Sorry, I missed it. :/ (...) That is correct. (...) My general rule is to always double-space before a single-digit dimension. I can't think of any situations where we've got three-digit dimensions, so the double-space rule should work. Steve (23 years ago, 10-Jun-03, to lugnet.cad.dat.parts)
|
|
