Till now I used the cyls and cyls2 primitives mainly in their available quarter editions, respectively in their 1/8th size

Now I would need a sub-division that does not start at the smallest part (as it is with the 3-16cyls) but one that starts from the tallest one.

- How should those be called? Basically it would be a 1-8cyl...

- And would LDView do Primitive Substitution for those as well?
   

The sticker sheet (6283148) for the Land Rover Defender set 42110 includes 35 numbered stickers. Some are mirror images of each other and in two cases the identical left and right versions have different numbers. To accommodate these in our sticker numbering schema, I am proposing a single character suffix for the unique stickers and a letter-number suffix for the mirror imaged stickers. This allows us to fit within the 26 alpha suffices:

1,3 -> a
2 -> b
3 -> c
4,12 -> d
5 -> e
6 -> f
7 -> g
8 -> h
9 -> i
10 -> j
11 -> k
14, 19 -> l1, l2
15 -> m
16, 18 -> n1, n2
17 -> o
20, 32 -> p1, p2
21, 31 -> q1, q2
22, 30 -> r1, r2
23, 29 -> s1, s2
24, 28 -> t1, t2
25, 26 -> u1, u2
27 -> v
33 -> w
34 -> x
35 -> y

These will take a while to model, but 6283148y.dat has been submitted to the Parts Tracker.

No guesses what this luck chap got for Christmas!

I recently discovered that Studio's Eyesight renderer is a repackaged version of Blender's Cycles renderer. Maybe we could have some enterprising LDrawer write a true converter so that we don't have to deal with Studio's idiosyncrasies? In the interim, there's also Mechabrick's free Blender plugin (that I also recently discovered).

...with building instructions!


Line following rodent


Color sorter

Technic 2004 set

How do I calculate the cumulative sum or total of transformation matrices passed down from parent to child to grandchild, etc.?

The docs say:

Quote:Formally, the transformed point (u', v', w') can be calculated from point (u, v, w) as follows:
u' = a*u + b*v + c*w + x
v' = d*u + e*v + f*w + y
w' = g*u + h*v + i*w + z

Whenever I click on a part in activity list, I get something like "File 'parts/65418.dat' was not found in Unofficial parts library."

I wanted to check with you, who has used LDPE to produce "organic parts" which are only in system given their bounding box.

I selected the Correlian Hound (36032) to try modelling my first part.

So far this is the result I can share no. It went pretty smooth, actually smoother than I thought I have to say. Now the touching up of the tail part and the modeling of the head is pending.

My approach was to take orthogonal pictures and trace the main lines with triangles in LDPC, import those into LDPE and move the vertices around...

Anybody having a different approach?

   

Big shout out to the LDRAW community and Roland Melkert for LDCad! And Rebrickable!
I trained a machine learning algorithm to recognize pictures of bricks, using an animation I made in LDCad. With a parts list from Rebrickable. And parts from LDraw of course. 
My ideal scenario is to grab a handful of bricks, toss them on the table, take a picture, and have the program catalog the pieces.

I put all the how-to details in an article on medium. https://towardsdatascience.com/machine-l...12e0544012
I am working on some other ideas for machine learning brick projects. And it would be cool if people have feedback or wanted to collaborate.

I updated the new LDRAW ALL IN version. There is no problem in the modeling by MLCAD. But when I run the POV file exported from LDRAW, the wrong message is as below.
I checked the before POV file made by old LDRAW ALL IN version, there is no problem. I don't know if there is any option need to setup. Thanks a lot.


Parse Error: No matching } in ‘texture’, undeclared identifier 'lg_gold_chrome' found instead

#ifndef (LDXColor334) // Chrome Gold
#declare LDXColor334 = #if (version >= 3.1) material { #end
texture {
lg_gold_chrome
}
#if (version >= 3.1) } #end
#declare LDXColor334_slope = #if (version >= 3.1) material { #end
texture {
lg_gold_chrome
#if (LDXQual > 1) normal { bumps 0.3 scale 25*0.02 } #end
}
#if (version >= 3.1) } #end
#end