LDCad Part Snapping missing/errors


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
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-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
(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
RE: Part Snapping missing/errors
(2021-11-27, 16:19)Philippe Hurbain Wrote: Forget this one, my shadow was not up to date!

I haven't updated this threads main version for some time, I was hoping to complete the 20-01 library first and include it in 1.7 Alpha 2, but haven't found the time for it yet Sad
Reply
RE: Part Snapping missing/errors
6587 (axle 3 with stud) snapping currently uses an axle meta with round section to make the stud. But this is wrong since the axle meta forces orientation of plate/tile placed on stud (moreover the hole in stud is not modeled).
Correction:
Code:
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=A 6 58   R 8 2] [center=true] [slide=true] [ori=0 -1 0 1 0 0 0 0 1]
0 !LDCAD MIRROR_INFO [baseFlip=Z] [counterPart=self]
instead of
Code:
0 !LDCAD SNAP_CLEAR
0 !LDCAD SNAP_CYL [gender=M] [caps=none] [secs=A 6 58   R 8 2   R 6 4] [center=true] [slide=true] [pos=2 0 0] [ori=0 -1 0 1 0 0 0 0 1]
0 !LDCAD MIRROR_INFO [baseFlip=Z] [counterPart=self]
Reply
RE: Part Snapping missing/errors
Not really a shadow problem, but the stud of the telescope (64644) is next to impossible to insert into tube of plate 1x1 round (6141). Most of the time, the telescope jumps to connect its tube to plate stud. Moving the plate instead doesn't help. It works much better with a regular plate 1x1 (3024)!
Reply
RE: Part Snapping missing/errors
For the part "Technic Sprocket Wheel 25.4" (57520), the following places snap points for each of the sprocket notches. That in turn makes placing the chain tread (57518) somewhat less fraught.


