https://forums.ldraw.org/ Sat, 11 Apr 2026 15:15:53 +0000 MyBB https://forums.ldraw.org/thread-29329.html Mon, 19 Jan 2026 22:42:08 +0000 Amiiyah]]> https://forums.ldraw.org/thread-29329.html
After Studio is installed, right click it, and click Configure, then Game options and write this command into the Arguments tab: -dx11 -windowed -ResX=128 -ResY=128.

Studio will run without crashing or freezing.]]>
After Studio is installed, right click it, and click Configure, then Game options and write this command into the Arguments tab: -dx11 -windowed -ResX=128 -ResY=128.

Studio will run without crashing or freezing.]]> https://forums.ldraw.org/thread-28839.html Sun, 25 May 2025 10:05:50 +0000 Jeff Jones]]> https://forums.ldraw.org/thread-28839.html but this isnt omr compliant, anyways this is one of the 2000 sets that is 100% complete kind of a part of my poorly thought out plan*.
she may have parts in the wrong colors, parts clipping in to eachother, missing parts, parts built wrong etc etc
(anyone is free to fix it and upload it to the omr board with proper credit)
*what that poorly thought out plan is, is a complete mystery to everyone except me hehehehehehehe


  povroy.png (Size: 260.57 KB / Downloads: 0)

  7190 millennium falcon.zip (Size: 1.08 MB / Downloads: 4) ]]> but this isnt omr compliant, anyways this is one of the 2000 sets that is 100% complete kind of a part of my poorly thought out plan*.
she may have parts in the wrong colors, parts clipping in to eachother, missing parts, parts built wrong etc etc
(anyone is free to fix it and upload it to the omr board with proper credit)
*what that poorly thought out plan is, is a complete mystery to everyone except me hehehehehehehe


  povroy.png (Size: 260.57 KB / Downloads: 0)

  7190 millennium falcon.zip (Size: 1.08 MB / Downloads: 4) ]]> https://forums.ldraw.org/thread-28788.html Sun, 27 Apr 2025 10:03:43 +0000 Jeff Jones]]> https://forums.ldraw.org/thread-28788.html have i been banned?, parts author taken away from me?]]> have i been banned?, parts author taken away from me?]]> https://forums.ldraw.org/thread-28775.html Mon, 21 Apr 2025 16:09:28 +0000 Angel Amezcua]]> https://forums.ldraw.org/thread-28775.html
I don't know if i have to move some parameters but, i make my manuals in landscape positions, but when i export to PDF appears in portail, i don't why this happen with the new version 2.4.9), this not happen with 2.4.3 Versión. 

Could you help me please if i have to change a parameter or is a bug that has the new versión? thanx.

  File2.png (Size: 139.51 KB / Downloads: 2)

  File10.png (Size: 377.23 KB / Downloads: 5) ]]>
I don't know if i have to move some parameters but, i make my manuals in landscape positions, but when i export to PDF appears in portail, i don't why this happen with the new version 2.4.9), this not happen with 2.4.3 Versión. 

Could you help me please if i have to change a parameter or is a bug that has the new versión? thanx.

  File2.png (Size: 139.51 KB / Downloads: 2)

  File10.png (Size: 377.23 KB / Downloads: 5) ]]> https://forums.ldraw.org/thread-28738.html Fri, 21 Mar 2025 15:34:20 +0000 Brickboy22]]> https://forums.ldraw.org/thread-28738.html . I'm wondering if there is a parts CDN to be used with the ThreeJS LdrawLoader, (or if I can host one). I know there is some on GitHub, however most of them have not been updated in years, and I can't find an updated one. (gkjohnson/ldraw-parts-library on GitHub is what I found, but as a stated before, has not been updated in 2 years)

Also sorry for posting in off topic, I don't know what category this belongs in other than parts and I'm pretty sure that's for requesting new parts/issues with part models.]]> . I'm wondering if there is a parts CDN to be used with the ThreeJS LdrawLoader, (or if I can host one). I know there is some on GitHub, however most of them have not been updated in years, and I can't find an updated one. (gkjohnson/ldraw-parts-library on GitHub is what I found, but as a stated before, has not been updated in 2 years)

