LDCad Part Snapping missing/errors


Part Snapping missing/errors
#1
This is intended to be a catchall thread to let Roland know about missing/problematic part snapping info.

Note: make sure that the part you are reporting is official
Reply
RE: [LDCad] Part Snapping missing/errors
#2
75181 (Turntable Flat Base 4x4) is missing snap info
Reply
RE: [LDCad] Part Snapping missing/errors
#3
55817, Wheel 21x56 with 8 Spokes Armoured. No snap info for pinhole and the 8 holes on the sides.
Reply
RE: [LDCad] Part Snapping missing/errors
#4
All the flex-system hoses have no snap info.
Reply
RE: [LDCad] Part Snapping missing/errors
#5
The various components of the old 6x16 train assembly are missing snap info. I've added my own, as follows:

In the 6x16 base plate itself (736.dat), I added female snap cylinders for the two magnet holders, and for the two axles:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 12] [pos=0 39 -140]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 12] [pos=0 39 140]
0 !LDCAD SNAP_CYL [group=axleR4] [gender=F] [caps=none] [secs=R 4 80] [pos=-40 42 -100] [ori=0 -1 0 1 0 0 0 0 1]
0 !LDCAD SNAP_CYL [group=axleR4] [gender=F] [caps=none] [secs=R 4 80] [pos=-40 42 100] [ori=0 -1 0 1 0 0 0 0 1]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=-50 8 -150] [grid=2 16 100 20]

In the magnet holder (735.dat), I added a male cylinder for mating to the base, along with a pair of point snaps on the magnet itself (for coupling two magnets together):

Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=one] [secs=R 6 12]
0 !LDCAD SNAP_GEN [group=mag] [gender=M] [bounding=pnt] [match=group] [pos=56 -5 0]
0 !LDCAD SNAP_GEN [group=mag] [gender=F] [bounding=pnt] [match=group] [pos=56 -5 0] [ori=-1 0 0 0 1 0 0 0 -1]

And in the wheel/axle shortcut (243c02.dat) I added the male cylinder snap for mating to the base:

Code:
0 !LDCAD SNAP_CYL [group=axleR4] [gender=M] [caps=none] [secs=R 4 80] [pos=-40 0 0] [ori=0 -1 0 1 0 0 0 0 1]

Feedback/suggestions welcome!
Reply
RE: [LDCad] Part Snapping missing/errors
#6
60478.dat, Plate 1x2 with Handle on End. Mirror doesn't work correctly. Probably missing info
Reply
RE: [LDCad] Part Snapping missing/errors
#8
(2020-01-02, 2:06)Orion Pobursky Wrote: 60478.dat, Plate 1x2 with Handle on End. Mirror doesn't work correctly. Probably missing info
That one isn't symmetrical in the X direction. Mirroring only works without shadow info for parts that are x symmetric.

If you don't want to wait on the update it's easily fixed by adding a mirror meta to the part (shadow) using a 'base flip' of whatever axis is symmetrical (Z in this case).
Reply
RE: [LDCad] Part Snapping missing/errors
#7
(2019-12-31, 2:30)Orion Pobursky Wrote: This is intended to be a catchall thread to let Roland know about missing/problematic part snapping info.
Good idea.

I'll try to include things posted here in the next release, but keep in mind I'm already working on the 1903 parts.
Reply
RE: Part Snapping missing/errors
#9
15207 has no bottom snap info
Reply
RE: Part Snapping missing/errors - 99012
#10
99012 (Technic Rotor 1 Blade 8L with Peghole and Axlehole) is missing mirroring info (and inherited connectivity can be refined).
Code:
0 !LDCAD MIRROR_INFO [baseFlip=Z]
0 !LDCAD SNAP_CLEAR [ID=axleHole]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=A 6 20] [pos=0 30 0] [ori=-1 0 0 0 1 0 0 0 -1]
Reply
RE: Part Snapping missing/errors
#11
I have problems with part-snapping of roller coaster tracks on top of other parts, i.e. 25061 (90 degree), 26561 (ramp), 34738 (S-shape), 26599 (S-shape lower)... They snap perfectly "under" another part, but not on top of it - so I let them snap below and move 2 plates (16 LDU) upwards. I don't know if this is my fault or if the parts are missing snapping info.
Reply
RE: Part Snapping missing/errors
#12
(2020-03-10, 20:09)Stefan Frenz Wrote: I have problems with part-snapping of roller coaster tracks on top of other parts, i.e. 25061 (90 degree), 26561 (ramp), 34738 (S-shape), 26599 (S-shape lower)... They snap perfectly "under" another part, but not on top of it - so I let them snap below and move 2 plates (16 LDU) upwards. I don't know if this is my fault or if the parts are missing snapping info.
This is the symptom of no snapping at all. It works from top because the part inherits connectivity of studs, but there is no common structure on plate bottom to allow subparting and inheritance.
Reply
RE: Part Snapping missing/errors
#13
Part 6628 is missing bar connectivity inside pin section:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 4 18] [pos=20 0 0] [ori=0 1 0 1 0 0 0 0 -1]
See set 42106 for usage example.
Reply
RE: Part Snapping missing/errors
#14
I've finished the snapping info for the 1903 library.

I also processed all thing people mailed me about and things mentioned above up to message #13.

Thanks for all whom contributed.

You can (always) download the latest seed file at:
http://www.melkert.net/action/download/shadow.sf

