Export linked tracks to LDD from Ldraw?

[Alasdair Ryan]

I have a question for Superkalle or to any one else who knows the answer.

Can LDD Manager convert a MLcad/LSynth (linked) track into LDD,I assume that the the part names and coordinates need to be changed or is there more to it than that?

If it is at all possible to implement,then I think this would be a really handy feature to have for those people struggling with links of technic treads and chains or help speed up the work of the advanced user.

Edited August 6, 2014 by Alasdair Ryan

[Superkalle]

LDD Manager only reads LDD files, not MLCad.

But to do what (I think) you want, create the track in MLCAd, and then import the LDR-file (File > Import).

If you're lucky, it will work.

[Alasdair Ryan]

Ok, I tried what you suggested but I just got a empty building window (it still played the finished loading model sound).

That suggests that LDD is not recognising the part,although they share the same part number.

Would it be at all possible to make a new feature that could make LDD manager read MLcad chain/tread and convert it into a LDD?

Edited August 6, 2014 by Alasdair Ryan

[Calabar]

Before importing in LDD, you should update the LDraw.xml file: click.

[Alasdair Ryan]

Before importing in LDD, you should update the LDraw.xml file: click.

Thank you for the link,I tried both versions of the XML update but I am still getting a blank screen.

I have added the MLcad text below if any one wants to try it for themselves.

0 Untitled
0 Name: ldd test.ldr
0 Author: LDraw
0 Unofficial Model
1 16 -144 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -128.4 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -112.8 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -97.2 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -81.6 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -66 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -50.4 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -34.8 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -19.2 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -3.6 18 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
1 16 -160 18 -52 0 0.4339 -0.901 0 -0.901 -0.4339 -1 0 0 3873.dat
1 16 -174.073 11.2228 -52 0 0.9749 -0.2225 0 -0.2225 -0.9749 -1 0 0 3873.dat
1 16 -177.549 -4.0054 -52 0 0.7818 0.6235 0 0.6235 -0.7818 -1 0 0 3873.dat
1 16 -167.81 -16.2174 -52 0 -0 1 0 1 0 -1 0 0 3873.dat
1 16 -20 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -35.6 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -51.2 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -66.8 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -82.4 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -98 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -113.6 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -129.2 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -144.8 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -160.4 -18 -52 0 0 1 0 1 0 -1 0 0 3873.dat
1 16 -4 -18 -52 0 -0.4339 0.901 0 0.901 0.4339 -1 0 0 3873.dat
1 16 10.073 -11.2228 -52 0 -0.9749 0.2225 0 0.2225 0.9749 -1 0 0 3873.dat
1 16 13.5487 4.0054 -52 0 -0.7818 -0.6235 0 -0.6235 0.7818 -1 0 0 3873.dat
1 16 3.8099 16.2174 -52 0 0 -1 0 -1 0 -1 0 0 3873.dat
0
0

Edited August 7, 2014 by Alasdair Ryan

[Superkalle]

Created a sepate topic of this

[Alasdair Ryan]

Thank you I was a bit concerned it was going slightly off topic.

[Calabar]

Alasdair Ryan, did you tried to make a simple import using few common piece to test the import functionality?

[Alasdair Ryan]

Alasdair Ryan, did you tried to make a simple import using few common piece to test the import functionality?

No,but I just tested it with a 1 stud brick and got nothing upon loading it in LDD.

Edited August 7, 2014 by Alasdair Ryan

[Philo]

In addition to "simple" import issues, I see two other potential problems; your track uses "main color" color 16 which doesn't map to a LEGO color. You should rather use black... The other issue is that if you look closely at your track, there is a slight overlaps between elements. LDD collision detection will probly choke on this...

[Alasdair Ryan]

In addition to "simple" import issues, I see two other potential problems; your track uses "main color" color 16 which doesn't map to a LEGO color. You should rather use black... The other issue is that if you look closely at your track, there is a slight overlaps between elements. LDD collision detection will probly choke on this...

I can change the colour of the tracks,but changing the overlapping tracks to a suitable distance might be a problem.

How much do LDD tracks overlap each other?

[Superkalle]

How much do LDD tracks overlap each other?

I think the only way is to give it a try and see.

Or you can manually edit the LXF-file and nudge a track-element a 10th of a milllimeter or so in various directions and see when it will be removed when opening the file. When it gets removed, you'll know you've bumped into a collision box

[Alasdair Ryan]

Thanks Superkalle,do you know of a tutorial that shows you how to move LDD parts around in a text editor?

I changed the colour to black,but it is still not showing anything up on screen.

I also just tried to import a single track piece from MLcad to LDD and I also got a blank screen, I also tried to export a track element from LDD to MLcad too which I got a blank screen on MLcad.

This would suggest that both LDD can't read the MLcad part and MLcad can't read the LDD part.

Now here is a thought,can LDD read sub parts to MLcad or is there some sort of extension that MLcad can not read that LDD uses?

Edited August 9, 2014 by Alasdair Ryan

[Classicsmiley]

Have you updated your ldraw.xml file? (The most recent version can be found here: http://gallaghersart.com/page/new_ldd_parts_and_the_ldraw.xml/ )

[Alasdair Ryan]

Yes I have.

[Classicsmiley]

Hmm. I was just able to export a file with a track link from LDD to ldr. I then duplicated the link a few times in MLcad, and imported the resulting file back into LDD with no problem.

[Alasdair Ryan]

I managed to got it working, although it did remove three links (the position of the template gears just need tweaked,nothing major).

Thank you to everyone who helped.

Edited August 10, 2014 by Alasdair Ryan

[Philo]

For our enlightenment, what was the problem that prevented import?

[Alasdair Ryan]

For our enlightenment, what was the problem that prevented import?

I think it was ether the wrong version of the XML file or because I was running a older version of LDD.