 | | Re: Segmented parts (ie hoses and flex tubes)
|
| (...) This sounds like a good idea to me, except for one thing: the 0 LDRAW_ORG lines are generated at release-time by the release script. Every type listed is determined by other data in the file, or about the file -- parts are in the /parts (...) (24 years ago, 23-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
| | | | | Re: Viewing Datsville
|
| (...) The main file is Town.ldr The subfiles of Town.ldr are 15 separate sections, unfortunately not as modular as the Moonbase Project for example, and Townpeep.ldr with some people and vehicles. I have made a map over the Town??.ldr submodels: (...) (24 years ago, 23-Aug-02, to lugnet.cad.dat.models)
| | | | | Segmented parts (ie hoses and flex tubes)
|
| Looking at some of the files generated using the new curve generator LDDesignPad plugin by Orion (as well as files generated by the EMacs macro it is based on), I noticed a problem when displaying with LDView (which might also effect L3P output). (...) (24 years ago, 23-Aug-02, to lugnet.cad.dat.parts, lugnet.cad.dev)
| | | | | Re: Viewing Datsville
|
| (...) Is your Dasville renderable. I was looking through the files last night and nothing looked like the "main" file to render. The reason I ask is that I'm working on a program that will composite many different images into a single image. I'ld (...) (24 years ago, 23-Aug-02, to lugnet.cad.dat.models)
| | | | | Re: Viewing Datsville
|
| (...) I have no ftp access to the Datsville pages, and I don't think I want that either. The hours I spend on renaming, inlining, extracing, and tagging Datsville files is mainly to make it easier for myself to use them. Then why do I publish the (...) (24 years ago, 23-Aug-02, to lugnet.cad.dat.models)
|
|