Also sorry for posting in off topic, I don't know what category this belongs in other than parts and I'm pretty sure that's for requesting new parts/issues with part models.]]> https://forums.ldraw.org/thread-28663.html Fri, 07 Feb 2025 13:08:55 +0000 Jaco van der Molen]]> https://forums.ldraw.org/thread-28663.html
I realize this might be considered heresy among true LEGO purists, but has anyone experimented with 3D printing LEGO elements, using an LDraw part file
(Or Stud.io part file for that matter)

For a very special project for a friend, I want to make a Technic, Axle and Pin Connector Angled #7 - 168.75 degrees in green.

So far, this part only comes in Reddish Orange from 5 sets.

Could someone provide me with a file format for a 3D printer?

Help or tips are much appreciated.

Jaco

P.S. Hoping some future botanical sets might ever use this part in green for plant stems... ;-)]]>
I realize this might be considered heresy among true LEGO purists, but has anyone experimented with 3D printing LEGO elements, using an LDraw part file
(Or Stud.io part file for that matter)

For a very special project for a friend, I want to make a Technic, Axle and Pin Connector Angled #7 - 168.75 degrees in green.

So far, this part only comes in Reddish Orange from 5 sets.

Could someone provide me with a file format for a 3D printer?

Help or tips are much appreciated.

Jaco

P.S. Hoping some future botanical sets might ever use this part in green for plant stems... ;-)]]> https://forums.ldraw.org/thread-28622.html Mon, 20 Jan 2025 12:52:35 +0000 Jeff Jones]]> https://forums.ldraw.org/thread-28622.html everytime i open it on emulators it say uhhh go to google play to update i go to google play its not there because incompablity]]> everytime i open it on emulators it say uhhh go to google play to update i go to google play its not there because incompablity]]> https://forums.ldraw.org/thread-28521.html Sat, 30 Nov 2024 14:01:26 +0000 Gabriel Läufer]]> https://forums.ldraw.org/thread-28521.html
maybe the *.conn file format is already known but in case its not you can find the description below.  I’m also referring partly to the thread “Studio Connectivity Data“ where the question was asked how the *.conn file format is defined.

Connectivity files, e.g., the file definition is actually not too complicated to understand. However, it is more complicated as the collision files just because there are more of them and they are encrypted.

It is true that Part Designer converts the *.conn files -contrary to the *.col files- to a binary format (due to whatever reason). But this does not mean that you cannot access the information, you just have to use a trick. If you generate a part file in Part Designer and store it as *.part it contains all information about the brick. The geometry, the connectivity info and -hidden in the part geometry- the collision data. To see the connectivity info in human-readable format only thing you have to do: Start with a new part but only add connectivity elements (no geometry). In the part editor you will see an empty workspace but in the connectivity editor you can see the connectivity element. If you store this part now as *.part you can open and read it in a text editor (the conversion to binary takes places during export; not internally). From here it is rather a matter of changing the individual values/variables  in *.part file and check what are the consequences. Below an image from the STUD connectivity element e.g. the file format:


  Con1.png (Size: 11.06 KB / Downloads: 31)
Figure 1.1: Connectivity file format for the STUD connectivity element (associated *.part file)

I’ve been playing around with these values and compared it with the other connectivity elements. What I’ve found out so far:

First block:              0 (always the same)
Second block:          PE_CONN (always the same, mostly likely a meta command; Part Editor Connectivity maybe)
Third block:             ID1 (group ID see figure 1.2 below)
Fourth block:           ID2 (element ID see figure 1.2 below)
Fifth block:              1 0 0 0 1 0 0 0 1 (always the same, Transformation matrix)*
Sixth block:              XYZ (Position of the element)
Seventh block:         2 2 (always the same; geometry data aka visual representation of the element)**
Eight block:             3:1,0:4,3:1,0:4,10:4,0:4,3:1,0:4,3:1 (always the same; geometry data aka visual representation of the element)***

