 | | Re: Does LDD's LDraw importer actually work?
|
|
(...) This is the file that LDD exported: 0 exported 0 Author: LEGO Digital Designer 3.0 1 71 -190 -24 -190.0000152587890625 1 0 0 0 1 0 0 0 1 3005.dat 1 14 170 -24 210.0000152587890625 1 0 0 0 1 0 0 0 1 3005.dat The two bricks are about 20 studs (...) (15 years ago, 22-Mar-10, to lugnet.cad.ldd, FTX)
|
| |
| | Re: The future of LDraw?
|
|
(...) First, let me make it clear that I am not a supporter of this policy (the fact that I have to write "policy" makes me feel a tad ill, to be honest). I was reporting, not defending. You quoted the most relevant portion of what I wrote. "The (...) (15 years ago, 22-Mar-10, to lugnet.cad)
|
| |
| | 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)
|
