 | | Re: Does LDD's LDraw importer actually work?
|
|
(...) Thanks Joshua. This is what I wanted to hear. I figured out what the problem is. The Mac version of LDD expects imported LDraw files to have Unix line endings (LF), and silently fails if the line endings are in another format. Ironically, it (...) (14 years ago, 25-Mar-10, to lugnet.cad.ldd, FTX)
|
| |
| | Re: Does LDD's LDraw importer actually work?
|
|
(...) FWIW, 1) I run LEGO Digital Designer 3.0.11 under Windows 7 2) I chose Creator Freebuild (shouldn't matter with this test) 3) I executed menu: File | Import 4) Picked exported.dat off my desktop (how I saved this text, using notepad) (note (...) (14 years ago, 22-Mar-10, to lugnet.cad.ldd)
|
| |
| | Re: Does LDD's LDraw importer actually work?
|
|
--snip-- (...) Well it's definitely not overlap then. I assume that both coloured 1x1s exist too... Did you try removing the superfluous fractional digits? I'm relying on hunches here and don't have LDD installed but I do remember weird problems to (...) (14 years ago, 22-Mar-10, to lugnet.cad.ldd, FTX)
|
| |
| | 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 (...) (14 years ago, 22-Mar-10, to lugnet.cad.ldd, FTX)
|
| |
| | 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 (...) (14 years ago, 22-Mar-10, to lugnet.cad.ldd, FTX)
|