Just replace the old one in LDCad's seeds location  (subfolder of the exe file).

Some notes

@Orion
I can't find 75181, did you mean 61485 ? although that one has snapping info.

"All the flex-system hoses have no snap info."
They do have info, but only for the end caps, or did you mean the bended parts. LDCad doesn't support that at the moment, maybe in 1.7

@N.W.Perry
I applied your #5 definitions with some minor changes which should make it somewhat easier to use. Feel free to review.
Reply
RE: Part Snapping missing/errors
#15
(2020-03-14, 2:50)Roland Melkert Wrote: @Orion
I can't find 75181, did you mean 61485 ? although that one has snapping info.

Yes. (75181 is the set I was working on). Unless the info is in this update, then my current shadow library does not have it

(2020-03-14, 2:50)Roland Melkert Wrote: "All the flex-system hoses have no snap info."
They do have info, but only for the end caps, or did you mean the bended parts. LDCad doesn't support that at the moment, maybe in 1.7

Not the bent ones, the straight ones. And it would be helpful to have this info for the middle section.
Reply
RE: Part Snapping missing/errors
#17
(2020-03-14, 2:50)Roland Melkert Wrote: @N.W.Perry
I applied your #5 definitions with some minor changes which should make it somewhat easier to use. Feel free to review.

Everything looks good to me!
Reply
RE: Part Snapping missing/errors
#16
The door element 60616a does not snap into 60596 (but for example 60623 does) and the window element 57895 does not snap into 57894.
Reply
RE: Part Snapping missing/errors
#18
(2020-03-15, 10:51)Stefan Frenz Wrote: The door element 60616a does not snap into 60596 (but for example 60623 does) and the window element 57895 does not snap into 57894.
Did you update to the above shadow?

Because only 57894 doesn't have snap information in that version.

I'll add 57894 to the next update.
Reply
RE: Part Snapping missing/errors
#19
(2020-03-16, 19:19)Roland Melkert Wrote: Did you update to the above shadow?
On the tested installation: not yet, sorry. Sad
Reply
RE: Part Snapping missing/errors
#20
The hose reel 2585 does not snap into the hose reel holder 2584 (with shadow.sf). Not a problem, but maybe nice to have. Smile
Reply
RE: Part Snapping missing/errors
#21
There’s no snap info for the center pin in the 2x2 Turntable (3680 and 3679)
Reply
RE: Part Snapping missing/errors
#22
15207.dat is missing bottom stud connectivity. I copied from 30413.
Reply
RE: Part Snapping missing/errors
#23
I am not sure, if this is so wanted.
The middle hole of the Servomotor (99498) have no info.


Attached Files Thumbnail(s)
   
If nothing goes right, go left.
Reply
RE: Part Snapping missing/errors
#24
15301 shooter bottom is missing connectivity.
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [center=true] [pos=0 -2 -30] [grid=1 4 0 20]

Snapping for arrow is kind of missing in 15400 shooter assembly. I propose
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 5.5 9   R 4 35.9   R 4 45.1] [slide=true] [pos=0 8.446736 -48] [ori=-1 0 0 0 -0.017452 -0.999848 0 -0.999848 0.017452]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 5.5 9   R 4 35.9   R 4 45.1] [slide=true] [pos=0 8.446736 48] [ori=1 0 0 0 -0.017452 -0.999848 0 0.999848 -0.017452]
...questionnable, but works well!
Reply
RE: Part Snapping missing/errors
#25
Pneumatic valve with axle hole 19474

No information on the hose connections
If nothing goes right, go left.
Reply
RE: Part Snapping missing/errors
#26
(2019-12-31, 2:30)Orion Pobursky Wrote: This is intended to be a catchall thread to let Roland know about missing/problematic part snapping info.

Not sure if this would need a new thread, but I'm introducing a new (shadow) meta in 1.6d

!LDCAD HINTS

It can (also) be used to override the rest rotation of parts in the part bin.

I used it to rotate panels so their pattern is faced forwards.

If anyone thinks other parts need rotating let me know.
Reply
RE: Part Snapping missing/errors
#27
Microfig 85863.dat (or rather its sub-part -s01) is missing bottom snap info.
Reply
RE: Part Snapping missing/errors
#28
28326 (Car Mudguard 4x3x1) has no bottom snap info
Reply
RE: Part Snapping missing/errors
#29
30301 has wrong bottom info
Reply
RE: Part Snapping missing/errors
#30
(2020-04-02, 9:55)Gerald Lasser Wrote: 30301 has wrong bottom info

??
Can't find that number.
Reply
RE: Part Snapping missing/errors
#31
(2020-04-02, 10:59)Magnus Forsberg Wrote: ??
Can't find that number.

Typo: 30201
Reply
RE: Part Snapping missing/errors
#32
(2020-04-02, 15:04)Gerald Lasser Wrote: Typo: 30201

These kinds of mistakes happen when I go trough too many parts in one go Smile
Reply
RE: Part Snapping missing/errors
#33
Round tile 2x2 (14769.dat) is missing the connection on the center underside stud.

For that matter, I've noticed that snapping info is not generally included for any of the in-between underside studs/tubes on 2x or larger parts (not to mention the space between studs on the top surface). I'm sure this is intentional and I can fully understand the reason.

But I think it's worth including for the 2x2 round tile, since having that connection is fundamental to the (re-)design of the part.
Reply
RE: Part Snapping missing/errors
#34
(2020-04-04, 17:42)N. W. Perry Wrote: Round tile 2x2 (14769.dat) is missing the connection on the center underside stud.

