 | | Re: LDraw and the Track Designer (Was: Next show)
|
|
(...) A stand-alone utility could call LDraw (or LDLite) to produce the images, but extract the (port) information directly from the .DAT file. Calling into LDraw/LDLite is pretty easy -- both programs are command-line driven. The utility would have (...) (26 years ago, 16-Feb-99, to lugnet.trains, lugnet.cad.dev)
|
| |
| | Re: LDraw and the Track Designer (Was: Next show)
|
|
(...) Track Designer can already automatically rotate [1] and scale any new bitmap that you give it. I'm not sure why you would want to do this in an image editor? What are the weird artifacts that you are referring to when using magenta as the (...) (26 years ago, 16-Feb-99, to lugnet.trains, lugnet.cad.dev)
|
| |
| | Re: LDraw and the Track Designer (Was: Next show)
|
|
This sounds like an excellent idea, however I'm not sure how to implement it. If it were a built in feature of Track Designer it would require that the entire rendering engine of LDraw be built into TD. A bit daunting! If it were built into LDraw, (...) (26 years ago, 16-Feb-99, to lugnet.trains, lugnet.cad.dev)
|
| |
| | Re: Part Bug: 6540 Technic Steering Arm Large
|
|
The Steering Arms I have are clearly marked '6540'. So this is one of those cases where we ought to have an 'A' and a 'B' part? (That is, if anyone ever models the part with the pin socket connection?) Kim Fredrik Glöckner wrote in message ... (...) (...) (26 years ago, 16-Feb-99, to lugnet.cad.dev)
|
| |
| | Re: Non-TLG Parts
|
|
(...) Just generate the mesh once. The part-file would be static, with one rough/broken side. It's still a lot of work for just one element -- it'd be easier to take the existing part-file, and just break it in half. Steve (26 years ago, 16-Feb-99, to lugnet.cad.dev)
|
