 | | Re: Does LDD's LDraw importer actually work?
|
|
(...) I've never had it properly confirmed but I'm fairly certain the problem with import is that the overlap detection is way too overzealous. Which means that when you read in a file it decides the parts conflict and can't be there. It's (...) (15 years ago, 22-Mar-10, to lugnet.cad.ldd, FTX)
|
| |
| | Re: The future of LDraw?
|
|
(...) How widespread a problem is that, though? I know that some parts do indeed have two numbers, but this would seem a glitch that should have been resolved eight or more years ago, no? I mean, when you can turn a brick over and say "Yep, it's a (...) (15 years ago, 22-Mar-10, to lugnet.cad)
|
| |
| | Does LDD's LDraw importer actually work?
|
|
I recently had a Bricksmith user write asking for help importing an LDraw file into LDD. (He was using LDraw because LDD made it very difficult to build his model.) But when he attempts to import the LDraw file, he sees at most the first brick of (...) (15 years ago, 22-Mar-10, to lugnet.cad.ldd, FTX)
|
| |
| | Re: Developing LDBoxer Again
|
|
(...) Thanks, Tim! Along with a couple of bug fixes, support for the two other categories is now implemented. Right now, I'm creating the studless parts for the \B folder. Without them, LDBoxer would still not be able to boxer them. /Tore (15 years ago, 21-Mar-10, to lugnet.cad.dev)
|
| |
| | Re: Developing LDBoxer Again
|
|
(...) --snip-- (...) This sounds like an excellent development. I had to hand alter some of my Boxer'd MOCs to get the bottom detailing back in. And I think I forgot some. Tim (15 years ago, 21-Mar-10, to lugnet.cad.dev)
|