For that matter, I've noticed that snapping info is not generally included for any of the in-between underside studs/tubes on 2x or larger parts (not to mention the space between studs on the top surface). I'm sure this is intentional and I can fully understand the reason.

But I think it's worth including for the 2x2 round tile, since having that connection is fundamental to the (re-)design of the part.

Yes those are missing on purpose.

The main reason being the LDCad snapping engine only searches for a single connection pair when dragging stuff around. So the middle 6ldu hole would make it snap 'wrong' 95% of the time.

That said, you might be right about this part being used more often in that way.

This is the exact reason I'm considering adding a 'priority' property to the snapping metas in 1.7, which should reduce the false matches considerably.
Reply
RE: Part Snapping missing/errors
#35
I've processed all up to post #34

It will be in the def shadow of 1.6d
Reply
RE: Part Snapping missing/errors
#36
4x4 Dome (86500.dat) has no info. I put anti-studs at all four corners (under the notches), but I'm not sure that's the right approach. You may need more studs inside the rim, or maybe the whole thing has to act as one giant cylinder snap?
Reply
RE: Part Snapping missing/errors
#37
(2020-04-13, 6:32)N. W. Perry Wrote: 4x4 Dome (86500.dat) has no info. I put anti-studs at all four corners (under the notches), but I'm not sure that's the right approach. You may need more studs inside the rim, or maybe the whole thing has to act as one giant cylinder snap?

The corners is probably good enough.

I've also added the ring, so if something happens to use the same radius it will snap to that too.

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [grid=C 2 C 2 60 60]
0 !LDCAD SNAP_CYL [gender=F] [caps=A] [secs=R 38 4] [pos=0 -4 0] [ori=1 0 0 0 -1 0 0 0 -1]
0 !LDCAD SNAP_CYL [gender=M] [caps=one] [secs=R 39.5 4] [pos=0 -4 0] [ori=1 0 0 0 -1 0 0 0 -1]
Reply
RE: Part Snapping missing/errors
#38
Part 30046 (window lattice) snap just needs to be nudged -1 on Y. (The matching window frame 30044 is correct.)
Reply
RE: Part Snapping missing/errors
#39
Part 4740 has overlapping cylinder snaps, one in the part and one in the sub-part. (Neither is quite correct for this part's weird dimensions; the cylinder sections should be [ R 6 5.3  R 4 6.7 ].)
Reply
RE: Part Snapping missing/errors
#40
So I've got a few more in here:

  • Wheel rim 11208 has no snap info.
  • Inverted dome 15395 has no snap info.
  • 95109 could use a cylinder snap on the non-pointy section. However, that may be getting renumbered as a subpart.
  • EDIT: The various 90462 (Egyptian headdress) parts don't have bottom snap info (I guess because it's a tube prim)
Reply
RE: Part Snapping missing/errors
#41
I've processed up to #40

Latest shadow is at:
http://www.melkert.net/action/download/shadow.sf

It also includes a whole lot of shadow files donated by Alex Taylor, some of which are for unofficial files.

I haven't had the time to review them all but this is a work in progress version of the shadow anyway Smile

I will not include the unofficial ones in LDCad releases so some snapping functionally might 'disappear' when you upgrade to an official version.


(2020-05-02, 4:24)N. W. Perry Wrote: Wheel rim 11208 has no snap info.
What kind of pin is supposed to snap to that?
Reply
RE: Part Snapping missing/errors
#42
(2020-06-09, 23:16)Roland Melkert Wrote: What kind of pin is supposed to snap to that?

Good question, actually—the only set I've used it in uses a 3.18 bar. But it seems to pair with the city/town scale wheel pins, such as 4488.dat.
Reply
RE: Part Snapping missing/errors
#44
(2020-06-09, 23:16)Roland Melkert Wrote: What kind of pin is supposed to snap to that?

So yeah, it's meant to just go onto wpin.dat. The wheel pin clicks into the empty space in the middle, so it only extends halfway through the wheel.

Here's what I ended up going with:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 4 11   R 5 3   R 4 11] [center=true] [slide=true] [ori=1 0 0 0 0 1 0 -1 0]
Reply
RE: Part Snapping missing/errors
#45
(2020-07-09, 2:50)N. W. Perry Wrote: So yeah, it's meant to just go onto wpin.dat. The wheel pin clicks into the empty space in the middle, so it only extends halfway through the wheel.

Here's what I ended up going with:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 4 11   R 5 3   R 4 11] [center=true] [slide=true] [ori=1 0 0 0 0 1 0 -1 0]

Yes, but on both sides.

This rim should have used 2 wpinhol2
1 16 0 0 -3.25 -0.707107 0 -0.707107 -0.707107 0 0.707107 0 9.25 0 wpinhol2.dat
1 16 0 0 3.25 -0.707107 0 -0.707107 -0.707107 0 0.707107 0 -9.25 0 wpinhol2.dat
Reply
RE: Part Snapping missing/errors
#46
(2020-07-09, 5:20)Magnus Forsberg Wrote: Yes, but on both sides.

Well, the single cyl snap extends all the way through. A wheel pin will snap on either side, but a 318 bar will still slide all the way through. But perhaps this is not the preferred method?

