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:

I tried to load a model and found that a number of Bionicle and Factory parts where not available for LDraw.
If someone could make these, I would really appreciate that.

LDD number    Bricklink number    Bricklink description
41890    41890    Arm Mechanical, Super Battle Droid
98570    98570pb01    Hero Factory Chest Badge with 'H' on Light Bluish Gray Background Pattern
98562    98562    Hero Factory Weapon - Handcuff
47299    47299    Bionicle Toa Metru Knee Cover
19179    19179    Minifigure, Weapon Blade with Bar and 3 Spikes
92222    92222    Hero Factory Shield with Handle for Clip
15407    15407    Minifigure, Hand Armor
47298    47298    Bionicle Toa Metru Foot
98564    98564    Hero Factory Zamor Sphere Launcher - Bottom Half with Axle Hole
98593    98593    Hero Factory Shoulder Armor, Sonic Speaker
98341    98341    Ring 4 x 4 with 2 x 2 Hole and 4 Arrow Ends (Ninjago Spinner Crown)

Thanks in advance,

René

https://youtu.be/4cvr20Q39gw

New parts @ 4:13

I can't quite figure out how to calculate the angle and vertical distance of a piston rod on a rotated crankshaft, specifically using LDCad's Selection Info tool. Here's a diagram:
   

So the crankshaft has been rotated -49.5 degrees. The piston rod (A-B) will move up the Y-axis, but I don't know that distance (it's slightly less than the current Y distance between A and C). Also, point B will remain at its current X position but point A will rotate around point B to connect with the axle at point C. The angle of that rotation is the second thing I don't know.

No doubt this has been tackled many times before, but I'd like to know the precise way to figure it out (rather than downloading an already finished model). It's either slightly more difficult, or vastly simpler than I realize.   (And I do know about the piston placement script in LDCad, but AFAIK it doesn't recognize these old-style piston parts or brick-built cylinders.)

Again, the two values I need to find are:

• The distance to move the piston rod along the Y-axis, and
  
• The angle to rotate point A around point B so that it connects with axle C
  

There's a bit of a debate about U-Joint shortcuts going on on the PT.

Here's my take:

There are 2 ends and a center for each U-joint.  

The ends are 3712 - https://www.ldraw.org/parts/official-par...artid=3712 
These parts have only ever come in color 7 or 71

The center has 2 types:
3326a - https://www.ldraw.org/parts/official-par...rtid=3326a 
This came in color 7, 71, and 79
3326b - https://www.ldraw.org/parts/official-par...rtid=3326b 
This came in color 7, 71

The current shortcut, 3712c01.dat, uses 3326a and is color 16 for all 3 parts

There are updated shortcuts on the PT that hard code the center color. There is some debate about these here:
https://www.ldraw.org/cgi-bin/ptdetail.c...712c03.dat

This thread is intended to continue that discussion.

Note: this is in response to this thread.

This is a proposal to add a new !DATA meta-command that can be used to embed texture data into model files (for use with unofficial parts in an OMR model). The proposed specification for the new meta-statement follows. Please discuss.

Purpose

This document describes the !DATA meta-statement, which contains a set of commands for embedding binary data into LDraw files.

New meta-statement token

!DATA

This is the main data-embedding meta-command.

Reuse of existing meta-statement token

!:

This will be used to specify a BASE-64 encoded data stream. This token was introduced with the !TEXMAP meta-statement, and will be reused here for three reasons: its reuse will not interfere with its use in !TEXMAP; it is useful for the same reasons that it was useful in !TEXMAP; and !DATA is only useful right now for embedding texture data for use with !TEXMAP, so the two meta-statements are related to each other.

Syntax

0 !DATA START
0 !: <data1>
0 !: <data2>
...
0 !: <datan>
0 !DATA END

Description

This meta-statement allows for BASE-64 encoded data to be used inside a multi-part-dat (MPD) file. The decoded binary data replaces of the embedded MPD sub-file.

1. This meta-statement must come after the 0 FILE meta-statement signifying a sub-file in a multi-part-dat (MPD) file.
   
2. The FILE that the DATA belongs to must not contain any geometry.
   
3. The FILE must contain one and only one DATA section.
   
4. The FILE may contain header information.
   
5. All characters after 0 !: that are not valid BASE-64 characters must be ignored. (This is intended to allow white-space characters to be placed in the line, but still applies to all other characters that are not valid BASE-64 characters.)
   
6. Each 0 !: line except for the last must contain exactly 76 encoded characters.
   
7. The last 0 !: line must contain no more than 76 encoded characters.