Duplo for Studio!

[Philo]

Many people asked for the possibility to use Duplo parts in Studio, so I created this parts pack (including connectivity): https://drive.google.com/open?id=1A1gE522bMrcER3hYjqd0CLbGPrvSlvoE
To use it, unzip it and place its contents in your C:\Users\{your username}\AppData\Local\Stud.io . Duplo parts will then be available in Custom Parts palette of Studio. More details on custom parts in Studio forum: http://forum.bricklink.com/viewtopic.php?f=4&t=965&p=2615&hilit=customparts&sid=a0487a9d7213c77248f4ce56001e5072#p2615

Caveats:
- Many Duplo parts are missing here (and are not available in LDraw library anyway)
- Studio doesn't provide specific connectivity for Duplo, so I had to make do with simple stud or axle connexions.
- Compatibility with regular LEGO is limited (you can place bricks over Duplo, but Duplo on bricks doesn't position correctly and generate collisions).
- Some parts create unwanted collisions, eg. Duplo wheel on axle. Problem is that Studio part designer generate collision data automatically, I have no control on this. Turn collision off when this happens.

 

[knotian]

You should repost this on the Stud.io forum

http://forum.bricklink.com/index.php?sid=f254c5d0c3730894acabbb726b069865

[Philo]

I already did ;)

http://forum.bricklink.com/viewtopic.php?f=6&t=2986&sid=7696d83f36f7fca78cdce4c67bbafc60

[knotian]

woops - missed it

[artic13]

On 10/14/2019 at 2:54 PM, Philo said:

Many people asked for the possibility to use Duplo parts in Studio, so I created this parts pack (including connectivity): https://drive.google.com/open?id=1A1gE522bMrcER3hYjqd0CLbGPrvSlvoE
To use it, unzip it and place its contents in your C:\Users\{your username}\AppData\Local\Stud.io . Duplo parts will then be available in Custom Parts palette of Studio. More details on custom parts in Studio forum: http://forum.bricklink.com/viewtopic.php?f=4&t=965&p=2615&hilit=customparts&sid=a0487a9d7213c77248f4ce56001e5072#p2615

Caveats:
- Many Duplo parts are missing here (and are not available in LDraw library anyway)
- Studio doesn't provide specific connectivity for Duplo, so I had to make do with simple stud or axle connexions.
- Compatibility with regular LEGO is limited (you can place bricks over Duplo, but Duplo on bricks doesn't position correctly and generate collisions).
- Some parts create unwanted collisions, eg. Duplo wheel on axle. Problem is that Studio part designer generate collision data automatically, I have no control on this. Turn collision off when this happens.

 

many thanks for sharing this works sir, its realy help specialy for teacher making instruction for their student to follow.

[1963maniac]

Thank you Philo!! I wish there were digital files for the two train bridge parts. I'm trying to layout my Duplo tracks with Bluebrick.

[Philo]

16 hours ago, 1963maniac said:

I wish there were digital files for the two train bridge parts

Parts need to be created first, and tracks are a hell to model ;)

[warlogon]

On 10/14/2019 at 10:54 AM, Philo said:

Many people asked for the possibility to use Duplo parts in Studio, so I created this parts pack (including connectivity): https://drive.google.com/open?id=1A1gE522bMrcER3hYjqd0CLbGPrvSlvoE
To use it, unzip it and place its contents in your C:\Users\{your username}\AppData\Local\Stud.io . Duplo parts will then be available in Custom Parts palette of Studio. More details on custom parts in Studio forum: http://forum.bricklink.com/viewtopic.php?f=4&t=965&p=2615&hilit=customparts&sid=a0487a9d7213c77248f4ce56001e5072#p2615

Caveats:
- Many Duplo parts are missing here (and are not available in LDraw library anyway)
- Studio doesn't provide specific connectivity for Duplo, so I had to make do with simple stud or axle connexions.
- Compatibility with regular LEGO is limited (you can place bricks over Duplo, but Duplo on bricks doesn't position correctly and generate collisions).
- Some parts create unwanted collisions, eg. Duplo wheel on axle. Problem is that Studio part designer generate collision data automatically, I have no control on this. Turn collision off when this happens.

http://www.brickshelf.com/gallery/Philo/misc2/duplo4studio.jpg

Hello, sorry, but I couldn't find any folders, arhives or files in the forum to donwload basic Duplo details like simple bricks on your screenshot. Could you please share it?

On 10/14/2019 at 10:54 AM, Philo said:

 

 

[Philo]

On 5/18/2025 at 1:00 PM, warlogon said:

Hello, sorry, but I couldn't find any folders, arhives or files in the forum to donwload basic Duplo details like simple bricks on your screenshot. Could you please share it?

 

It's all there... you just have to download the zip file, open it then drag/drop the folder in the right place. More details here: https://philohome.com/studio/packs.htm

[VesperA]

Hi @Philo,

Thank you so much for this work!

I'm currently trying to build some MOC in Studio with Duplo. I imported the library from your website.

I'm facing however an issue: I don't see the basic DUPLO bricks, only the ones with stickers.

I wanted to ask you if it was the intended behaviour or if there was an option I was not aware of?

I attached a screenshot where I'm trying to get the Brick 2x2, and only the options with stickers are being displayed.

Thanks again!

[SylvainLS]

For some unknown reason, some DUPLO parts are already in Studio’s part database.  There, there’s an association between a filename and diverse BrickLink and Studio info.  Some of these info have values that prevent them from showing in palettes (one example is the categories/shapes numbers that are unset or set to 0).

By construction, and for almost every undecorated part, the filename that’s there is the same as the filename used by LDraw.

So, when you make a custom part (like Philo did) and export it to Studio with its LDraw filename (like Philo did), Studio will use the matching entry in its database and the part won’t show in the palettes.

What that means is that one needs to rename all the files of custom parts to NOT be the same as LDraw filenames (and change all the references to other “custom” filenames inside the files).  One simple solution would be to rename all the files by adding “ld_” in front of them.

 

(The pack used to work.  It’s changes in 1. Studio’s database, 2. how custom parts are handled in palettes, that are causing this.)