Quote:This rim should have used 2 wpinhol2
1 16 0 0 -3.25 -0.707107 0 -0.707107 -0.707107 0 0.707107 0 9.25 0 wpinhol2.dat
1 16 0 0 3.25 -0.707107 0 -0.707107 -0.707107 0 0.707107 0 -9.25 0 wpinhol2.dat

The geometry of the rim is funky overall, and doesn't match the wpin's dimensions well. Maybe the snap info should match the rim's geometry rather than the pin's, allowing some realistic "play", but in my models I find that more a hindrance than a help. I like things like wheels to just snap to one place, and one place only.
Reply
RE: Part Snapping missing/errors
#49
I think there is something wrong in the shadow file s\31111s01.dat


.png   31111.png (Size: 21.98 KB / Downloads: 318)

My log-file say this:
Circular reference detected to "s\31111s01.dat" from "31111.dat", reference will be cleared and rendered as "missing".


Attached Files
.zip   logFile-2020-07-17-15-49-25.zip (Size: 30.47 KB / Downloads: 0)
Reply
RE: Part Snapping missing/errors
#50
(2020-07-17, 13:56)Magnus Forsberg Wrote: I think there is something wrong in the shadow file s\31111s01.dat

My log-file say this:
Circular reference detected to "s\31111s01.dat" from "31111.dat", reference will be cleared and rendered as "missing".

Indeed,

"s\31111s01.dat" references to 31111 for its snap data, while 31111 references "s\31111s01.dat" mesh wise.

Solution is to move the snap data from "31111.dat" to "s\31111s01.dat", and delete the shadow for "31111.dat" entirely.

Is "31111.dat" using a subpart a recent change?
Reply
RE: Part Snapping missing/errors
#51
Relatively recent yes, when I created the animal "segment" patterns (such as https://www.ldraw.org/parts/official-par...d=31111p02). There was already a patterned version, but it was not subparted (https://www.ldraw.org/parts/official-par...d=31111p01)
Reply
RE: Part Snapping missing/errors
#43
Two updates to official parts:

24866.dat
Needs the following additional cyl snap (to connect with various stem parts):
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 2 2] [pos=0 2 0]

63965a.dat
Has no snap info; should be:
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=R 4 16   R 6 8   R 4 96] [slide=true] [pos=0 16 0]
Reply
RE: Part Snapping missing/errors
#47
I have no idea if this is my fault or maybe I missed something, but perhaps it has to do with part snapping: using 35563 (Cone 4x2x4 Half with Roof Tiles, I think it was in the last LDraw part update) as upper part and trying to snap this with the bottom to the upper side of a below 48310 (Cone 8x4x6 Half), the part is 1/2 stud (10 LDU) beside the "real" studs..
Reply
RE: Part Snapping missing/errors
#48
(2020-07-09, 18:23)Stefan Frenz Wrote: I have no idea if this is my fault or maybe I missed something, but perhaps it has to do with part snapping: using 35563 (Cone 4x2x4 Half with Roof Tiles, I think it was in the last LDraw part update) as upper part and trying to snap this with the bottom to the upper side of a below 48310 (Cone 8x4x6 Half), the part is 1/2 stud (10 LDU) beside the "real" studs..

Yes, that's because the upper part has no snap info of its own, but it is inheriting the snap for the bottom stud tube. So it's connecting that to the hollow studs of the lower cone.

Adding the following pair of lines to 35563 should work:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [pos=0 96 -30] [grid=C 4 1 20 0]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [pos=0 96 -10] [grid=C 2 1 60 0]
Reply
RE: Part Snapping missing/errors
#52
I've processed up to message #48

And I also added a new bunch of files by Alex Taylor (incl some unofficial ones)

As always the latest (test) shadow is at:
http://www.melkert.net/action/download/shadow.sf
Reply
RE: Part Snapping missing/errors
#54
(2020-08-04, 20:42)Roland Melkert Wrote: I've processed up to message #48

And I also added a new bunch of files by Alex Taylor (incl some unofficial ones)

As always the latest (test) shadow is at:
http://www.melkert.net/action/download/shadow.sf

I'm a little unclear how the shadow.sf file in the seeds directory relates to the shadow libraries in Application Data. How do the newly added parts get into the official library, and what if I'm using a custom library, containing all the official content but also whatever new files I've added?

Just want to be sure I'm not updating the hard way. :-)
Reply
RE: Part Snapping missing/errors
#55
(2020-08-05, 23:06)N. W. Perry Wrote: I'm a little unclear how the shadow.sf file in the seeds directory relates to the shadow libraries in Application Data. How do the newly added parts get into the official library, and what if I'm using a custom library, containing all the official content but also whatever new files I've added?

The contents of .sf (plain zip) files are synchronized with the per user location at program start.

This way each user can setup their own bins and options etc, while still having defaults out of the box.

It will only update existing files and remove obsolete ones, if you got additional custom content that will not change.

If you are using an unpacked shadow it shouldn't affect you at all, unless you unpack the updated shadow (.csl) in the user location again.
Reply
RE: Part Snapping missing/errors
#56
(2020-08-06, 20:20)Roland Melkert Wrote: The contents of .sf (plain zip) files are synchronized with the per user location at program start.

This way each user can setup their own bins and options etc, while still having defaults out of the box.

It will only update existing files and remove obsolete ones, if you got additional custom content that will not change.

If you are using an unpacked shadow it shouldn't affect you at all, unless you unpack the updated shadow (.csl) in the user location again.

