Announcements

The Autodesk Community Forums has a new look. Read more about what's changed on the Community Announcements board.

use more than 1000 points in Subassembly Composer for p1 class

DRH_
Contributor

use more than 1000 points in Subassembly Composer for p1 class

DRH_
Contributor
Contributor

Hello, I am making a custom subesslambale and I have created more than 1000 points, and when I try to use the class p(1001.x) I get this error, any idea how to solve it?

DRH__2-1715453668587.png

 

I found this in autodesk help

DRH__3-1715453734954.png

 

 

 

0 Likes
Reply
565 Views
6 Replies
Replies (6)

nkiakas
Collaborator
Collaborator

Hi @DRH_ 

I am afraid there is no solution because you reached the limitation of the application.

What can you do?

It depends from the nature of your subassembly.

"Break" it to to sections, when each section could be another subassembly.

By the way i am curious, what subassembly could require more than 1000 points? 

DRH_
Contributor
Contributor

thanks for your time, I'm making a road subassembly and I'm adding some things like curbs, I'm going to post it on autodes C3D ideas, while I'm going to look for other solutions on .net

ecfernandez
Advisor
Advisor

Hi @DRH_, I agree with @nkiakas. So far in my career, I have created complex subassemblies and have hardly reached point 200. My recommendation is to break it down if you are facing this limitation.

 

Sometimes, we want to build complex geometries without noticing they can be broken down into smaller pieces that make the job of creating and using them easier. As an example, I can mention a subassembly I had the chance to see last week in the Autodesk Civil 3D Forums in Spanish. They had built a complete lane with a gutter at the edge of pavement and a daylight slope. They could have just created two separate subassemblies simplifying the idea and the job in SAC.

 

Best regards guys!

Camilo Fernández

Civil engineer | Specialist in design, construction, and maintenance of roadways

EESignature

LinkedIn

cwr001
Collaborator
Collaborator

I can only concur with the previous answers!

Out of curiousity I'd love to see a subassembly that contains so many nodes. You might not want to share it, but I'd be happy to see even a screenshot - that beast must be hell to maintain!

I've also noticed major performance issues with subassemblies that got too big (e.g. a ton of nested if-conditions) - this hasn't been a problem for you?

 

surafeltklt
Advocate
Advocate

i have once created subassembly file that goes like p700,it has cut and fill condition, It has a switch to about  5 categories of slope (side and bench slope) since this depends on soil class on the road section, it even calculates fill widening and it calculates shoulder rollover super elevation and i don't remember  what else it could do,it ca do retaining wall, but that file is very big i mean its about 74kb.the problem is i have to edit it every now and then to fit it to specific projects and it takes longer time to show results and i no longer use it. my point is it would have been great to have something that does every thing  with small edits but unfortunately it takes longer to edit ,so its good if you use smaller parts of sections for this purpose 

DRH_
Contributor
Contributor

Hello, the reality is that it doesn't have so many if conditionals, it has some switches and many shapes, in terms of performance I don't think it's that heavy because I try to work with a lot of order, here is the screenshot, maybe you can't see all of my work, when I finish it and optimize it I will upload a video so you can see how it works

DRH__0-1715624758615.png

 

0 Likes