Hi,
based on this brick viewer, I have written a converter, that creates LDraw files from LDD mesh files (*.g).
I've solved the problem of the files with the g1, g2, etc. extensions. These are subparts for a model, that are colored differently or textured. My converter can merge these into a single file.
I've attached an example of a part, that was originally split into two.
If there's enogh interest, I'm willing to upload the sources to Github and create a somewhat user friendly version (currently it's a command line tool.)
Thanks to the hard work of very many LDraw parts authors I have here an actual model of a 8564-1 Lehvak. Though, it seems to be missing a little something.
The Krana and the Krana holder pieces are still not modeled, and are the last Bohrok parts that are in such a state. Anyone got thoughts on how are we going to get the models for the Krana? The Bionicle masks in general seem like a nightmare to model. Perhaps that awesome 3D scanner of Philo's could get the mesh? It seems to have the design ID 42042, though note: there's 8 variants though Peeron only pictures 5 of them.
I still think we should congratulate ourselves, we sure have gotten a lot of parts done! I know the rubber band is also missing though that's because I don't know LSynth-fu.
though not yet registered as a part submitter I felt the need to model some parts since my boys are quite addicted to Lego Chima.
In 11767 there is a wheel (11140) made from a metal, apparently tin, but I don't know it for sure.
What would be the appropriate color for this part? Any ideas?
I would like to know if there is a way to change the default 0.3 Bumps on slope parts (used to simulate the slope granularity) to an other value. As for me 1 Bumps would better fit for my renders but it seems that ldview automatically choose a value of 0.3.
Is there anyway to change that instead of manually editing the Pov-ray file ?
As I'm used to model my own LGEO parts for my renders, I frequently add new parts to the lg_elements.lst provided with L3P Add-On.
Then, it will recognize the new part as a LGEO-available one, and will make me a pov file using this LGEO equivalent part.
Problem is that u-parts (u1125 as an example) seems not te be taken into account when inserted in lg_elements.lst.
Does someone has an idea of how can I proceed to make L3P Add-On take those parts into account if inserted in the lg_elements.lst?
I'm not even sure that the problem is the name (beginning by "u") but usually it work like a charm with standard 4 digits part name).
[Edit] I wasn't there was a better forum subsection for DIY rendering, and came across enough projects over there to realize that when I switched over to the show your work arrays, I got my matrices backward for the child transformations.
I've been working on my off again on again graphics engine project and decided to combine my passion for LEGO's as well, but I've hit a stumbling block with loading the .dat files. It seems the once I get a couple levels down everything goes to heck. i've been testing with 4070.dat (1x1 Brick with headlight), and everything seems fine except for the headlight (stud2a.dat) it's squashed on the y axis. Other problems pop up when I try other models. I know it's something in my matrix transformations, and I've tried everything I can think of (went from clean Matrix objects to "show your work" variable arrays, switched from floats to doubles, etc.), and hit a brick wall on searching for examples on the net, so I'm hoping another set of eyes will be what I need. I'm in the testing stage, so the code is kinda ugly, but for the double[12] arrays i'm holding the matrix in, 0->8 is "a" to "i" and 9->11 is "xyz". I'm also attaching a screen shot of 4070.dat with everything but "stud2a" and "stud" removed, so you can see how odd "stud2" looks. Thanks for any help.
I am a pioneer in 3d animation and LEGO is the mother of all 3d. When I found LDRAW a long time ago on the internet I started to do some research with digital LEGO a long time before the LEGO movie. Due to my limited time as a company owner I just made some tests and that's it. Now I am testing with MODO and could unlock a new level of detail and realism which is worth to share. LDD2POVRAY is a nice toy but not really useable for more complex stuff like handling bigger scenes with animation, simulation, effects etc. And it's far too slow. The actual result looks quite promising. I need to find a way to get the LEGO logo on the studs. Unfortunately the replacements for stud.dat and stud2.dat are broken and give not the geometry shown in the pictures: http://www.ldraw.org/cgi-bin/ptdetail.cg...-logo3.dat
The fun part is now that I can import everything coming from LeoCAD or MLCad and setup the materials and shading in 15+ minutes to get this quality. A rendering of this Snowspeeder in HD will take around 4-5 minutes on my 12 core DELL. I wished LEGO would allow an export from LDD. I will update this thread with more results. Have fun.
//
UPDATE +++ Studs with LEGO logo
And here's a result where you see the missing panel in the cockpit now. The panel picture is modeled with MLCad I think and not based on a .dat model. Therefore the python script couldn't convert it. But in MLCad you can export in primitives and then you get the complete model but no separate bricks anymore. And this causes again problems with the rounding shader, low-res studs only as you can see and that's not the model I want to have. So I need to do more investigation and talk to the dev team of that LDR importer to fix this for the future.
4K Rendering with materials from the Peeron Color List. I made intense tests with hi-res studs and bevels I created with Primitiv Generator 2 but the results are the same when I start to adjust the LEGO logo and edges with the rounded edge feature. And the geometry will be much higher. The Peeron RGB colors are looking good. You need to click again on the picture to scale it to full 4K.
And another test with a Technic model. I fixed some missing parts but still some bended hose is missing.
The ultimate renderstresstest with over 5.000 bricks what will take full 32 GB of RAM and patience. Check out the 8K version with impressive details:
Another test with the great 10019 set. I wished it were based on the original LEGO CAD data from Billund incl. labels *:-)