What I've been doing is copy the offLib.csl to my own custLib.csl, then I unpack that and use it as my shadow library so I can save corrections and new shadow files.


So if I understand correctly, my process should be:

  • -Before installing the new .sf, I should re-pack my custom library to custLib.csl
  • -Set custLib.csl as my library so that it will synchronize
  • -Install the new .sf and re-launch LDCad
  • -Re-unpack custLib and switch to that directory when I want to make more changes
I should now have all updated files, plus whatever new ones I'd made (unless they were corrections to existing files, which are now replaced with your updates). Right?
Reply
RE: Part Snapping missing/errors
#57
(2020-08-07, 0:30)N. W. Perry Wrote: What I've been doing is copy the offLib.csl to my own custLib.csl, then I unpack that and use it as my shadow library so I can save corrections and new shadow files.


So if I understand correctly, my process should be:

  • -Before installing the new .sf, I should re-pack my custom library to custLib.csl
  • -Set custLib.csl as my library so that it will synchronize
  • -Install the new .sf and re-launch LDCad
  • -Re-unpack custLib and switch to that directory when I want to make more changes
I should now have all updated files, plus whatever new ones I'd made (unless they were corrections to existing files, which are now replaced with your updates). Right?

No. You'll destroy your customizations if you do that. You have have more that one shadow library. Better to have a separate shadow library that only contains your altered/added files much like is done with unofficlal parts. Then your custom lib will override the "official" Roland supplied one.
Reply
RE: Part Snapping missing/errors
#58
(2020-08-07, 0:55)Orion Pobursky Wrote: No. You'll destroy your customizations if you do that. You have have more that one shadow library. Better to have a separate shadow library that only contains your altered/added files much like is done with unofficlal parts. Then your custom lib will override the "official" Roland supplied one.

But I actually want the Roland-file to override mine, that's OK. I only want to keep any of my additional files that haven't made it into the "official" package yet. It sounded like those wouldn't get overwritten.

For unofficial parts it's no problem; the shadow info can even be baked into the main file. For official parts, you can only choose one shadow library per search path, but I suppose I can duplicate the official search path (same main folder, but different shadow libs). Keep the offLib as a zipped library, and use an unpacked one for saving my own additions/corrections. Would that work?
Reply
RE: Part Snapping missing/errors
#59
(2020-08-07, 2:52)N. W. Perry Wrote: But I actually want the Roland-file to override mine, that's OK. I only want to keep any of my additional files that haven't made it into the "official" package yet. It sounded like those wouldn't get overwritten.

For unofficial parts it's no problem; the shadow info can even be baked into the main file. For official parts, you can only choose one shadow library per search path, but I suppose I can duplicate the official search path (same main folder, but different shadow libs). Keep the offLib as a zipped library, and use an unpacked one for saving my own additions/corrections. Would that work?

The .sf will sync offLibShadow.csl as a whole.

So you'll need to unpack it (again) yourself. I sugest first renaming the original unpacked folder so you can visualize changes with e.g. winmerge.

Each search location has only one shadow as the content will be appended to the pure part files before parsing start.
Reply
RE: Part Snapping missing/errors
#60
(2020-08-07, 17:19)Roland Melkert Wrote: The .sf will sync offLibShadow.csl as a whole.

So you'll need to unpack it (again) yourself. I sugest first renaming the original unpacked folder so you can visualize changes with e.g. winmerge.

Each search location has only one shadow as the content will be appended to the pure part files before parsing start.

Got it. So I'm already doing it correctly (re-naming and re-unpacking the synced official library). The difficulty is just that MacOS doesn't have a convenient way to merge folders if they contain sub-folders, so I have to do that part manually.
Reply
RE: Part Snapping missing/errors
#53
The venerable Fabuland shovel (4330) need snaps on its handle and shaft. (And is the actual part really that long??!)
Reply
RE: Part Snapping missing/errors
#61
Part 39794 Technic Beam 11x7 with Open Center 9x5 is missing snap info for the pinholes on the sides.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#62
(2020-08-28, 8:33)Jaco van der Molen Wrote: Part 39794 Technic Beam 11x7 with Open Center 9x5 is missing snap info for the pinholes on the sides.

The same info is missing on the bigger frame 13 x 9, 39790
Reply
RE: Part Snapping missing/errors
#63
Gate 42448 needs cyl snaps on at least the shortest of the verticals, where you'd normally clip it.
Reply
RE: Part Snapping missing/errors
#64
The big plastic wheels need cylinder snaps:

6118.dat
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 16   R 8 42] [pos=0 0 8] [ori=1 0 0 0 0 -1 0 1 0]

2593.dat
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 16   R 8 4] [pos=0 0 -2] [ori=1 0 0 0 0 -1 0 1 0]