* For other elements not always the identity matrix; see figure 1.2
** Lateral size. If you change it from 2 2 to 1 1 it has half the size. But any other value does not work
*** Most complicated one. I guess it describes or are related the geometry of the connectivity element itself (squares in the corner, disc in the center and the connection lines). If you change 10:4 to 20:4 for example the disc changes its form from a disc to a ring. Some of the numbers fit roughly to the size of the connectivity element.

One can argue that during the export Part Editor adds additional data but I’ve also checked this. I’ve generated a *.part file with connectivity elements and exported it to Studio. The associated connectivity file (*.conn) I’ve opened in Part Editor and saved it as *.part again. If the exporter from PE adds additional data to the *.conn file these files should be different but there are the same (I’m assuming PE does not remove data during import).   

In figure 1.2 you can see the *.part file with all connectivity elements you can choose from the menu. There are 43 of them. Sorted by ID1. You can see the similarity between these elements. Only the seventh and eights block is different. I guess the above file format also applies to these files (more or less).


  Con2.png (Size: 87.17 KB / Downloads: 56)
Figure 1.2: Connectivity file format for all connectivity elements you can pick from task bar 

In figure 1.3 you can see all connectivity elements in the connectivity editor (sorted by group).


  Con3.png (Size: 199.18 KB / Downloads: 38)
Figure 1.3: Connectivity elements in Part Designer 

Hope the helps.

Best,
Gabe]]>
maybe the *.conn file format is already known but in case its not you can find the description below.  I’m also referring partly to the thread “Studio Connectivity Data“ where the question was asked how the *.conn file format is defined.

Connectivity files, e.g., the file definition is actually not too complicated to understand. However, it is more complicated as the collision files just because there are more of them and they are encrypted.

It is true that Part Designer converts the *.conn files -contrary to the *.col files- to a binary format (due to whatever reason). But this does not mean that you cannot access the information, you just have to use a trick. If you generate a part file in Part Designer and store it as *.part it contains all information about the brick. The geometry, the connectivity info and -hidden in the part geometry- the collision data. To see the connectivity info in human-readable format only thing you have to do: Start with a new part but only add connectivity elements (no geometry). In the part editor you will see an empty workspace but in the connectivity editor you can see the connectivity element. If you store this part now as *.part you can open and read it in a text editor (the conversion to binary takes places during export; not internally). From here it is rather a matter of changing the individual values/variables  in *.part file and check what are the consequences. Below an image from the STUD connectivity element e.g. the file format:


  Con1.png (Size: 11.06 KB / Downloads: 31)
Figure 1.1: Connectivity file format for the STUD connectivity element (associated *.part file)

I’ve been playing around with these values and compared it with the other connectivity elements. What I’ve found out so far:

First block:              0 (always the same)
Second block:          PE_CONN (always the same, mostly likely a meta command; Part Editor Connectivity maybe)
Third block:             ID1 (group ID see figure 1.2 below)
Fourth block:           ID2 (element ID see figure 1.2 below)
Fifth block:              1 0 0 0 1 0 0 0 1 (always the same, Transformation matrix)*
Sixth block:              XYZ (Position of the element)
Seventh block:         2 2 (always the same; geometry data aka visual representation of the element)**
Eight block:             3:1,0:4,3:1,0:4,10:4,0:4,3:1,0:4,3:1 (always the same; geometry data aka visual representation of the element)***

* For other elements not always the identity matrix; see figure 1.2
** Lateral size. If you change it from 2 2 to 1 1 it has half the size. But any other value does not work
*** Most complicated one. I guess it describes or are related the geometry of the connectivity element itself (squares in the corner, disc in the center and the connection lines). If you change 10:4 to 20:4 for example the disc changes its form from a disc to a ring. Some of the numbers fit roughly to the size of the connectivity element.

