In order to align all ring primitives to the"ring" vice "rin" or "ri" naming and prevent 100s of parts having to pass through the PT, I intend to do the following:
- Create new "ring" primitives and submit them to the PT (these will be fastracked if already CC BY 4)
- Obsolete the old "rin" and "ri" primitives and submit those to the PT (these will also be fastracked if already CC BY 4)
- Certify those 2 groups of primitives via the normal process
- Once certified, update all the affected parts to the non-obsolete primitive via manual database action. The official parts will be flagged as receiving a minor edit and will automatically be included in the next part update.
Since this circumvents the normal PT process for some parts, I'd like to ensure there are no major objections to this plan.
I am starting the thread based on the discussion that evolved here on the PT concerning part 72008, which has no through holes, but an axle stopper at the centre.
There are some other parts that have a stopper, but no matter how small it is, this is currently incompüatible with our axel lengths, which are multiples of 20 LDUs.
Here is Magnus' statment: Magnus Forsberg [MagFors] made the following comment. 2024-01-10 16:53:49 This is perhaps a good opportunity to discuss the error in all similar parts. The hole needs to be exactly 20 ldu deep, but in most cases it has been modeled with a divider at 19.5, 1 ldu thick. That's not correct.
All Technic Axle are made using the axle.dat primitive. Or something more suitable, when needed. That primitive is not correct. A real axle has a slightly bevelled, convex end. Making it possible to have the 2 axles pushed all the way into the stopper ring, wich has a coresponding concave bevelled design
The axlehole primitives in this part need to be 20 ldu deep, to allow a correct position of a mounted axle. But we need to also have a stopper, 1 ldu thick. It doesn't add up.
When I reworked the axlehole primitive I found that many parts use a primitive that is only 19.5 ldu. This will be a problem in connection seeking SW, that will not allow a correct position of the axle. The hole isn't deep enough.
And Max' measurement of the Axles in real life: Max Martin Richter [MMR1988] made the following comment. 2024-01-10 18:24:00 All axles I measure are shorter than our models. 2L = 15.7 mm 3L = 23.4 mm 4L = 31.7 mm 5L = 39.4 mm 6L = 47.7 mm 7L = 55.5 mm 8L = 63.5 mm 10L = 79.4 mm 12L = 95.2 mm
I'm trying to locate files and models for various G1 and G2 Bionicle parts, with a particular focus of masks.
While I've encountered a few comprehensive parts catalogs, there's a conspicuous gap in the archival of masks from G2, and even from G1's Voya-nui, Mahri-nui, and Karda-nui sets.
I'm not picky with the results here; any sources/files are greatly appreciated.
The official specification for texture mapping says:
Quote:Filenames that themselves contain double quotes must use \ as an escape character immediately prior to the double quote. The \ character itself must be doubled up (\\) in order to be used to specify a sub-directory, but it is recommended that / be used instead in this case. (In LDraw files, \ and / are interchangeable as path separators.)
I have several questions...
Are these sentences referring to quoted filenames specifically, or all filenames? It's not very clear from the context of the document. The paragraph starts (before the bit I've quoted) by talking about quoted filepaths specifically but then changes tack to talk about appending "textures/" which is surely not specific to a quoted filepath.
It would seem to make sense that a regular non-quoted path to a texture ought to be able to use a single backslash as a separator since it seems to be common practice when referencing parts etc, and the quote that separators are "interchangeable".
Should the backslash "escape character" work with characters other than " and a second backslash or just those two?
The main spec page is even fuzzier about filenames - no mention of spaces or quoting. Is it allowed, disallowed, discouraged? All we seem to get is just:
Quote:"Special characters, such as &, #, |, and ?, should be avoided as they may also cause cross-platform issues and create problems when used in URLs."
The use of the phrase 'such as' lacks clarity: which characters should be discouraged and which are fine? It would surely help people to know. Are any characters disallowed? e.g. are quotes and spaces allowed?
this is should be easy... are in the Sets: Castle: Kingdoms: 7189-1
Goat with Black Eyes, Dark Tan Horns and Medium Nougat Spots Pattern
Item No: 95341pb01
and
Deer with Dark Brown Antlers 51493c01pb01
in the Sets Holiday & Event: Christmas: 40499-1 and Winter Village Collection: Holiday & Event: Christmas: 10275-1
During the recent holidays I started building Void Crew LEGO models just for entertainment purposes, but I quickly ran out of bricks the right color and size so I took the project online where I found LeoCAD!
The project became way more ambitious when I suddenly had access to unlimited legacy bricks, so I decided to build a version of the Metem Destroyer in Void Crew!
Scale wise it’s not really big enough for minifigures, but it was an interesting challenge to interpolate the design 😄 and there’s some silly choices in there, especially the airlock, which is a screen door brick I think 😄
Anyway, I just wanted to share the result here if anyone else is both a Void Crew and LEGO fan and want to keep building on the model I made. You should be able to use the .ldr I attached to the post, it is my first LeoCAD model though, so it's pretty messy ( 20 20 hindsight right ) - I'll do better next time!
Next phase: Figure out how LeoCAD records each step of the way, perhaps order the actual bricks and build it RL OR go big and create a version with interior that fits minifigures
![[Image: 65461pb06.png]](https://img.bricklink.com/ItemImage/PN/47/65461pb06.png)
![[Image: metemdestroyerdoneshot01.png?w=1088]](https://witusdotdk.files.wordpress.com/2024/01/metemdestroyerdoneshot01.png?w=1088)
![[Image: ingamedestroyer01.png.png?w=1024]](https://witusdotdk.files.wordpress.com/2024/01/ingamedestroyer01.png.png?w=1024)
![[Image: metemdestroyerdoneshot02.png?w=1024]](https://witusdotdk.files.wordpress.com/2024/01/metemdestroyerdoneshot02.png?w=1024)
