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...
I uploaded the cake costume parts, 35860 and 38560p01, and had them rendered in Stud.io.
What I got was an interesting result. on the LEFT the parts are as I have uploaded them to the PT, resulting in this "cond-line artefact". I remembered that I used a rect2p there with a shear matrix. So I in-lined this and I got the result on the RIGHT picture. Seems that the pre-processing for the renderer is not working correctly.
Has anybody noticed this and (re-)designed a part with this problem in mind?
I cant find an alternate part number for this and cannot see this on the part tracker or any forum posts for the part number or other searches like "technic large motor" or "technic large" yield no results.