One can argue that during the export Part Editor adds additional data but I’ve also checked this. I’ve generated a *.part file with connectivity elements and exported it to Studio. The associated connectivity file (*.conn) I’ve opened in Part Editor and saved it as *.part again. If the exporter from PE adds additional data to the *.conn file these files should be different but there are the same (I’m assuming PE does not remove data during import).   

In figure 1.2 you can see the *.part file with all connectivity elements you can choose from the menu. There are 43 of them. Sorted by ID1. You can see the similarity between these elements. Only the seventh and eights block is different. I guess the above file format also applies to these files (more or less).


  Con2.png (Size: 87.17 KB / Downloads: 56)
Figure 1.2: Connectivity file format for all connectivity elements you can pick from task bar 

In figure 1.3 you can see all connectivity elements in the connectivity editor (sorted by group).


  Con3.png (Size: 199.18 KB / Downloads: 38)
Figure 1.3: Connectivity elements in Part Designer 

Hope the helps.

Best,
Gabe]]> https://forums.ldraw.org/thread-28518.html Wed, 27 Nov 2024 21:55:43 +0000 Gabriel Läufer]]> https://forums.ldraw.org/thread-28518.html
maybe the *.col file format is already known but in case its not you can find the description below.  I’m also referring partly to the thread “Studio Connectivity Data“ where the question was asked how the *.col file format is defined.

Collider files e. g. the file definition is actually not too complicated to understand. I’ve not checked all *.col files in the Studio LDraw folder but some of them. Hence, I cannot tell you if the file format applies to all files, but it applies to the ones I’ve checked. Below a snapshot from the collider file for brick 3005.dat (named 3005.col).


  Col01.png (Size: 99.46 KB / Downloads: 10)
Figure 1.1: Collider file for brick 3005.dat (1x1 Brick)

Each line in the *.col files describes one collision box. All lines (boxes) together form kind of collider brick. Whenever two of these collider bricks are touching each other, the associated brick went transparent in Studio which indicates a collision (if the function is activated in Studio).

The file format from one collision box is as follows:

First block:                9 (always the same)
Second block:            0 (always the same)
Third block:               1 0 0 0 1 0 0 0 1 (1st part of a transformation matrix; always the same)*
Fourth block:             X Y Z (2nd part of the transformation matrix; position of the collision box)
Fifth block:                W H L (size of the collision box) 
Sixth block:               null (always the same)**

* Some of the *.col files store this block as 1 instead of 1.000
** This block only exists in the earlier *.col files (at the same time Studio beta was launched; maybe a coincidence). 

I’ve written a very simple and basic program that converts a *.col file into a *.ldr file using the box.dat primitive (one primitive for each collision box). The above file is then called 3005COL.ldr. In figure 1.2 below you can see the collider brick in red. In figure 1.3 I’ve superimposed the collider brick and the real brick itself (brick 3005 is drawn transparent for clarification).


  Col02.png (Size: 188 KB / Downloads: 3)
Figure 1.2: Collider brick for brick 3005


  Col03.png (Size: 154.65 KB / Downloads: 3)
Figure 1.3: Collider brick and brick 3005 superimposed

One can see that the collider brick is a little bit smaller as the brick itself. This can be verified with Studio also. The collision warning does not occur directly after the bricks have contact but a little later. See figure series below. 


  Col04.png (Size: 195.36 KB / Downloads: 0)
Figure 1.4: Two 1x1 bricks separated. Collision warning in Studio activated. No collision detected.


  Col05.png (Size: 201.15 KB / Downloads: 0)
Figure 1.5: Two 1x1 bricks just touching each other. Collision warning in Studio activated. No collision detected.


  Col06.png (Size: 157.74 KB / Downloads: 0)
Figure 1.6: Two 1x1 bricks collided (they intersect a little bit). Collision warning in Studio activated. But no collision detected.


  Col07.png (Size: 212.56 KB / Downloads: 0)
Figure 1.7: Two 1x1 bricks collided (they intersect a bit more). Collision warning in Studio activated. Now the bricks turn transparent to indicate a collision.

