Can I use one part for a model that I will sell if I give credit to this site and author? I am 3d modeling a project from scratch and there is one part that is taking forever to make. I saw this in legal and need confirmation that I can use one part if I give credit.
You are free:
to copy - distribute, display, and use the CA approved LDraw Parts Library
to make derivative works
to make commercial use of the CA approved LDraw Parts Library
Attribution - You must give the original author credit. The LDraw Steering Committee (SteerCo) also holds an attribution to 'The LDraw Parts Library' in such Derivative Works to be sufficient in lieu of a full list of authors.
I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2020-02. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.
I created a revision of part 59233, left the current official part, right my new part:
Before I finish this part, what about the roundings? I used sharp angles because I thought it looked better and was easier to model.
I want to round the ends a bit, but what about the other angles, should they all be rounded?
Hi all, my name's Pat. I've just replaced my 13+ year old home computer with a new one and I'm just installing ldraw again. Question I have relates to the parts tree hierarchy in mlcad. When I installed this all those years ago, there was a some kind of parts tree tweak available that I had installed that separated out, for example, all of the different brick types (decorated, modified, etc.) such that when clicking on the basic brick category, exactly and only that would appear in the parts preview pane, basic bricks only. Would dearly love to be able to set this up this way again.
I have no recollection on how I managed to implement this reorganization back then. Any direction on how to do so again would be appreciated.
I had this topic in mind, when I stumbled on this very old thread. With the vastly increased use of photo-realistic rendering since then, I'm wondering if the subject has been given any more thought?
In particular, I've found that there's a fair number of parts that are made of a softer plastic than the typical ABS brick, and/or have a rougher, matte finish (like the slope texture that kicked off that thread). While there are already color categories for rubber, various metals, etc., there seems to be a lack of options for describing different solid plastic properties within LDraw.
As a more general note, this seems like another in a family of physical part characteristics that I could envision being described by a series of metadata extensions, possibly as part of a hypothetical LDraw 2.0. Others in the family could include snapping/connectivity info, physical part dimensions (for accurately rendering seams, or calculating part collisions), and kinematic info (for describing technical functions like gear meshes).
This is my first post here, so hopefully announcements of this sort are ok.
I'm a web developer who works on libraries related to web components, a way for developers to create their own HTML tags. As part of a demo/codelab a coworker and I created a MPD viewer web component using three.js called <brick-viewer>.
<brick-viewer> wraps up three.js and it's LDraw loader example so that it's super easy to use. All you have to do is import the element definition, then use the tag:
PHP Code:
<?php <!-- import the custom element definition -->
<script type="module" src="https://unpkg.com/brick-viewer?module"></script>
<!-- use the tag anywhere in HTML -->
<brick-viewer src="./radar_truck.mpd"></brick-viewer>
<brick-viewer> was made as a demo, but it's pretty usable. It displays build steps with a slider and that's controllable with an HTML attribute. The code itself is pretty straightforward, so it could be extended with new features. You can see the code and file bug reports and feature requests here: https://github.com/polymerlabs/brick-viewer/
I hope it enables sites like this to easily embed 3D models without any programming. It'd be nice to unleash the potential of WebGL + Lego on the web
I'd love feedback if you try it out! We're new to the file formats and use cases, so if there's something we could do better, let us know.
One thing I'd love to know about is if there are any efforts to make .ldr files be able to link to each other, or newer formats that would allow that. It seems like having to make MPD files slows down the workflow, and makes it a bit harder to make a viewer app that could just render LDR files hosted on the web.
Creating plain base part is sufficient, as I'll try to have training for curved surface patterns, as well as 93088.
Looking into Philo's 93088, I can see what we need for cleaning up LDD exported data:
- Adding conditional lines
- Using primitives especially for connections with other parts (studs, accessory holes, handles for minifigs etc.)
I'll start making my first 3-D part from easier one soon (such as 94717), but animals are a little above me now.
Could someone verify that lightsaber hilt length is different? If length is different (as they are modeled), I'm a bit surprised that they are mixed together on Bricklink...
![[Image: 59233.PNG]](https://bricksafe.com/files/ejboer/59233.PNG)