2515a.dat and 2515b.dat
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 16   R 8 6] [pos=0 0 -2] [ori=1 0 0 0 0 -1 0 1 0]
Reply
RE: Part Snapping missing/errors
#65
Plate  1 x  1 Round with  3 Leaves 32607 needs snapping info at the bottom stud.
It only snaps at the top stud now.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#66
Door 1x5x8.5 (87601) does not snap into Brick 1x1x3 with Two Clips (60583b)
Reply
RE: Part Snapping missing/errors
#67
Staircase Spiral Axle (40244) does not snap into Tile 2x2 with Pin (2460) nor into Plate 2x2 with Pin (2476a)
Reply
RE: Part Snapping missing/errors
#68
Bug-eye 30208.dat needs a grid of studs and a big 40R cylinder:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [grid=C 4 C 4 20 20]
0 !LDCAD SNAP_CYL [gender=M] [caps=one] [secs=R 40 4] [pos=0 -4 0] [ori=1 0 0 0 -1 0 0 0 -1]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 38 4] [pos=0 -4 0] [ori=1 0 0 0 -1 0 0 0 -1]
Reply
RE: Part Snapping missing/errors
#69
Can 96910 (Tile 1 x 2 Chamfered with 2 Top Indentations) also get a snap in the center?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#70
The bottom of Plate 1x1 Round with 3 Leaves (32607) does not snap into anything, I think it should snap into standard stud.
Reply
RE: Part Snapping missing/errors
#71
Wheel spoked 4489b needs to snap to 4488 (plate 2x2 with pin) for example.

I believe this will do the trick
0 !LDCAD SNAP_CYL [group=wpAxHole] [gender=F] [caps=one] [secs=A 4 10 R 5 2] [pos=0 0 8] [ori=1 0 0 0 0 -1 0 1 0]
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#72
Plate 1x2 with thick C-clip 63868 only snaps to the left and right side bar pieces of 2540 Plate 1x2 handle.
Should also snap to the center bar.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#76
(2020-11-30, 19:16)Jaco van der Molen Wrote: Plate 1x2 with thick C-clip 63868 only snaps to the left and right side bar pieces of 2540 Plate 1x2 handle.
Should also snap to the center bar.

This seems to be fixed, although it can be a little tough to fit it to the middle bar since the outer parts seem to win it from the middle snap info.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#73
Minifig Flame/Plume triple 64647 should also snap at the small bar piece to snap to parts with clips (like 60475b Brick 1x1 with clip vertical Thick C-clip)

0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=R 4 6] [center=true] [slide=true] [pos=0 -3 0]
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#74
Brick 1x2x5 without inner ridges (46212a) does not have snap info at the bottom, only the studs on top.

0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 20] [pos=0 120 0] [grid=C 2 1 20 0]
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#75
Part 4739 Treasure Chest Lid should have snap info for the studs too.

0 !LDCAD SNAP_CYL [ID=studC] [gender=M] [caps=one] [secs=R 6 4] [pos=30 0 0]
0 !LDCAD SNAP_CYL [ID=studC] [gender=M] [caps=one] [secs=R 6 4] [pos=10 0 0]
0 !LDCAD SNAP_CYL [ID=studC] [gender=M] [caps=one] [secs=R 6 4] [pos=-10 0 0]
0 !LDCAD SNAP_CYL [ID=studC] [gender=M] [caps=one] [secs=R 6 4] [pos=-30 0 0]
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#77
I've processed all up to msg #75

I also added lots of info for the 20-01 library (I'm behind 3 libraries now Sad )

As always the latest (test) shadow is at:

http://www.melkert.net/action/download/shadow.sf


(2020-11-30, 19:18)Jaco van der Molen Wrote: Minifig Flame/Plume triple 64647 should also snap at the small bar piece to snap to parts with clips (like 60475b Brick 1x1 with clip vertical Thick C-clip)

I fixed the snap info but due to a bug in the snapping solver it won't snap correct, this will be fixed in 1.7 Alpha 1.
Reply
RE: Part Snapping missing/errors
#78
(2021-03-06, 22:37)Roland Melkert Wrote: I've processed all up to msg #75

I also added lots of info for the 20-01 library (I'm behind 3 libraries now Sad )

As always the latest (test) shadow is at:

http://www.melkert.net/action/download/shadow.sf


I fixed the snap info but due to a bug in the snapping solver it won't snap correct, this will be fixed in 1.7 Alpha 1.

Great! Looking forward to 1.7 Alpha 1 ;-)
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#79
Part 28192 Slope Brick 45  2 x  1 with Cutout and without Stud is missing snap info.

should be something like this?

0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 8 0]
0 !LDCAD SNAP_CYL [gender=M] [caps=one] [secs=R 6 4] [pos=0 24 -20]
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#80
(2021-03-11, 21:28)Jaco van der Molen Wrote: should be something like this?
Almost,

I woud add this to s\28192s01.dat :

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 8 0]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 24 -20]
Reply
RE: Part Snapping missing/errors
#81
(2021-03-12, 0:57)Roland Melkert Wrote: Almost,

I woud add this to s\28192s01.dat :

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 8 0]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 24 -20]

Big Grin
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#82
Dish 2x2 both 2654a.dat and 2654b.dat have no snap info.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#83
Slope brick 45 2x1 inverted 3665a.dat has no snap info at the bottom.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#84
Wheel 2.8x34 [] for Wheel Holding Pin (4489a.dat) does not snap into Plate 2x2 with Wheel Pin (4488.dat).
Reply
RE: Part Snapping missing/errors
#85
Brick  2 x  2 with Ball Socket Type X and Axlehole

57910 and 92013 (type 1 and 3) are both missing the snap info for the ball in the socket.
62712 (type 2) does have this.

I think you can copy the info from 62712 to both 57910 and 92013?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#86
(2021-05-20, 10:49)Jaco van der Molen Wrote: I think you can copy the info from 62712 to both 57910 and 92013?

I added:
Code:
0 !LDCAD SNAP_CLEAR [ID=axle]
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 8  A 6 16] [pos=0 24 0]
0 !LDCAD MIRROR_INFO [baseFlip=Z] [counterPart=self]

