| |
Here is the current Ldraw.xml.
To install go to \LEGO Company\LEGO Digital Designer\Assets Directory and look
for the ldraw.xml file. Back the file up or rename it and replace it with the
new file. Make sure it has the same format as you see it on the download page.
For some reasons it may add extra data that will make it not work.
While in LDD go to export, choose the .ldr file type, remove the .lxf after your
file name, and save. To import just import from .ldr.
Some of the pieces will be killed by bad translations and rotation’s still but
that list is getting to be a very small list.
This version has many Technic, Minifig, and other parts added and working. The
Beta version has NXT and other parts that are not work out yet. But will import
and export in same locations, just do not correct the parts locations between
imports and exports. 1 version will work, the other will have parts moved and
rotated in whacky was.
Only working parts.
http://www.brickshelf.com/gallery/mikeslego/LDD/ldraw.xml
Beta version (will have incorrect transformation’s, in progress)
http://www.brickshelf.com/gallery/mikeslego/LDD/LdrawXML-Beta/ldraw.xml
I would like to thank all those who have contributed to this. And I hope I did
not leave anyone out but,
LDraw
LDD
Jason Railton
Timothy Gould
Willy Tschager
David Eaton
Michael Heidemann
Orion Pobursky
Magnus Forsberg
I will be keeping these files up to date as we make fixes. So check back when
you need, we may have you part fixed. Once a good size has been updated I will
post again. Rather not post for every part fixed.
Enjoy!
Mike Gallagher
GallaghersArt.com
|
|
| |
"mike Gallagher" <gallaghersemail@yahoo.com> wrote in message
news:K3AFKu.1IH@lugnet.com...
> Here is the current Ldraw.xml.
>
> To install go to \LEGO Company\LEGO Digital Designer\Assets Directory and
> look
> for the ldraw.xml file. Back the file up or rename it and replace it with
> the
> new file. Make sure it has the same format as you see it on the download
> page.
> For some reasons it may add extra data that will make it not work.
Does this file include the 973 parts/colors included in the latest Factory
palette? At last minifigs finally have weapons to wield in the Factory
palette!
> I will be keeping these files up to date as we make fixes. So check back
> when
> you need, we may have you part fixed. Once a good size has been updated I
> will
> post again. Rather not post for every part fixed.
When I open that link, it pops up as an HTML page with a lot of bolded
markup text representing commands. Is this supposed to happen, or do you
need to do something like encode it into an archive format? It does say
"ldraw.xml" at the top of the window, but I like to be careful before
messing with the unknown.
While on the subject of the file itself, you appear to have commented out a
duplicate entry of 30377.dat - it's still in the file though, just the
transformation line appears first as a comment, then as the proper
transformation line itself. There are a few other entries in the file like
that fortunately there's very few. Like below, if the cut/paste was
successful:
<!-- <Transformation ldraw="30377.dat" tx="-1.6" ty="0" tz="0"
ax="-0.512724" ay="0.688642" az="-0.512724" angle="4.34772" /> -->
<Transformation ldraw="30377.dat" tx="0" ty="-1.51" tz="0.51" ax="-0.5"
ay="-0.70710678118654752440084436210485" az="-0.5" angle="4.34772" />
Also, a question: Does the "only working parts" file transform at all the
part LDD knows as "SPIRAL TUBE W.FLANGE"
Cheers ...
Geoffrey Hyde
|
|
| |
> Does this file include the 973 parts/colors included in the latest Factory
> palette? At last minifigs finally have weapons to wield in the Factory
> palette!
My beta has most but some are still not working in that file. The goal is to
have all the parts that are in LDD. But Minifig items are some if the hardest to
fix.
> When I open that link, it pops up as an HTML page with a lot of bolded
> markup text representing commands. Is this supposed to happen, or do you
> need to do something like encode it into an archive format? It does say
> "ldraw.xml" at the top of the window, but I like to be careful before
> messing with the unknown.
Depends on how you download it. You can right click on the file and save as,
View source and save as, but once your file is saved it should read "ldraw.xml"
as the file name / type, and look the same way as you see while viewing file in
web browser from my site. If you double click the file after you download it
should look identical as viewed on my site. And if you get an error while
exporting then you know something is wrong. It will work or not.
> While on the subject of the file itself, you appear to have commented out a
> duplicate entry of 30377.dat - it's still in the file though, just the
> transformation line appears first as a comment, then as the proper
> transformation line itself. There are a few other entries in the file like
> that fortunately there's very few. Like below, if the cut/paste was
> successful:
>
> <!-- <Transformation ldraw="30377.dat" tx="-1.6" ty="0" tz="0"
> ax="-0.512724" ay="0.688642" az="-0.512724" angle="4.34772" /> -->
>
> <Transformation ldraw="30377.dat" tx="0" ty="-1.51" tz="0.51" ax="-0.5"
> ay="-0.70710678118654752440084436210485" az="-0.5" angle="4.34772" />
This is a work in progress with others along with my self working on it. Some
parts seem to change with the versions of LDD updates, or have some real crazy
rotation matrixes like the 30377 part. It’s just for our notes.
> Also, a question: Does the "only working parts" file transform at all the
> part LDD knows as "SPIRAL TUBE W.FLANGE"
Have not used any tubes yet, nor attempted to fix yet. But if they are in LDD we
are working on it. We start with the quickest parts to fix, and as we near the
end we are left with all the parts that may take many hours each to correct.
Mike Gallagher
GallaghersArt.com
MIKESLEGO
|
|
|
