Hello everyone,

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).

   
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).

   
Figure 1.2: Collider brick for brick 3005

   
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. 

   
Figure 1.4: Two 1x1 bricks separated. Collision warning in Studio activated. No collision detected.

   
Figure 1.5: Two 1x1 bricks just touching each other. Collision warning in Studio activated. No collision detected.

   
Figure 1.6: Two 1x1 bricks collided (they intersect a little bit). Collision warning in Studio activated. But no collision detected.

   
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.

   
Figure 1.8: Collider brick for part 10a.dat (Baseplate 24 x 32)

   
Figure 1.9: Collider brick for part 64713.dat (Cone Spiral Jagged - Step Drill)

   
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.

   
Figure 1.11: Close-up from the collider brick for part 10a.dat

   
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

i need front side maybe back top and bottom pics of sandy head id 61285
maybe fish head id 61286

Thread for Wednesday license sets

LDCAD already has the ctrl+right-click function for multiple selections. Is it possible to add a selection function similar to Blender?For example selection Circle and selection Lasso?I think this will be more convenient to operate

Hello everyone,

I had an idea and was wondering if this might be something worth looking into.
There was an older post regarding the issue, but it seems this was without solution:
https://forums.ldraw.org/thread-27623.html

Is it allowed to use a mixture of "normal" patterns and Texmaps to simulate the effect of certain holofoil stickers (like in 6991 or 6949)? Seems a bit unusual to me, but in theory it works.

Here is a quick test shot I made:
   

Probably need to get a better image of the foil and get the scaling more accurate to the real stickers. Perhaps this single image can even be used on all those "dotted" stickers.

However, there seem to be issues when exporting to other formats or Stud.io

Hello, I need help numbering (and composing) a part...
I dont have the physical part but got good pics from Ddriver, so the part itself is nearly done.
   
Part(s) in question: x871a/b
http://www.peeron.com/inv/parts/x871a
http://www.peeron.com/inv/parts/x871b
https://www.bricklink.com/v2/catalog/cat...a#T=C&C=12
https://www.bricklink.com/v2/catalog/cat...b#T=C&C=12
https://rebrickable.com/parts/upn0313a/c...functions/
https://rebrickable.com/parts/upn0313b/c...functions/
from the outside, its the same brick, but the B version has some electronics inside to reverse it.

Now the big question: how should that get split (and numbered)?

Its consists of base (black) electronics (dark tan) and cover (clear)
BL and Peeron have the main (paintable) color clear and the base is hardcoded black.
I would use u9618-20, each in a and b like the microphones u9616.
a is the older Forward/Stop and b the newer Forward/Stop/Backwards
Should i use u9617 for a split microphone bottom?

René

Hello community

Could you tell me if there is any way to improve the quality of the exported files as .stl (increase the amount of polygon)?

thanks

I've added a new tab to the user dashboard for uXXXX numbers. You can:
- See the uXXXX numbers assigned to you
- See if those numbers are in use or not
- Make notes on the numbers you are assigned
- Request more numbers
- Give back numbers that you don't intend to use

Hello there everyone. I'm once again requesting a rather important part to use on some IG posts. Could someone please add this wavy hair to the parts list?

Bricklink Code: 73272

Seems strange because the part is in LDraw since 1998 but it seems 2566 is wrong: the body is too long (24 LDU instead of 20 LDU) and the bottom bar too short (16 LDU instead of 24 LDU).

There’s no alternate ID so it shouldn’t be a variation.  Am I missing something?

Source and pic.