to all three, and variations of:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 5] [pos=40 10 11.5] [ori=1 0 0 0 0 1 0 -1 0]
0 !LDCAD SNAP_GEN [group=techBallJnt] [gender=F] [bounding=sph 12.7] [match=size] [placement=free] [pos=40 10 0] [mirror=none]

The half socket subparts.
Reply
RE: Part Snapping missing/errors
#87
(2021-05-20, 20:00)Roland Melkert Wrote: I added:
Code:
0 !LDCAD SNAP_CLEAR [ID=axle]
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 8  A 6 16] [pos=0 24 0]
0 !LDCAD MIRROR_INFO [baseFlip=Z] [counterPart=self]

to all three, and variations of:

Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=none] [secs=R 6 5] [pos=40 10 11.5] [ori=1 0 0 0 0 1 0 -1 0]
0 !LDCAD SNAP_GEN [group=techBallJnt] [gender=F] [bounding=sph 12.7] [match=size] [placement=free] [pos=40 10 0] [mirror=none]

The half socket subparts.

Thanks!
Is the shadow updated?
http://www.melkert.net/action/download/shadow.sf
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#88
41682 Bracket 2 x 2 with 1 x 2 Vertical Studs does not snap at the bottom of the 1x2 plate.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
#89
Wheel rim 2998 does not snap correctly to wheel hub 2999. It ends up rotated 90° from where it should be.
Reply
RE: Part Snapping missing/errors
#90
(2021-09-30, 3:28)N. W. Perry Wrote: Wheel rim 2998 does not snap correctly to wheel hub 2999. It ends up rotated 90° from where it should be.

This is one of those parts I haven't seen in real life (didn't even realize the pairing), so I took a guess on it.

How should 2999 be positioned with a 2998 at 0,0,0?

edit, I think this should work:

2999a.dat
Code:
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=F] [bounding=cyl 17 32] [pos=0 0 9] [ori=0 -0 -1 1 -0 0 -0 -1 0]
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=F] [bounding=cyl 17 32] [pos=0 0 -9] [ori=-0 -0 1 1 -0 0 0 1 0]

2998.dat
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=R 23 3  R 20 4  R 18 56  _L 19 2] [slide=true] [pos=0 -31 0] [ori=0 0 1 0 -1 0 1 0 -0]
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=M] [bounding=cyl 17 32] [pos=0 1 0]
Reply
RE: Part Snapping missing/errors
#91
The numbers are mixed up…but this is what works for me:

2998a.dat
Code:
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=F] [bounding=cyl 17 23] [ori=0 0 -1 1 0 0 0 -1 0]

Position should stay at 0 0 0, and there doesn't seem to be a need for the second snap. This wheel only seems to fit one way.

2999.dat
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=R 23 3   R 20 4   R 18 56   _L 19 2] [slide=true] [pos=0 -31 0] [ori=0 0 1 0 -1 0 1 0 0]
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=M] [bounding=cyl 17 23] [pos=0 11 0]

This is fine with the pos adjusted to 0 11 0. (The original was 0 12 0 and was off by 1 LDU.)
Reply
RE: Part Snapping missing/errors
#92
(2021-10-01, 2:05)N. W. Perry Wrote: The numbers are mixed up…but this is what works for me:

2998a.dat
Code:
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=F] [bounding=cyl 17 23] [ori=0 0 -1 1 0 0 0 -1 0]

Position should stay at 0 0 0, and there doesn't seem to be a need for the second snap. This wheel only seems to fit one way.

2999.dat
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=R 23 3   R 20 4   R 18 56   _L 19 2] [slide=true] [pos=0 -31 0] [ori=0 0 1 0 -1 0 1 0 0]
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=M] [bounding=cyl 17 23] [pos=0 11 0]

This is fine with the pos adjusted to 0 11 0. (The original was 0 12 0 and was off by 1 LDU.)

The hub is free movable in the arm without the wheel. But it should snap to its final position in LDCad, I think.
The wheel can be connected in one way only. It's not possible to connect it with the backside turned to the outside.
Reply
RE: Part Snapping missing/errors
#94
(2021-10-01, 7:54)Max Martin Richter Wrote: The hub is free movable in the arm without the wheel. But it should snap to its final position in LDCad, I think.
The wheel can be connected in one way only. It's not possible to connect it with the backside turned to the outside.

The arm is 6540a/b, by the way. I did check the fit of all three parts, and with the 0 11 0 position on the wheel rim, everything lines up snugly.
Reply
RE: Part Snapping missing/errors
#93
Is it possible, and maybe even wanted, to have 2907 snap to the inside of the hub 2999 ?
Reply
RE: Part Snapping missing/errors
#95
(2021-10-01, 15:24)Magnus Forsberg Wrote: Is it possible, and maybe even wanted, to have 2907 snap to the inside of the hub 2999 ?

