|
|
| |
Just posted a new version of the LDraw.xml file that’s used to import and export
LDR files out of LDD. Please visit the
current LDraw.xml download page
to get the most current version. Enjoy,
Gallagher
|
|
| |
In lugnet.cad.ldd, Jaco van der Molen wrote:
>
> Does anyone have another solution for this?
>
> Jaco
I would create a temporary one line ldraw file that adjusts the origin by the
desired x, y, and z values, and then inline that file.
|
|
| |
In lugnet.cad.ldd, Jaco van der Molen wrote:
> Hello,
>
> When exporting an LDD file to LDraw the xyz position is slightly off the grid.
>
> What I do now is replace all dots with comma's, import the LDraw file in Excel,
> round all xyz coordintates on whole numbers, copy that to notepad and past in
> the LDraw file.
>
> This is a lot of work and in some cases this places some parts 1 LDU of the
> grid.
>
> Does anyone have another solution for this?
>
> Jaco
Could you send me a couple of samples of files exported to LDraw that are
slightly off the grid so I can see if there is any easy way to auto-adjust them?
/Tore
|
|
| |
Hello,
When exporting an LDD file to LDraw the xyz position is slightly off the grid.
What I do now is replace all dots with comma's, import the LDraw file in Excel,
round all xyz coordintates on whole numbers, copy that to notepad and past in
the LDraw file.
This is a lot of work and in some cases this places some parts 1 LDU of the
grid.
Does anyone have another solution for this?
Jaco
|
|
| |
On 31/12/2010 20:42, Anders Isaksson wrote:
> Wayne Jackson wrote:
> > How many versions are there of LDD currently available?
> >
> > I have 4.0.20 with brick set 287, but I am seeing on Brickshelf screen
> > shots of what appear to be LDD4 with train tracks, and 9V train
> > motors - none of these appear to be present.
>
> Have you activated "Universe mode"?
> http://www.eurobricks.com/forum/index.php?showtopic=40794
>
> This should give you access to all the 1400+ parts available in LDD.
>
>
Ah! Found it, but everything is red. I see a couple of posts
mentioning this though.
|
|
| |
Wayne Jackson wrote:
> How many versions are there of LDD currently available?
>
> I have 4.0.20 with brick set 287, but I am seeing on Brickshelf screen
> shots of what appear to be LDD4 with train tracks, and 9V train
> motors - none of these appear to be present.
Have you activated "Universe mode"?
http://www.eurobricks.com/forum/index.php?showtopic=40794
This should give you access to all the 1400+ parts available in LDD.
--
Anders Isaksson
|
|
| |
How many versions are there of LDD currently available?
I have 4.0.20 with brick set 287, but I am seeing on Brickshelf screen
shots of what appear to be LDD4 with train tracks, and 9V train motors -
none of these appear to be present.
|
|
| |
> In case you still need the answer...
> http://www.eurobricks.com/forum/index.php?showtopic=48123
Philo,
Thanks for the link. Alas it does not work.
Placing the ldraw.xml file in the same folder as ldd.exe does not let me import
LDraw files.
It seems that it does import, but then one is unable to place the model. In
fact: no element is placed at all!
I have contact with TLG atm about this issue.
Hope they solve it.
Jaco
|
|
| |
In lugnet.cad.ldd, Jaco van der Molen wrote:
> Hi all,
> After updating LDD to version 4, the import of an LDraw file does not work
> anymore :-( Anyone know how to fix this?
>
> It seems the ldraw.xml file is missing.
> The library in this new version is now one big .lif file, where as the previous
> version had a subdirectory in the LDD program folder called Assets that
> contained 9 .lif files and the ldraw.xml file.
Hi Jaco,
In case you still need the answer...
http://www.eurobricks.com/forum/index.php?showtopic=48123
Philo
|
|
| |
On 31/10/2010 04:53, Philippe Hurbain wrote:
> In lugnet.cad.ldd, Wayne Jackson wrote:
> > Not sure if it is just me, but has the new version of LDD gone a little
> > crazy?
> >
> > I have been trying to place a 4x4 plate on top of a square made with two
> > 1x2 and two 1x4 bricks, and it will not line up whatsoever. It has the
> > plate half a stud off each and every time.
> >
> > Have other experience this?
> I tried to reproduce the problem without success, all seems to work fine.
>
> Philo
If I restart the program, it works. Didn't have this problem with the
last version.
|
|
| |
In lugnet.cad.ldd, Wayne Jackson wrote:
> Not sure if it is just me, but has the new version of LDD gone a little
> crazy?
>
> I have been trying to place a 4x4 plate on top of a square made with two
> 1x2 and two 1x4 bricks, and it will not line up whatsoever. It has the
> plate half a stud off each and every time.
>
> Have other experience this?
I tried to reproduce the problem without success, all seems to work fine.
Philo
|
|
| |
Not sure if it is just me, but has the new version of LDD gone a little
crazy?
I have been trying to place a 4x4 plate on top of a square made with two
1x2 and two 1x4 bricks, and it will not line up whatsoever. It has the
plate half a stud off each and every time.
Have other experience this?
|
|
| |
Hi all,
After updating LDD to version 4, the import of an LDraw file does not work
anymore :-( Anyone know how to fix this?
It seems the ldraw.xml file is missing.
The library in this new version is now one big .lif file, where as the previous
version had a subdirectory in the LDD program folder called Assets that
contained 9 .lif files and the ldraw.xml file.
Jaco
|
|
| |
After today's update to LDD version 4 it doesn't work anymore... :-(
|
|
| |
In lugnet.cad.ldd, Allen Smith wrote:
> In lugnet.cad.ldd, Joshua Delahunty wrote:
> > FWIW,
<steps to use LDD to import under Winders>
> >
> > Hope this helps,
> >
> > -- joshuaD
>
> 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 exports CRLF as one would
> expect.
>
> If you convert the LDraw file to Unix line endings, it imports correctly
> (well, as close to "correct" as LDD provides with its finicky restrictions).
>
> Does anybody know how I can report this bug and actually have it get to the
> people it needs to get to?
I can do it. ;-)
I got to meet the architect for LDD at Brickcon.
Consider it done. :)
-- joshuaD
|
|
| |
In lugnet.cad.ldd, Joshua Delahunty wrote:
| |
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 that I couldn’t browse, LDD doesn’t recognize .dat as a valid extension,
but will load if it I type that in)
5) The two bricks (MS grey on the left, yellow on the right) are “attached” to
my cursor (this is how imported files come in), and I’m able to place them in
the scene.
Hope this helps,
-- joshuaD
|
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 exports CRLF as one would expect.
If you convert the LDraw file to Unix line endings, it imports correctly (well,
as close to “correct” as LDD provides with its finicky restrictions).
Does anybody know how I can report this bug and actually have it get to the
people it needs to get to?
Allen
|
|
| |
In lugnet.cad.ldd, Allen Smith wrote:
> In lugnet.cad.ldd, Timothy Gould wrote:
> > In lugnet.cad.ldd, Allen Smith wrote:
> > > 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 the model and nothing else.
> > >
> > > I verified this on LDD 3.0.11 for Mac OS X. If I export an LDD file
> > > containing nothing but 2 1x1 bricks not touching each other, LDD produces a
> > > valid LDraw file. Attempting to import said file back into LDD (with no
> > > changes) doesn't work. Sometimes I get only the first brick ready to place;
> > > sometimes I get nothing at all. In no instance do I get any error message;
> > > only the little import-finished bleep noise.
> > >
> > > Is this a Mac-only thing? Is it a problem with the latest version? I can't
> > > find any older versions available for download. My e-mail to Lego technical
> > > support hasn't been answered yet either.
> > >
> > > Thanks,¬
> > > Allen
> >
> > 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 irritating.
>
>
> 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 away from each other, so it's hard to
> imagine how it could possibly see any overlap issues there. On import, I get
> absolutely nothing except the bleep sound. No bricks, no errors.
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 that I couldn't browse, LDD doesn't recognize .dat as a valid extension,
but will load if it I type that in)
5) The two bricks (MS grey on the left, yellow on the right) are "attached" to
my cursor (this is how imported files come in), and I'm able to place them in
the scene.
Hope this helps,
-- joshuaD
|
|
| |
--snip--
| |
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 away from each other, so it’s hard to
imagine how it could possibly see any overlap issues there. On import, I get
absolutely nothing except the bleep sound. No bricks, no errors.
Allen
|
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 do
with the lack of rounding. I always assumed it was overlap testing but maybe
not.
Your other alternative is to just use the conversion file (Mike Gallagher has
the latest version http://news.lugnet.com/cad/ldd/?n=234 ) and write your own
converter or export function.
Not very helpful I’m afraid. Mike may have a better idea.
Tim
|
|
| |
In lugnet.cad.ldd, Timothy Gould wrote:
| |
In lugnet.cad.ldd, Allen Smith wrote:
| |
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 the model and nothing else.
I verified this on LDD 3.0.11 for Mac OS X. If I export an LDD file
containing nothing but 2 1x1 bricks not touching each other, LDD produces a
valid LDraw file. Attempting to import said file back into LDD (with no
changes) doesn’t work. Sometimes I get only the first brick ready to place;
sometimes I get nothing at all. In no instance do I get any error message;
only the little import-finished bleep noise.
Is this a Mac-only thing? Is it a problem with the latest version? I can’t
find any older versions available for download. My e-mail to Lego technical
support hasn’t been answered yet either.
Thanks,
Allen
|
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 irritating.
|
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 away from each other, so it’s hard to imagine
how it could possibly see any overlap issues there. On import, I get absolutely
nothing except the bleep sound. No bricks, no errors.
Allen
|
|
| |
In lugnet.cad.ldd, Allen Smith wrote:
| |
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 the model and nothing else.
I verified this on LDD 3.0.11 for Mac OS X. If I export an LDD file
containing nothing but 2 1x1 bricks not touching each other, LDD produces a
valid LDraw file. Attempting to import said file back into LDD (with no
changes) doesn’t work. Sometimes I get only the first brick ready to place;
sometimes I get nothing at all. In no instance do I get any error message;
only the little import-finished bleep noise.
Is this a Mac-only thing? Is it a problem with the latest version? I can’t
find any older versions available for download. My e-mail to Lego technical
support hasn’t been answered yet either.
Thanks,
Allen
|
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
irritating.
Tim
|
|
|
