polymaker

It seems like this is a limitation of LDD. The palette file format does not provide a way to specify which part instance to alter when the assembly contains many of the same part. I tested adding a refID attribute to the part in the palette to match the IDs in the assembly but it did not work.

You are correct. LDD use some connections as collision and it is the case with type 14 (1.5mm bars). If you remove this connection it will fit inside pins but you loose connection to 1.5mm bars. Type 7 is also used as a collision so if you change type 21 for type 7 it prevents connecting 1.5mm bars (type 15). Type 21 act the same as type 7 but does not collide with type 15. In case all those number are confusing, here is a small cheat sheet: type 6: 3.5mm bar holder type 7: 3.5mm bar type 14: 1.5mm bar holder type 15: 1.5mm bar type 21: 3.5mm hollow bar

Hi folks! As you may know I am the author of "Brick Studio", a tool for viewing and creating custom parts for LDD. I've been working on this project for a few years now and I'm really happy that I was able to make something that works and is simple enough to be used by anyone. I am amazed by the current community and what we managed to accomplish so far. I'm starting this thread because my software has still some issues and is missing a lot of basic features and I really could use some help. I don't expect anyone to help me code... even if my code was simple to understand (it is not) there are not a lot of you that have the knowledge to do so. But I could really use your input. The main difficulty I have is myself.. I have a hard time taking decisions and I always prioritize new ideas instead of finishing what I already started... For example, if I need to add a button/menu for a new functionality, I will fiddle around a long time just to find where I can place it or how to name it and I sometimes just abandon and move on without ever adding the functionality I'm also creating this thread to have general inputs on the software, like suggestions or issues/problems. I'm currently reworking the core of the application so it can leave the "prototype" stage and I need you help for a few points: The name "Brick Studio" is something I came up almost only as a placeholder. I was not aware at the time that there is other existing application with similar names. Should I stick with this name or I should find something more proper? I am polishing the text and messages and also adding French and German translations and I need some help with Lego vocabulary: How do you call "studs" in French and German (I'm French and I have no clue ) Are there proper terms for male and female studs? I use top/bottom at some places but for me "bottom studs" means studs at the bottom of a part, not the female connection (I hope you understand what I mean). Some data of the LDD model files (*.g) is related to the "tubes" under some bricks. Is "brick tube" a clear enough term? And how would it be translated to French/German? I am never sure if I should use the term Brick or Part. Some Lego parts are not technically bricks... Also how would you name theses 3D terms in French and German?: Model and mesh. Maybe I don't use theses terms properly but to me mesh is more related to the 3D data (vertices, triangles, etc) and model is a more global term (a model can be composed of multiple meshes) Bone. In 3D modeling, bones are used to define how a model is animated. In LDD it used for defining how a flexible part bends. All my 3D modeling experience is with English softwares. For me when I see "Os" (bone in French) it does not sound related to 3D modeling. For now I have used "Armature" (frame) in some places. That's all I can think for now. Any suggestion is appreciated.

@ProfessorBrickkeeper This is actually a "feature". My algorithm considers overlapped edges as fused. This is mostly to prevent generating outlines around decorable surface that are coplanar with non-decorable surfaces (e.g. the face of a minifigure head). I plan to add more control over this process in brick studio but currently you will have to use a little trick (found by @Stephan IIRC): Simply pull apart the model in brick studio so each surfaces to outline are separated, then generate the outlines and then put them back to their original positions.

Yes you are right. I didn't think of that Anyway here is the list so far: part id => replaced by 30007 => 4215 32239 => 6588 41070 => 32008 45173 => 42060 46212 => 2454 47577 => 93565 52035 => 89536 57722 => 71986 59577 => 57558 60677 => 55676 60700 => 6015 61988 => 53788 63021 => 62699 63153 => 61804 64871 => 32278 82610 => 4034 86210 => 60603 86209 => 60601 88513 => 53451 88701 => 87777 89500 => 85961 There is another set of part IDs that are checked but those are not replaced by another ID, rather they seem to have a special behavior. I'll post what I find.

Well... I've reverse engineered LDD and I just found out that there is a bunch of hard-coded "aliases". I've stepped through the loading of a model file with the part 46212 and I stumbled upon this It translate to: compare memory value to B484 (hexadecimal for 46212) if the memory value is equal replace memory value with 996 (hexadecimal for 2454) otherwise continue There is a bunch of other comparisons. I will try to make a list of them all. Also I might be able to create a patch for LDD to prevent this behavior. I don't have a lot of experience doing so but I know it is possible.

@suenkachun About the supported decorations size & ratio, I'm might be wrong but I'm pretty sure that it has to do with OpenGL more than LDD. LDD uses an old version of OpenGL and it is known that it does not handle well textures (images) with sizes that are not power of two (e.g. 128, 256, 512) This would explain why 1x2 and 1x4 images works be cause the width and height are both powers of two (e.g. 32 x 64, 32 x 128) But an 1x6 image cannot be loaded because it is impossible to have a number that is a power of two for both the width and height. So in theory an 1x8 image would work in LDD (e.g. 32 x 256) By the way, thank you for making me discover that LDD can load non-square texture.

I've made the PNGs 1024x1024. Otherwise the text was all squished and blurred.

If anyone is interested, I made these two decals some time ago: I sent the files to Stephan,

When I made Brick Studio it didn't really cross my mind that it could be used on a Mac. But now I know that there is also a couple of other people using it on Mac. I remember that at some point I implemented the same camera controls as LDD but I changed it to be more like blender afterward. If I remember correctly, I wanted to make it so that you could choose the camera rotation button (middle or right) so I'm sure the code is still there. When I have some spare time I will try adding back that feature so you can rotate the camera!

Hold the middle mouse button and move the mouse. And you can pan the camera if you hold "shift" while pressing the middle mouse wheel button.

You are correct. I made Brick Studio with OpenGL 3. I didn't know OpenGL 2 was still a thing.

Can you explain what you have found? I haven't had enough time to poke around to understand how it works. When I made the part 47996 (boat mast) flexible, on my first try it was not bending correctly in LDD (wrong direction). To fix the issue I rotated each bone by 90 degree but I was wondering if I could only edit the flexAttributes. Actually, I just re-tested the issue and it is only the Ball connections that needs to be rotated. Brick Studio generates the "flex" connections relatively to the bone orientation so that is why I needed to rotate the bones.

You have found a valid work-around, but I understand that this process is a bit cumbersome. I will definitely add more control over this in the future but it was not in my priorities. But in the next release you will have a more easy solution though. I have revised my "custom" file format for Brick Studio and starting with the next version they will be plain XML (presently they are just a zip file with a custom extension containing an XML file and the meshes files). So after that you "calculate the outlines", you could save your project, open the ".lpp" in notepad, find the element for your model and delete the "<Outlines></Outlines>" tag then reload the project.

No worries I was not sure if you meant to implement a way to make sphere collisions, but the LDD primitive format already supports a sphere collision element. Anyway, I cannot say that Brick Studio is well documented so I cannot blame you for not knowing