Good question…I am not fortunate enough to have owned the set these parts came in (but can you guess what I've been building?). But while 2907 is meant to rotate on XZ along with 2999, it is also meant to pivot independently on XY. So perhaps snapping is not recommended?
Reply
RE: Part Snapping missing/errors
#96
(2021-10-01, 17:10)N. W. Perry Wrote: Good question…I am not fortunate enough to have owned the set these parts came in (but can you guess what I've been building?). But while 2907 is meant to rotate on XZ along with 2999, it is also meant to pivot independently on XY. So perhaps snapping is not recommended?
I think it can snap: this is the same kind of joint type as 32494/92906.
Reply
RE: Part Snapping missing/errors
#97
(2021-10-01, 17:10)N. W. Perry Wrote: Good question…I am not fortunate enough to have owned the set these parts came in (but can you guess what I've been building?). But while 2907 is meant to rotate on XZ along with 2999, it is also meant to pivot independently on XY. So perhaps snapping is not recommended?

Seems logical, acting like a compact universal joint like in real cars.

   
Reply
RE: Part Snapping missing/errors
#98
(2021-10-01, 18:24)Roland Melkert Wrote: Seems logical, acting like a compact universal joint like in real cars.

Hey, they more possibilities, the better!

Will the snapping data depend on the orientation of the grooves (as was recently corrected in the PT)?
Reply
RE: Part Snapping missing/errors
#99
(2021-10-01, 18:46)N. W. Perry Wrote: Will the snapping data depend on the orientation of the grooves (as was recently corrected in the PT)?

It could if it uses a generic sphere meta using absolute placement.

That would get it in a good starting position, so the user can slide it inside and rotate/bend the attached axle later on.

Like so (including the corrections reported above)

2999.dat
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=R 23 3  R 20 4  R 18 56  _L 19 2] [slide=true] [pos=0 -31 0] [ori=0 0 1 0 -1 0 1 0 0]
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=M] [bounding=cyl 17 32] [pos=0 2 0]
2907.dat
Code:
0 !LDCAD SNAP_GEN [gender=M] [bounding=sph 15] [ori=0.92388 0 0.382683 0 1 0 -0.382683 0 0.92388]

2998a.dat
Code:
0 !LDCAD SNAP_GEN [group=techWhlCon1] [gender=F] [bounding=cyl 17 32] [pos=0 0 9] [ori=0 0 -1 1 0 0 0 -1 0]

optimally it would need a new snap connection (sphere in a tube), but I'm not sure it would really be that more helpful.
Reply
RE: Part Snapping missing/errors
(2021-10-01, 19:21)Roland Melkert Wrote: optimally it would need a new snap connection (sphere in a tube), but I'm not sure it would really be that more helpful.

I was thinking of something like the SLIDE property, where it snaps in one place but can then freely rotate.
Reply
RE: Part Snapping missing/errors
(2021-10-01, 20:07)N. W. Perry Wrote: I was thinking of something like the SLIDE property, where it snaps in one place but can then freely rotate.

You could fake that by using a square or axle SNAP_CYL pair, to force the 'teeth' inline with he nudges inside the hub connector (those connections are forced at 90 deg rotation).

The snap meta on 2907 will still need a 22.5 deg rotate to force the offset as the current official part doesn't align at rest.
Reply
RE: Part Snapping missing/errors
(2021-10-01, 20:27)Roland Melkert Wrote: You could fake that by using a square or axle SNAP_CYL pair, to force the 'teeth' inline with he nudges inside the hub connector (those connections are forced at 90 deg rotation).

The snap meta on 2907 will still need a 22.5 deg rotate to force the offset as the current official part doesn't align at rest.

Please remember, that the official 2907 has an error with the teeth and the axle orientation. This (wrong) correction erroneously jumped through the review process and got official. As the fixed part just needs an admin cert it will surely included in the next parts update.

/Max
Reply
RE: Part Snapping missing/errors
I can't tell if this is a bug or a feature, but I noticed some studless Technic beams were missing their axlehole snaps. I figured out that this was because they use axlehole prims with unofficial updated versions (which I have set to be first in my search paths).

I added the appropriate snap_include to the unofficial primitive file, and now when I edit the part itself the snap info is there, but in the actual model (and part bin) it is not there. How do I get the snap info from unofficial prims to appear in the model?
Reply
RE: Part Snapping missing/errors
(2021-10-22, 4:38)N. W. Perry Wrote: I can't tell if this is a bug or a feature, but I noticed some studless Technic beams were missing their axlehole snaps. I figured out that this was because they use axlehole prims with unofficial updated versions (which I have set to be first in my search paths).

I added the appropriate snap_include to the unofficial primitive file, and now when I edit the part itself the snap info is there, but in the actual model (and part bin) it is not there. How do I get the snap info from unofficial prims to appear in the model?
Which part number?

The bin and editor use the exact same data, they might render differently though (for snap editing purposes)
Reply
RE: Part Snapping missing/errors
(2021-10-22, 18:44)Roland Melkert Wrote: Which part number?

The bin and editor use the exact same data, they might render differently though (for snap editing purposes)

Part number is axlehol4.dat.

I copied this snap info into the unofficial primitive:
0 !LDCAD SNAP_INCL [ref=axlehole.dat]

It shows up fine in the parts that reference it, if opened in their own session:
   
And if I view the dependencies of those parts, it shows that they are indeed referencing the unofficial version of axlehol4.
But in the model session, the snap is missing:
   
Reply
RE: Part Snapping missing/errors
Edited...
42862s01 is missing connectivity:
Forget this one, my shadow was not up to date!

41862 tubes of vertical plate are backwards. Connectivity should be:
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 -10 4] [ori=-1 0 0 0 0 1 0 1 0] [grid=C 2 1 20 0]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [pos=0 8 0] [grid=C 2 C 2 20 20]
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 2 Guest(s)