To show the geometry of more complex collider bricks, I’ve also converted the *.col files for part 10a (Baseplate 24 x 32), 64713 (Cone Spiral Jagged - Step Drill) and 59278 (Boat hull, Hull Unitary 74 x 18 x 7 with Light Bluish Gray Top). The first one is a part with multitude of studs, the second one a complex shaped part and the latter one of the largest file in the *.col folder. See images below.


  Col08.png (Size: 241.63 KB / Downloads: 2)
Figure 1.8: Collider brick for part 10a.dat (Baseplate 24 x 32)


  Col09.png (Size: 211.59 KB / Downloads: 3)
Figure 1.9: Collider brick for part 64713.dat (Cone Spiral Jagged - Step Drill)


  Col10.png (Size: 268.67 KB / Downloads: 2)
Figure 1.10: Collider brick for part 59278.dat (Boat hull, Hull Unitary 74 x 18 x 7 with Light Bluish Gray Top)

And some close ups from 10a.dat and 59278.dat.


  Col11.png (Size: 145.34 KB / Downloads: 1)
Figure 1.11: Close-up from the collider brick for part 10a.dat


  Col12.png (Size: 489.73 KB / Downloads: 3)
Figure 1.12: Close-up from the collider brick for part 59278.dat

Hope the above explanation helps to get an impression how studio calculates collisions.

Best,
Gabe]]>
maybe the *.col file format is already known but in case its not you can find the description below.  I’m also referring partly to the thread “Studio Connectivity Data“ where the question was asked how the *.col file format is defined.

Collider files e. g. the file definition is actually not too complicated to understand. I’ve not checked all *.col files in the Studio LDraw folder but some of them. Hence, I cannot tell you if the file format applies to all files, but it applies to the ones I’ve checked. Below a snapshot from the collider file for brick 3005.dat (named 3005.col).


  Col01.png (Size: 99.46 KB / Downloads: 10)
Figure 1.1: Collider file for brick 3005.dat (1x1 Brick)

Each line in the *.col files describes one collision box. All lines (boxes) together form kind of collider brick. Whenever two of these collider bricks are touching each other, the associated brick went transparent in Studio which indicates a collision (if the function is activated in Studio).

The file format from one collision box is as follows:

First block:                9 (always the same)
Second block:            0 (always the same)
Third block:               1 0 0 0 1 0 0 0 1 (1st part of a transformation matrix; always the same)*
Fourth block:             X Y Z (2nd part of the transformation matrix; position of the collision box)
Fifth block:                W H L (size of the collision box) 
Sixth block:               null (always the same)**

* Some of the *.col files store this block as 1 instead of 1.000
** This block only exists in the earlier *.col files (at the same time Studio beta was launched; maybe a coincidence). 

I’ve written a very simple and basic program that converts a *.col file into a *.ldr file using the box.dat primitive (one primitive for each collision box). The above file is then called 3005COL.ldr. In figure 1.2 below you can see the collider brick in red. In figure 1.3 I’ve superimposed the collider brick and the real brick itself (brick 3005 is drawn transparent for clarification).


  Col02.png (Size: 188 KB / Downloads: 3)
Figure 1.2: Collider brick for brick 3005


  Col03.png (Size: 154.65 KB / Downloads: 3)
Figure 1.3: Collider brick and brick 3005 superimposed

One can see that the collider brick is a little bit smaller as the brick itself. This can be verified with Studio also. The collision warning does not occur directly after the bricks have contact but a little later. See figure series below. 


  Col04.png (Size: 195.36 KB / Downloads: 0)
Figure 1.4: Two 1x1 bricks separated. Collision warning in Studio activated. No collision detected.


  Col05.png (Size: 201.15 KB / Downloads: 0)
Figure 1.5: Two 1x1 bricks just touching each other. Collision warning in Studio activated. No collision detected.


  Col06.png (Size: 157.74 KB / Downloads: 0)