0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [slide=true] [pos=0 -30 0] [ori=-1 0 0 0 0 1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [slide=true] [pos=0 30 0] [ori=1 0 0 0 0 -1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [slide=true] [pos=-25.980762 -15 0] [ori=-1 0 0 0 0 -1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [slide=true] [pos=-25.980762 15 0] [ori=1 0 0 0 0 -1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [slide=true] [pos=25.980762 -15 0] [ori=-1 0 0 0 0 -1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [slide=true] [pos=25.980762 15 0] [ori=1 0 0 0 0 -1 0 -1 0]


David
Reply
RE: Part Snapping missing/errors
(2022-02-24, 4:04)David Manley Wrote: For the part "Technic Sprocket Wheel 25.4" (57520), the following places snap points for each of the sprocket notches. That in turn makes placing the chain tread (57518) somewhat less fraught.

Very useful, I added:

Code:
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [pos=0 -30 0] [ori=-1 0 0 0 0 1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [pos=25.980762 -15 -0] [ori=-0.5 -0 -0.866025 -0.866025 -0 0.5 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [pos=25.980762 14 -0] [ori=0.5 -0 -0.866025 -0.866025 -0 -0.5 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [pos=0 30 0] [ori=1 0 0 0 0 -1 0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [pos=-25.980762 14 -0] [ori=0.5 0 0.866025 0.866025 -0 -0.5 -0 -1 0]
0 !LDCAD SNAP_CLP [radius=4] [length=10] [center=true] [pos=-25.980762 -15 -0] [ori=-0.5 0 0.866025 0.866025 -0 0.5 -0 -1 0]

to s\57520s02.dat

Only difference with yours are the clip orientations which may come into play in a future version of the snapping engine.
Reply
RE: Part Snapping missing/errors
(2022-02-24, 19:14)Roland Melkert Wrote: </snip>

Only difference with yours are the clip orientations which may come into play in a future version of the snapping engine.

Thanks Roland.

When I was tutu-ing with configuring the snap information for the part, I had played about with the orientation and decided it wasn't that significant. However, it is useful to know that there may be benefits to more properly orientating the clips.

It's interesting that the Y co-ordinate of two of the points are changed from 15 to 14. I thought the sprocket would be symmetrical (not that I actually checked!), which is why I used -15 and 15. Presumably s\57520s02.dat reflects the effective Y values as being -15 and 14 hence why you used those two values.

Regards,

David
Reply
RE: Part Snapping missing/errors
(2022-02-24, 22:08)David Manley Wrote: It's interesting that the Y co-ordinate of two of the points are changed from 15 to 14. I thought the sprocket would be symmetrical (not that I actually checked!), which is why I used -15 and 15. Presumably s\57520s02.dat reflects the effective Y values as being -15 and 14 hence why you used those two values.

No, you are right.

Something went wrong they should be at 15.

Don't know how that happened as I rotated duplicates of the top one using 0,0,0 as a rotation center.
Reply
RE: Part Snapping missing/errors
For part 41682 (Bracket 2 x 2 - 1 x 2 Up Centred), I can't seem to attach to the back of the vertical plate. The front of the vertical plate is fine.

From playing around a bit, I think that this line:

0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 -10 0] [ori=1 0 0 0 0 1 0 -1 0] [grid=C 2 1 20 0]

should be:

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]

Regards,

David
Reply
RE: Part Snapping missing/errors
(2022-03-07, 6:48)David Manley Wrote: For part 41682 (Bracket 2 x 2 - 1 x 2 Up Centred), I can't seem to attach to the back of the vertical plate. The front of the vertical plate is fine.

Yes, I made the same correction in response of post #88 but hadn't updated the shadow.sf mentioned in this thread for ages.
Reply
RE: Part Snapping missing/errors
I've processed all thing people mailed me about and things mentioned above up to message #115.

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).
Reply
RE: Part Snapping missing/errors
Part 12818 is missing its bottom snap info:
Code:
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=10 144 -50]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=50 144 -10]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [pos=30 144 -50] [grid=1 2 0 20]
0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=R 6 4] [pos=50 144 -30]

(This should also work for unofficial part 79393.)
Reply
RE: Part Snapping missing/errors
The Grill Tile is missing snap info on the flat thing in the centre. Should stick to the inside of the hollow stud.

   
Reply
RE: Part Snapping missing/errors
(2021-12-04, 11:03)Philippe Hurbain Wrote: Not really a shadow problem, but the stud of the telescope (64644) is next to impossible to insert into tube of plate 1x1 round (6141). Most of the time, the telescope jumps to connect its tube to plate stud. Moving the plate instead doesn't help. It works much better with a regular plate 1x1 (3024)!

I've investigated this and it is caused by the 'keep sliding info sticky to last match' mechanics.

This is proven by it working more like expected after you remove all 'slide' checks from the involved part's snap info.

Thing is I'm not sure how to improve this so both scenarios work no matter the info configuration.
Reply
RE: Part Snapping missing/errors
These are both very new parts, but 73825 and 79389 need bottom snap info for their 1x1 plate sections.

EDIT: Also 78256 and 79756.
Reply
RE: Part Snapping missing/errors
(2022-04-11, 3:15)N. W. Perry Wrote: These are both very new parts, but 73825 and 79389 need bottom snap info for their 1x1 plate sections.

EDIT: Also 78256 and 79756.

Those are from the 22-01 library, I'm still processing 20-01 Angry
Reply
RE: Part Snapping missing/errors
(2022-04-11, 18:36)Roland Melkert Wrote: Those are from the 22-01 library, I'm still processing 20-01 Angry

Any way we can help? These files should be very easy to copy-paste from other library parts. Or, we can limit suggestions for now to 2019 and earlier.
Reply
Important: LDCad shadow issue when used with the 22-03 library.
Just wanted to let people know there is a potential circular reference problem in LDCad's shadow library when used combined with the new 22-03 Library.

Normally circular references are detected during loading, but this is a 'cross reference' one where only the combined data from library and shadow will have the problem.

The bug caused these kinds of references to be missed when the parts involved are loading at the same time. If so it will crash the program.

1.7 Alpha fixes the issue:
Code:
Error    | Circular reference detected to "axl2hol8.dat" from "axl2hole.dat", reference will be cleared and rendered as "missing".

I'm hoping to release the new 1.7 version very soon.

In the meantime it can be prevented by deleting (or editing) axl2hol8.dat from LDCad's shadow library.
Reply
RE: Part Snapping missing/errors
Part 54200 (slope brick 31 1 x 1 x 0.677 / cheese slope) no longer has snap info?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
(2022-07-12, 10:48)Jaco van der Molen Wrote: Part 54200 (slope brick 31 1 x 1 x 0.677 / cheese slope) no longer has snap info?

I had the same problem: I updated shadow info but main part library stayed one version behind. Updating the main ldraw library solved the problem. Isn't it your case as well?

Details: Newest shadow library matches the newest main ldraw library, where 54200 was rewritten using a subpart - and shadow info is for that subpart now.
Reply
RE: Part Snapping missing/errors
(2022-07-12, 11:46)Milan Vančura Wrote: I had the same problem: I updated shadow info but main part library stayed one version behind. Updating the main ldraw library solved the problem. Isn't it your case as well?

Details: Newest shadow library matches the newest main ldraw library, where 54200 was rewritten using a subpart - and shadow info is for that subpart now.

Ah, OK. I think I am up to date, but will check. Tnx for pointing this out.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
(2022-07-12, 13:16)Jaco van der Molen Wrote: Ah, OK. I think I am up to date, but will check. Tnx for pointing this out.

Hi,

I am slightly confused about something,

I can see that there is (for example) shadow/p/stud.dat but why does ldraw/parts/3024.dat not just use that?
instead, there is shadow/parts/3024.dat and it uses shadow/p/stud.dat, and then shadow/parts/3024.dat links to /ldraw/parts/3024.dat

Because then LDRAW part authors can just use shadow/p/ (which will almost always have the correct primative in it anyway) and not wait for ldcad to update /shadow/parts

Now I know 3024 has all of the primative snapping info intact but what about something like ldraw/parts/86996.dat which most probably have the correct primative snapping in the shadow library, but is not snapping on the bottom (antistud/clutch)

Perhaps someone can clear this up? If this is not on-topic I guess I could just PM roland.
Reply
RE: Part Snapping missing/errors
(2022-07-22, 13:59)SNIPE Wrote: Perhaps someone can clear this up?
I'm not entirely sure what you mean but:

The shadow is basically a patch to be applied to the official ldraw library.

Information can be inherited (like stud.dat) or included from another shadow file.

Parts without a shadow file will only inherit. So they usually end up without bottom connectivity because there are no useful primitives involved for shaping the antistuds.
Reply
RE: Part Snapping missing/errors
(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.

Note: make sure that the part you are reporting is official

42924 "Pin long with friction Type 2" and 61332 "Pin with friction Type 2" missing ?
If you don't understand my english, that's normal, me too !
Reply
RE: Part Snapping missing/errors
(2022-10-31, 17:23)Marc Giraudet Wrote: 42924 "Pin long with friction Type 2" and 61332 "Pin with friction Type 2" missing ?

Those were just released last update and use new pin primitives. There is some lag time since Roland has to manually update his shadow lib.
Reply
RE: Part Snapping missing/errors
(2022-10-31, 18:07)Orion Pobursky Wrote: Those were just released last update and use new pin primitives. There is some lag time since Roland has to manually update his shadow lib.

Make that a lot of lag, as I haven't had time for it at all lately.

I was hoping the github repository would help me improve on this.
https://github.com/RolandMelkert/LDCadShadowLibrary

But no pull requests so far.
Reply
RE: Part Snapping missing/errors
(2022-11-07, 22:57)Roland Melkert Wrote: Make that a lot of lag, as I haven't had time for it at all lately.

I was hoping the github repository would help me improve on this.
https://github.com/RolandMelkert/LDCadShadowLibrary

But no pull requests so far.

OK, nice, but how does one make a offLibShadow.csl file from that?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
(2022-11-08, 7:42)Jaco van der Molen Wrote: OK, nice, but how does one make a offLibShadow.csl file from that?

You can download the whole repository (green 'code' button top right) or use a local git installation to clone it.

Then in LDCad you point the shadow to the root directory (holding parts and p) just like the normal library locations.


If you really want a csl, just (re)zip the contents making sure the parts and p folders are the root folders inside the zip and rename it to csl.

The downloaded zip can't be used directly because at the moment LDCad doesn't compensate for the 'LDCadShadowLibrary-main' root folder inside it.

This is something that will be improved upon in the next version (It will support using the github downloaded zip as is).
Reply
RE: Part Snapping missing/errors
(2022-11-09, 21:16)Roland Melkert Wrote: You can download the whole repository (green 'code' button top right) or use a local git installation to clone it.

Then in LDCad you point the shadow to the root directory (holding parts and p) just like the normal library locations.


If you really want a csl, just (re)zip the contents making sure the parts and p folders are the root folders inside the zip and rename it to csl.

The downloaded zip can't be used directly because at the moment LDCad doesn't compensate for the 'LDCadShadowLibrary-main' root folder inside it.

This is something that will be improved upon in the next version (It will support using the github downloaded zip as is).

Ah yes, the csl is just a zip.
I will try this. Tnx.
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
(2022-11-14, 17:42)Jaco van der Molen Wrote: Ah yes, the csl is just a zip.
I will try this. Tnx.

OK, this works. I downloaded, unpacked, made a re-zip, etc.
I found another brick with missing snap info (92946) and created a file for that (attached)

.dat   92946.dat (Size: 301 bytes / Downloads: 0)
Now, can I contribute this file to the Github repos?

Is the contents correct like so:

Code:
0 LDCad shadow info for "Slope Plate 45.73  2 x  1"

0 Author: LDCad Shadow Library
0 !LICENSE CC BY-SA 4.0, see LICENSE.md

0 !HISTORY 2022-11-16 {Jaco van der Molen} Initial info for 15672.dat copy to 92946

0 !LDCAD SNAP_CYL [gender=F] [caps=one] [secs=S 6 4] [pos=0 8 0] [grid=1 C 2 0 20]
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: Part Snapping missing/errors
(2022-11-16, 9:49)Jaco van der Molen Wrote: Is the contents correct like so:

Looks ok to me, but maybe use "Initial info for 92946.dat (copy of 15672.dat)" as the description?
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 2 Guest(s)