This is a valid connection, used in official BI

1 0 0 -8 0 1 0 0 0 1 0 0 0 1 20482.dat
1 72 0 -18 0 1 0 0 0 1 0 0 0 1 2723.dat

How many of the axle hole primitives are allowed to attach on a Bar sized cylinder?
Digging in my parts I found only a few, mainly older parts that didn't fit on a Bar. Is the design of the axlehol primitive correct?

I was asked to maybe change the design on the new wheelholder brick, 65634 , but I can't find a better suited axle primitive.
The best suited primitive is maybe axl3hol6, but it doesn't look right.

Are we missing an axle primitive?

Hi guys
Is there a possibility to insert a LPub meta command directly into the source Window of LDCad?
Or must I go over the (Windows)Editor?

Thanks and regards
Johann

With the official launch of Spike Prime set, I was asked how to create cables in models... so I made this short video:
https://www.youtube.com/watch?v=vDnkkPsyCT4

A quick reference to the candidates for the 2020/2021 LDraw.org Steering Committee (SteerCo) election. The information is drawn from the nomination process and corrections are welcome, please email the webmasters.

Candidates are listed by nomination status in alphabetical order by last name and no ranking or endorsement should be inferred from their position on the list. The following table summarizes the status of each candidate in the format:

Nominee name: Nomination Status (Nominator, Second)

Johann Eisner: Accepted (Max Martin Richter, Willy Tschager)
Philippe Hurbain: Accepted (Johann Eisner, Orion Pobursky)
Gerald Lasser: Accepted (Johann Eisner, Orion Pobursky)
Orion Pobursky: Accepted (Johann Eisner, Travis Cobbs)
Max Martin Richter: Accepted (Orion Pobursky, Johann Eisner)
Willy Tschager: Accepted (Orion Pobursky, Johann Eisner)

Chris Dee: Not Yet Accepted (Orion Pobursky, Johann Eisner)
Magnus Forsberg: Not Yet Accepted (Philippe Hurbain, Orion Pobursky)
Roland Melkert: Not Yet Accepted (Philippe Hurbain, Orion Pobursky)

Travis Cobbs: Declined (Philippe Hurbain, Orion Pobursky)
Steffen: Declined (Orion Pobursky, Johann Eisner)


Replies to this have been disabled. The nominations thread is where they belong.

Knights Kingdom

Per the LDraw.org Bylaws at [color=black]http://www.ldraw.org/article/268.html[/color], Subsection
6.03(a), the 2019/2020 Steering Committee hereby calls for the community to
nominate individuals as candidates for the 2020/2021 Steering Committee[1].

Please post nominations in response to this message. Nominations will only be
recognized if they are in response to this message.

Per ss.6.03(a), you must specify the name of the person you are nominating,
along with your name. Another member of the community must second the nomination
in a reply, and the nominee must publicly accept the nomination in the same
channel (direct reply to the nomination or second) in order to be valid. If the
nominee does not accept, it will be assumed that he or she has declined, and
they will not be placed on the ballot.

Nominations will close at 11:59 PM GMT on 29 February 2020. This means that to
be listed on the ballot, a candidate must have been nominated, seconded and must
have formally stated acceptance by that time.

The Steering Committee will give sufficient notice of the election and election
procedures per ss.6.03(b).

NOTE: subsection 6.03(b) states that elections should take place before March 1.
We interpret this to mean that we will commence the election on March 1, but
since it is electronic, it will run for 2 weeks, just as last time. The exact
time and date of start and end will be announced sometime very close to (but
after) 0000 GMT March 1.

Again, thanks to all of you for your commitment to the goals of the
organization, and in working with us this year. Please, stay involved with
LDraw.org and keep it moving forward!

Willy Tschager
On behalf of the LDraw.org Steering Committee

--
[1] Try not to confuse the LDraw.org Steering Committee (SteerCo) with the LDraw
Standards Board (LSB). The Steering Committee sets the course for the LDraw
Organization while the Standards Board deals with the LDraw File Format.

There is some consistency problem on PT concerning the link texts and what they point to:
- in detail page/required/related subfiles, title text points to detail page while part_number.dat allows to download file. Perfect imho.
- in activity page, there is only a link on part_number.dat, but it points to detail page. I'd like it to download file, and get a link on title pointing to detail page
- Similar problem in parts list, i'd like part_number.dat to directly download file (and, for sake of consistency, show the .dat extension)
- I guess that file scan could/should be homogeneized too, with link to download on part_number.dat, link to detail page on part title, and link column with only the events link.

Even more nitpicking, use bold face for title in activity/list/scan pages like it is used in detail page.

Say, what's the deal with the !THEME meta? It's an optional meta for the OMR spec, but it doesn't appear in the list of official metas, nor the list of known unofficial ones. LDCad doesn't know it, are there other programs that do? Is it helpful to include when submitting to the OMR, or is it just as easy to include the theme as a keyword?

Since we use a hybrid threaded model, I’m toying with turning off automatic quoting. This mean that the post you are replying to won’t be quoted unless you explicitly check the quote box next to the post.

Thoughts?

I am working on the Belville Door, 33216, which has a rounded narrow side which goes along another curve. So naturally it should be a torus.

Now comes the problem: The major radius is 69.5 LDU, the minor radius is 2.5 LDU. The size of the major radius calls for a 48 segment division, but for the other dimension 48 segments are way too much.

So I think a set of primitives would make sense, that have a 48 segment division for the major radius, but a standard 16 segment division for the minor one. This could apply if the major radius is more than 10 times the minor one.

Also, if those primitives, made by the primgen2, have 'only' 4 decimals, the scaling to a radius of 70 leads to gaps, extending this to 5 decimals is a benefit for those applications.

Currently I made a subfile for this special torus-"primitive"

What's your opinion?