This!
I have many large builds made in Stud.io that I don't want to rebuild.
I hope this is manageable when Mecabricks already have an LDD-import.

In fact there is a ldd import tool already in the workshop

@Blender4Bricks: Yep, that's what I wrote. But is is my large Stud.io builds I want to import, and when Mecabricks already have an LDD-import there's hopefully some similarities between the files and therefore doable to make an Stud.io import as well.
At least that's what I hope for 😃

Where it is complicated:

• First, I need to understand the format
• Secondly huge data work: Add conversion data (rotation and translation matri😆 for more than 3000 parts...

It's an zip archive with ldraw files inside (Password protected: soho0909)
You can then try to load the ldr into LDD and then import in Mecabricks.

As Scrubs mentioned, for the direct conversion from LDraw to Mecabricks, it's required to gather conversion data for each part individual. Also, part/color numbers may differ. It's something that cannot be done fast.

Thanks for the answers, and too bad it wasn't easily solved. Will try your technicue Sim 😃
Wish there was a "best-of-Mecabricks & best-of-Stud.io" version 😉
Some things Mecabricks does better and vice versa.
Love the new render farm by the way 😃

@Sim: Any information about the password protected zip-files would be much appreciated 😃

I've sent you a private message with the password. I'll be looking forward to the results. 😉

@Scrubs: Can you give me an example of how the Mecabrick-files look? The io-files is more or less a long list with transformation/translation data and shouldn't be that hard to parse. I'm a programmer myself and I'm curious if it is manageable 😃

I can handle anything. It doesn't have to be the mecabricks file format. The main issue is not really to parse the file but to have the conversion table to convert ldraw parts to mecabricks as origins and orientations for parts are different in both systems.

Ah, that's a bummer. Thought it would be enough with parts- and color-tables.
But it worked to import the ldr-file in LDD first and then import the LDD in Mecabricks. Positions and colors where correct in both LDD and Mecabricks. Lots of bricks where filtered away in LDD though when LDD doesn't have them. And I guess Mecabricks does the same when it imports from LDD.
I did this way with "10260 - Downtown Diner" and I lost about 100 bricks along the way. But the rest was actually quite accurate 😃

Missing parts indeed go bye bye in the conversion of LDD to Mecabricks. 😃 You can only check the missing parts in the developer console. There's no message given when the import finishes.

The system used to convert LDD files to Mecabricks can be reused, I think, to handle Ldraw to Mecabricks? You might have to give it a try, Scrubs? 😃

I believe that you can export stud.io builds to LDD, and then from LDD to Mecabricks. Obviously, you will lose a few parts along the way... 😛
Tell me if I'm wrong.

LDraw importer is now available in the workshop. Sim and Sealund are currently working on the huge task of populating the database.

Woohoo! Scrubs' 1600th post! Loud Clapping and Cheering 😄 😄 😄 😄 😃 😉

Sorry, that was off topic.

@Sim could you please provide stud.io zip password also to me? Need to fetch thumbnail.png from it 😃

Sent, good luck! 😃

@Sim: Sorry to bother you, but I'd also really like the stud.io zip password. I have some conflicted files due to an online sync tool, and need to compare contents... Thanks!

Heh, found the password elsewhere, immediately after posting above message, of course. 😃

anybody know how to import from mecabricks to stud.io?