polymaker

@Stephan thank you Another reason that I would like a more detailed tracking system (like an excel/google sheet as you mentioned) is that I like to add support for culling in my parts (hiding portion of the mesh when connected to another parts). This is very optional because it only improves performance a little and does not affect how the part works, I mainly do it because I'm a bit perfectionist So in a excel-like tracking there could be a column to tell if the culling support was implemented. Also I was reading a bit on this thread and I found a discussion about adding authors into the files. I also had a similar idea and I think I found a way to write that information in the G files also. I have planned to add in my program a way to keep the authors and date of modification. This information could then be added to the xml when saving.

I'm a little late to the party but do you guys have a common list of currently created bricks? As I understands there is a couple of people that creates custom bricks but I was wondering if everyone is doing what they want or if it is a little organized. Because I have some parts made and I wanted to now if they were already made or if it is already made, maybe mine is more complete (outlines, collisions, etc). And more important, I don't want to start modeling and editing a brick that has already been done. For example on my github I recently started a tracker file that list the currently finished bricks and those that are in development (https://github.com/Polymaker/ldd-modder/blob/develop/LDD Bricks/readme.md) I also describe the progress like if only the model is done, if the collision and/or connections are missing. I think making a common tracking like this could be beneficial to all of us. With a system like that we could also list missing parts or issues with existing LDD parts.

An installer should be available soon on my github. Sorry for the absence I just got married and I haven't touched my PC for a while I'll let you know when it's ready. This can happen in some cases. Generating the outlines is very complex and my algorithm is not perfect. As a proof, even some existing parts in LDD have similar issues . I will add an option to export parts without outlines that will be useful when the result is too ugly otherwise,

This behavior is a feature intended to improve performance by reducing the triangle count when parts of the brick are hidden (e.g. when connected). This is specified in the last portion of the G file. This data also references the Custom2DField in the XML by index. So swapping the two Custom2DField (type 22 and type 23) will probably fix the issue. But may I ask where you got that part? Because generating that data is not possible with the converter people are using. My most recent and unreleased editor can generate this data but needs manual editing of the file because I have not yet finished the UI to input some needed parameters. I have made this part for myself with the alternate mesh feature (when connected) and it works properly. So I really wonder where you got it!

Wait what! Really? I was not aware! Good to know it was useful! But that version was something I whipped up real quick for someone that was a bit impatient. I had most of the code to read and write LDD parts for a while but I'm bad with UI and also I'm a bit perfectionist so I envisioned a full fledged 3D editor from the start but I did not have the knowledge and time to make it happen until recently. I agree that a release of the latest version is long overdue! I'm trying to make it stable enough so people with no coding knowledge can use it. About the MacOS thing... I share your dream man but I'm specialized with .Net and WinForma and the few cross-platform UI frameworks for .Net that exists are bad or cannot really achieve what I want.

@Kuramapika1 "Colorable" parts are the same as part with decals. They are the "g1", "g2", "g3" (etc) files. Each surface that can be colored or have a decal must be in a separate file. The format of those files is slightly different from the the "g" files as they include texture coordinates (even if decals are not needed). If your question was about how to make them yourself, it is not possible without a software or script to generate them.

Hey dude! I just discovered your work and I think you may be interested to know that I have made an almost complete editor for LDD parts. You can edit the model and connections at the same time and output the G and XML files directly into LDD primitives. I've managed to reverse engineer the whole G format and I can generate the data to render edges/outlines on the bricks. My software is still in progress but I have already made a bunch of missing parts (but not as much as you) I also managed to create flexible parts but only by script. If you are interested checkout my github project: https://github.com/Polymaker/ldd-modder/tree/v2

Nothings wrong... I've only activated DeveloperMode. When you active DeveloperMode, you can show 'hitboxes' by pressing 'V'. You can also toggle (collision) physics (it's how I placed the parts to take the screenshot), but I think re-opening the file will remove clipping parts, so it is not a solution. To enable DeveloperMode check http://ldd.wikia.com/wiki/Developer_Mode or http://www.brickwiki.info/wiki/LDD_developer_mode P.S. to moderators, enabling the DeveloperMode does not break TLG EULA right? Correct me if I'm wrong, I'll edit my post.

I have noticed that the icon for train parts have a strange shadow/border: Also, like many have mentioned, there are many collision problems, here's one I found while trying to build this Y-Wing (though I can't confirm if it's from the newest update) Here's why it doesn't work:

Well... I happen to have reverse engineered the LDD file format and I'm able to create custom bricks. So for now I'm the only one who has it, but I do hope that TLG release an official version. What are the part numbers? I don't seem to find the wheel hub. Is it from the unreleased technic Porsche?

This part?: Well I want it too and I'm working on making it...