M2m

Fixed 20460 and 20461 https://raw.githubusercontent.com/sttng/LDD-New-Parts/master/Primitives/20460.xml https://raw.githubusercontent.com/sttng/LDD-New-Parts/master/Primitives/20461.xml They missed correct values for faces and subMaterialRedirectLookupTable

@jester @Stephan I just wanted to say that this initiative really made my day. I feel like Christmas and birthday happening at the same time !

Nice ! Thanks @Stephan You may want to include in your parts set :)

@jester That video is great. Easy to follow these steps. @polymaker Ever considered a Blender Plugin for exporting g. files ? Not sure if it feasible, thought. Anyway I hope you can release an updated version of your cool tool. I may run a virtual Windows just to use it I just released an update of LegoToR - my LDD to RenderMan and USD converter with initial support for custom bricks: https://github.com/sttng/LegoToR/releases/tag/v0.5.0.7

Yeah I see. Maybe I give Swift a try, luckily you released the source, and I may look into converting it into Swift. Great Tutorial ?? Keep up the amazing work.

He is using a program called Brick.Creator.v0.1c-alpha (which was developed by Polymaker by the way) - its in the google drive jester shared. And also of course in the github of Polymaker who developed it originally, https://drive.google.com/drive/folders/1TvqeAikmMU0THUCc0a4YNScICgjd7kiV Basically to transform a single colored part into a multi colored one would mean to break up on .g file into multiple .g .g1 .g2 etc files (one .gX file for each different color). It should be relatively straight forward with a 3D editor and I assume Brick.Creator.v0.1c-alpha can do that. I can't test myself because I am on macOS. @Poly do you think you can make a more current release ? Also a macOS Port would be great (one can dream ) Cheers

Have 2 fixes (Fixed connections on the top): https://raw.githubusercontent.com/sttng/LDD-New-Parts/151e317d57455abd1d48fab2152b722875a68213/Primitives/65426.xml https://raw.githubusercontent.com/sttng/LDD-New-Parts/151e317d57455abd1d48fab2152b722875a68213/Primitives/65429.xml

No problem. You must first go to the folder where you downloaded the file in terminal. most likely it’s in your downloads folder. So first: cd ~/Downloads Then: python LIFExtractor.py /Users/Toitoine/Library/Application Support/LEGO Company/LEGO Digital Designer/db.lif I know being new with terminal / command line is a little bit complex

Direct link to py file https://raw.githubusercontent.com/sttng/LIF-Extractor/master/LIFExtractor.py

You would need to add UV mapping coordinates to the .g files. Unsure if the current .g converter supports that. Details of the .g (geometry format): https://github.com/sttng/LDD/blob/master/doc/g-file-format.md

Hi Toitoine. Get LIFExtractor.py https://github.com/sttng/LIF-Extractor run the python script from command line: python LIFExtractor.py /Users/YOURUSERNAME/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/db.lif Then copy the files of the pack into the respective subdirectories of the created db folder: /Users/YOURUSERNAME/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/db/ Thats about it On another note I am making progress to get the new parts working with my LDD to Renderman converter.

I’m using the new parts in LDD on OSX / macOS and it works smoothly. There is LIF extractor on macOS in form of a python program.

I think we would need a specific male connector type for the Duplo Studs to allow 2x2 bricks to be placed but for ex 2x2 plates not. With the existing types I don’t see that possibility.

I don’t think LDD has the right connection Types to support Duplo. I am only aware of these connection types: https://github.com/sttng/LDD/blob/master/doc/Custom2DField.md

That looks amazing ! I think the cumulatively number of times a part is used per set until now. (For ex part number 58011 is used 155 times in 70 sets until today) may provide a good indication of its usefulness.

So I guess that LDD misses around 2600 parts (with dates) all together. I think LDD has ~4400. Is it possible to gather which ‘most useful’ or most used parts are missing ? I think this would be helpful.

Does that mean that for ex LDD misses approx 300 parts of the 1600 used in 2020 ?

I guess you know this document already https://github.com/Polymaker/ldd-modder/blob/v2/Documentation/G (mesh) file structure.md Seems the Round edge shader data is not that good understood yet :-(

Oh ok. Didn't know that. Thanks ! Seems the new parts are missing bricks outline information. I don't thinks its a big issue, just to let you guys know. You can see in the picture (left part is original from LDD, right is new ones)

Question: How is the new added part 40811 different from 4081 (which is already existing in LDD).

Any tutorials on how to create parts ?

I’d vote for monorail parts !

The 100MB limit isn't an issue unless 1 brick is bigger then that (doubt it). I created an example github repository just to show you how I would set it up. Just with all the files and folders. At the right the green clone/download button would be to get the most recent version. https://github.com/sttng/LDD-New-Parts Feel free to ask any questions surely. :)

By the way I had a typo. you can create releases. A release would then automatically pickup ther version of a file (part) of the time the release is created. For ex. release 0.9 from 1st of May has all parts (and those versions) of 1st of May. Then 2 weeks later release 0.95 has all parts and those versions, etc. Versions and releases are features of github I really value. Plus of course you can go back to an earlier version (if you need to because a newer version introduces bugs). Per file limit is 100MB.

Found out this is the thread to discuss: Stephan! Great work ! May I suggest to put all parts on github ? That has several advantages: - you get version control for all files (parts) - you can’t create releases for the full enhanced library addition any time you like - people can fork it, create fixes, enhancements and then pull requests which you can then review to be included in your official curated enhancement pack. Additionally maybe it’s possible to give your parts lib a version name (similar to original LDD lib. version) but with a ‘mod’ indicator. That may help if we can use this lib in the official sets thread. Like part lib brick version 2670mod20200515 (or whatever you like) Once again. Congrats !