43045 and 43056 are new versions of 98286 and 98285 with 2 holes instead of 3. I would do these myself but I don't have the part so I can't verify how the underside has changed.

Hi all,

thanks to a post on Eurobricks, I remembered I made a script to generate cliff landscape LDraw models a few years back.

It generates models like this one:

(higher resolution)

So I translated the code to Javascript (for portability) and put it there (licenced under GPL 3+).

You can download the project (e.g. as a zip archive), unpack it and open ldraw_cliff.html in a (recent) browser. 

The algorithms are quite simple so it’s really quick.

Note that it might go all wrong on you depending on the parameters (which aren’t really checked).  It will just produce nothing (but messages in the web console if you have one).

Hope you enjoy it.

I have begun work on this model. Should be done in a week or so.

Since I got such quick and helpful advice on my piston rod question, here is my next challenge: universal joints!

Specifically, how do I work out the compound angles of a double u-joint connection? See the image below, where I need to connect axle A to axle B by using the short connecting axle that's floating nearby.
   

Here are some parameters:

• Axle A is oriented parallel the model's Z axis; axle B is oriented at an angle to it. The connector will have to be rotated in both the X and Y directions, but you can't just set one and then the other, because changing either affects both. I'm guessing the 't' word, trigonometry, will come in again here, but because of the compound angle, I'm not sure where to place the triangles.
  
• Axles A and B are rotated 22.5 degrees with respect to their longitudinal axes; my assumption is that the U-joint will transmit the same angle to the connector axle, and that while this rotation needs to be accounted for, it won't change the method needed to determine the connector angle.
  
• I guess I need to determine the rotation of the U-joint hubs at A and B, around both of their local X and Y axes. Again, my assumption is that the hubs themselves, however they may be rotated, will always remain at the same coordinates in absolute space; that is, they always form the point around which the connector axle is angled at each end.
  
• The end of the axle at B may need to be slid downward along its own longitudinal axis in order to correctly intersect the connector axle; this unknown position makes the trigonometry harder to figure out for me.
  

To say the least - I have something left for the era of steam engines.



Especially these time, where the Art Deco has been founded - although my love belongs to the "Art Nouveau",

... also termed in German as "Jugendstil".



Simple marvellous!



So I built this steam locomotive - so as this "Lady" should look like,  trying to reach a maximum from the real original shape....

..as a relict of those nostalgic "Golden Times".



LDraw delivers some benefits, such as "no Dustcatchers" or "room murdering Vitrines", no Limitations of Brick parts amount or unavailable colors.

Also custom parts, patterns or stickers can be designed without any problem.



Always lovely to begin a new project



So, here it is:



Built in th Year of the Lord 1923 and

highlighted with technical performance-enhancing conversions and with representative paint, this machine was first exhibitioned 1925 in Paris, at



"Exposition Internationale des Arts Décoratifs et Industriels Modernes"



Original:

Name: Gt 2×4/4

"5773"

Later Termed  : BR 96

Indicated Power: 1630 PSi



Model:

1 x Buwizz

2 x original medium motors

2 custom Parts: Wind deflector on the cab, drive rod

1 modified part: 3,2 mm pierced 49098.dat (Chimney collar)

a big bunch of patterned parts

BBB Train Wheels

   
   
   
   

Hi Team,

I've created Tail 2340p030 but the surfaces seem to lose their relationships (?) when imported to Blender using the LDR import plugin.

The part was created using LDPE to create left and right templates for use in LDPC, then patterns created. These left and right patterns where then added to the subfile of 2340s01.

         

The created part imports into Stud.io correctly but subsequent export/import into Blender seems to break the part apart.

   

What term/technique have I overlooked or misunderstood?

I've actually created all of the "Canada" series printed bricks and am happy to submit them once this piece is complete.

Thanks in advance.
Adam

Attached Files

  2340pb030.dat (Size: 69.11 KB / Downloads: 3)

Over at the Stud.io forum there was an entry concerning the missing stud-logo on an old part, namely 50949.
I check it and noticed that the primitive is in upper case (STUD.DAT) that leads the renderer to ignore the substitution. Upon changing it to lower case the LEGO-logo was rendered.
   

Do we have an overview how many files still have uppercase prim in them? Shall we recycle them?

Since, although this part appears in only a single set (5571 Giant Truck), that set seems to be a favorite model for many of us, I thought I'd officially request the wheel hub that missing from the library:

https://www.bricklink.com/v2/catalog/cat...4a#T=C&C=9

Happy to work on it myself…but that will be sometime in the future after I get (much) more familiar with parts authoring!

«AWESOME LDraw» is curated list of LDraw resources, such as apps, 3rd-party parts libraries, tutorials, everything related to digital lego modeling.

I created a new LDConfig file using RGB colors from LDD:


  LDConfig.ldr (Size: 32.34 KB / Downloads: 14)

with the following conventions:

* LDraw and BrickLink mostly share naming conventions for their colours.
* Where possible LEGO colour numbers were used.
* The LEGO numbers, names and LDD colours are taken directly from LEGO Digital Designer.
* Colours were compared with Ryan Howerter colour list.
* Rubber colours got their value from the correspondent solid or transparent colour.
* Some transparent colours were altered so that they can be displayed with their LDraw alpha level.
* Edge colours for solid, pearl, metallic colours were calculated the following way:
  If the lightness value L in the HSL colours system was above 20% a Gray with 20% relative
  luminance in the terms of RGB-Gray was used.
  If the lightness value L in the HSL colours system was below 20% a Gray with 50% relative
  luminance in the terms of RGB-Gray was used.
* Edge colours for transparent, chrome, glitter colours were calculated the following way:
  The lightness value L in the HSL colours system was lowered by 20 %. If the lightness value L in
  the HSL colours system was below 20% it was rosen by 20%.

What do you think of it?

Philo kindly compiled a corresponding visual file:



The old version for comparison: