Problem dealing with Loop Geometry and Links after it

Problem dealing with Loop Geometry and Links after it

apegaia34T2D
Explorer Explorer
101 Views
2 Replies
Message 1 of 3

Problem dealing with Loop Geometry and Links after it

apegaia34T2D
Explorer
Explorer

Hi, I'm currently adapting a subassembly from my company, trying to simplify it by using loop instead of repeating the geometry, but it isn't working as I expected.

 

When the section change to add a new instance of the loop (in this case, to add a bench), it seems to be creating a gap between the last point of the loop and the link after it.

apegaia34T2D_0-1756759676859.png

I do believe it's kind of an intended behaviour, as I can understand that the end point of the loop itself is really changing from a section to another, but if that's the case, is there any workaround to make it actually target the last point of the link itself? 

apegaia34T2D_1-1756759867673.png

I've been trying to fix this for days and I've tried so many things, but couldn't reach the result I wanted if not by the "go horse" approach (which I reaaaally would like to avoid). 

 

Any help is welcome! Thanks!

 

Link to download the .PKT file:

SUBASSEMBLY_TEST.pkt 

 

0 Likes
102 Views
2 Replies
Replies (2)
Message 2 of 3

nkiakas
Advisor
Advisor

Hi @apegaia34T2D 

 

I see that you use C3D 2025.

There where some bugs in subassembly composer in this version.

Take a look in the link below to check if your problem is one of the bugs or not

 

https://forums.autodesk.com/t5/civil-3d-forum/subassembly-composer-v2025-buggy/m-p/13019285#M10179

 

Regards

Message 3 of 3

apegaia34T2D
Explorer
Explorer

Hi, @nkiakas! Thanks for your quick answer!

 

It doesn't seem to be a bug related to the version of subassembly composer or civil 3d. I've recreated the assembly in the 2023 version of composer and tested it on both versions of civil 3d and in all cases I've had the same result. Also, just to mention, increasing or decreasing the frequency of the assembly doesn't really help neither, it only makes it more or less apparent.

 

Maybe it's really an expected behaviour, but if that's the case I'm searching for some kind of a workaround (maybe not using the end point of the loop itself, splitting the geometry in multiple loops or something like that).

 

 Again, any ideas would be welcome!

0 Likes