Figure 1.6: Two 1x1 bricks collided (they intersect a little bit). Collision warning in Studio activated. But no collision detected.


  Col07.png (Size: 212.56 KB / Downloads: 0)
Figure 1.7: Two 1x1 bricks collided (they intersect a bit more). Collision warning in Studio activated. Now the bricks turn transparent to indicate a collision.

To show the geometry of more complex collider bricks, I’ve also converted the *.col files for part 10a (Baseplate 24 x 32), 64713 (Cone Spiral Jagged - Step Drill) and 59278 (Boat hull, Hull Unitary 74 x 18 x 7 with Light Bluish Gray Top). The first one is a part with multitude of studs, the second one a complex shaped part and the latter one of the largest file in the *.col folder. See images below.


  Col08.png (Size: 241.63 KB / Downloads: 2)
Figure 1.8: Collider brick for part 10a.dat (Baseplate 24 x 32)


  Col09.png (Size: 211.59 KB / Downloads: 3)
Figure 1.9: Collider brick for part 64713.dat (Cone Spiral Jagged - Step Drill)


  Col10.png (Size: 268.67 KB / Downloads: 2)
Figure 1.10: Collider brick for part 59278.dat (Boat hull, Hull Unitary 74 x 18 x 7 with Light Bluish Gray Top)

And some close ups from 10a.dat and 59278.dat.


  Col11.png (Size: 145.34 KB / Downloads: 1)
Figure 1.11: Close-up from the collider brick for part 10a.dat


  Col12.png (Size: 489.73 KB / Downloads: 3)
Figure 1.12: Close-up from the collider brick for part 59278.dat

Hope the above explanation helps to get an impression how studio calculates collisions.

Best,
Gabe]]> https://forums.ldraw.org/thread-28446.html Wed, 09 Oct 2024 21:52:21 +0000 Eugen]]> https://forums.ldraw.org/thread-28446.html

• https://blog.prusa3d.com/wp-content/uplo...2/lego.jpg
  
• https://twitter.com/josephprusa/status/1...8273700865
  

There was few similar MOCs on Lego.Ideas and Rebrickable:

• https://ideas.lego.com/projects/4e60af90...9e24b5ae07
  
• https://rebrickable.com/mocs/MOC-38505/A...ickscount/
  

]]>

• https://blog.prusa3d.com/wp-content/uplo...2/lego.jpg
  
• https://twitter.com/josephprusa/status/1...8273700865
  

There was few similar MOCs on Lego.Ideas and Rebrickable:

• https://ideas.lego.com/projects/4e60af90...9e24b5ae07
  
• https://rebrickable.com/mocs/MOC-38505/A...ickscount/
  

]]> https://forums.ldraw.org/thread-28204.html Mon, 08 Apr 2024 20:18:42 +0000 Manfred Schaefer]]> https://forums.ldraw.org/thread-28204.html
I am trying to calculate the individual rotations (Euler angles) around the three axes from the rotation matrix.

I have also tried it with quaternions, but somehow it doesn't work.  

Has anyone tried something like this before and can give me a solution or tips?
Thank you.

Manfred]]>
I am trying to calculate the individual rotations (Euler angles) around the three axes from the rotation matrix.

I have also tried it with quaternions, but somehow it doesn't work.  

Has anyone tried something like this before and can give me a solution or tips?
Thank you.

Manfred]]> https://forums.ldraw.org/thread-28078.html Mon, 19 Feb 2024 01:57:07 +0000 Steffen]]> https://forums.ldraw.org/thread-28078.html
They introduced nice playability features:
- modular space modules that interconnect
- crystal harvesting that is used to create energy cells used for power through all the sets consistently
- compatibility in design and functionality between FRIENDS and CITY sets
- reusing the CLASSIC SPACE logo in a new signature color BRIGHT BRIGHT ORANGE
- awesome spacey design
- special computer/monitor flatscreen elements

https://www.youtube.com/watch?v=UXXhwucHcQI


  LEGO Space 2024.png (Size: 480.81 KB / Downloads: 3) ]]>
