Has anyone used marked points much with the subassembly composer?
It appears to work good for "static" geometry. By static, I mean points & links that are always built.
I have a retaining wall subassembly that builds one block at a time then checks the depth to see if it needs more. Once it reaches it's target I assigned a marked point code. The geometry is very fluid in the sense that the number of blocks vary.
When I try to use it neither one of the "link to marked point" subassemblies work.
Any one else used marked points and geometry that is NOT static?
Solved! Go to Solution.
Sure, It might be crude but it's effective.
The first thing it does is compare the depth at the starting point against the "MinDepth" parameter to see if you want a wall. If not, it jumps over and creates a simple Cut/Fill slope.
If it does trigger the wall then it creates a point and labels it "WallStart" then checks if it's Cut or fill. Then creates the first block and checks depth to see if it needs another block. If not, it creates the slope behind the wall, labels the "WallEnd" code and is SUPPOSE TO create THE MARK POINT.
If it needs another block then it sets the batter offset based on input parameters and then creates the second block and starts the process all over again.
Side note to ADSK: This is where we could really use a "do loop"
I have it setup to build UP TO 14 blocks right now.
I have only added the "Marked Point" feature to the first 3 blocks in Cut and Fill for testing so make sure you are in that height range when testing.
You will also see that you need to set the wall target in the corridor. That is because there are times we have one wall targeting existing ground and other walls might be targeting a proposed surface (pond for example).
The default settings are for a keystone standard block unit.
Any luck on the marked point issue?
I have also been unable to get a set mark point generated in SAC to work properly in Civil 3D.
I did also clean up the logic on your subassembly, see attached (was trying to figure out if something else was causing the mark point to not work).
Thanks for verifying the marked point issue isn't just something I'm doing wrong.
Your coding is way cleaner then mine, THANK YOU!
It's nice to see your thought process in the coding, even though I didn't know you could use some of those conditions.
As you can tell, I'm a rookie with programming.
Glad to have given you a different perspective on code set up. There are often so many different ways to approach the same problem. As long as the logic makes sense to the person generating it (or the person who has to debug it or change it later) then that is all that matters.
If you (or any others reading this post) are going to be at AU2011 I would hope you would consider signing up for my lecture on SAC!
I am going and had already signed up for your class before I even knew about your mad programming skills
One thing that I have found with custom subassemblies is that you need to use the same point number at the location where you will be attaching other subassemblies. So the point number of the location in layout mode needs to be the same point number in each possible condition of the subassembly.
An example of this is a subassembly that changes shape based on cut and fill. In order to attach daylight, or marked point to the outermost point of the subassembly, the 'connection' point was assigned point number P12 in both instances.
How did you do that? Was that using the subassembly composer?
I get an error when trying to use the same number over again.
"Point number already in use, change to "XX" ?
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register