They introduced nice playability features:
- modular space modules that interconnect
- crystal harvesting that is used to create energy cells used for power through all the sets consistently
- compatibility in design and functionality between FRIENDS and CITY sets
- reusing the CLASSIC SPACE logo in a new signature color BRIGHT BRIGHT ORANGE
- awesome spacey design
- special computer/monitor flatscreen elements

https://www.youtube.com/watch?v=UXXhwucHcQI


  LEGO Space 2024.png (Size: 480.81 KB / Downloads: 3) ]]> https://forums.ldraw.org/thread-27694.html Fri, 01 Sep 2023 22:13:54 +0000 Roland Melkert]]> https://forums.ldraw.org/thread-27694.html
I need to 'draw' some simple 3D shapes for a new LDraw program I'm working on.

In the past I generated those in code (e.g. LDCad's color wheel disk etc), but this limits things a lot, so this time I'm thinking about importing .obj files or const data structures instead.

Blender and so on are a bit overkill for this as I only need very simple things (e.g. a ruby/marvel like one)

Anyone has tips on software to use for creating such simple triangle meshes?

Maybe even LDPE?]]>
I need to 'draw' some simple 3D shapes for a new LDraw program I'm working on.

In the past I generated those in code (e.g. LDCad's color wheel disk etc), but this limits things a lot, so this time I'm thinking about importing .obj files or const data structures instead.

Blender and so on are a bit overkill for this as I only need very simple things (e.g. a ruby/marvel like one)

Anyone has tips on software to use for creating such simple triangle meshes?

Maybe even LDPE?]]> https://forums.ldraw.org/thread-26720.html Tue, 04 Oct 2022 05:40:22 +0000 Lenny]]> https://forums.ldraw.org/thread-26720.html
I wrote veeery simple app to browse Rebrickable database (only minifigs) and create your local collection in browser. 

If someone open this app on mobile please tell me if you were not able to open cards: display/themes/collection. 

If you found another bugs - feedback aprreciated

Known bugs: if you want to remove minifig from display card the gold background of component is still visible.

https://rad-marigold-1c55dd.netlify.app/]]>
I wrote veeery simple app to browse Rebrickable database (only minifigs) and create your local collection in browser. 

If someone open this app on mobile please tell me if you were not able to open cards: display/themes/collection. 

If you found another bugs - feedback aprreciated

Known bugs: if you want to remove minifig from display card the gold background of component is still visible.

https://rad-marigold-1c55dd.netlify.app/]]> https://forums.ldraw.org/thread-26224.html Fri, 08 Apr 2022 08:07:27 +0000 Jaco van der Molen]]> https://forums.ldraw.org/thread-26224.html
As you might know (or not) but I was a contestant for LEGOMASTERS Netherlands/Belgium 2020

A cameraman from LEGOMASTERS Netherlands/Belgium asked our group if we could build a classic camera rig / boom.
This one:
https://www.flickr.com/photos/brian_will...237539889/

I understand most of the model and with a few tweaks here and there made a digital version and instructions for him.
For what I can tell some parts are not LEGO or custom or cut.

The one thing I do not get is how the camera rolls are build and attached to the camera. Anyone any thoughts?
I asked the author but no response so far.

Also, the clips that hold the rail are not LEGO too, are they? If so, what part is that clip?

Thanks!]]>
As you might know (or not) but I was a contestant for LEGOMASTERS Netherlands/Belgium 2020

A cameraman from LEGOMASTERS Netherlands/Belgium asked our group if we could build a classic camera rig / boom.
This one:
https://www.flickr.com/photos/brian_will...237539889/

I understand most of the model and with a few tweaks here and there made a digital version and instructions for him.
For what I can tell some parts are not LEGO or custom or cut.

The one thing I do not get is how the camera rolls are build and attached to the camera. Anyone any thoughts?
I asked the author but no response so far.

Also, the clips that hold the rail are not LEGO too, are they? If so, what part is that clip?

Thanks!]]>