Quite often you want to use the same generic subassembly twice but you need the ability to distinguish between them with codes. It would be excellent if we could prefix or suffix all the codes used in the default subassemblies as shown below.
This enables a lot of flexibility for the styling of codesets and creating separated surfaces. It can resolve issues with codes overlapping each other.
Things like different options, left right, center etc. can all be established within the one corridor. Making it easier to link things together and create surfaces etc…
It would be incredibly useful to allow certain aspects of Civil 3D styles to change dependent on the scale they are visible at. (other than just the size, which happens already of course!)
This could be done at style level or object level or even better both? one overrides the other.
Fox example
Contour Intervals could change depending on the scale
Alignment Intervals could change dependant on scale.
Style could also allow visibility of certain objects only at certain scales.
Components could display different information at different scales (labels could become more or less complex)
Dragged states could have different locations for different scales (similar to annotative scaling already for regular autocad objects)
I particularly like the way arcgis handles this with scale ranges that make sense, like room, county, building,continent etc..
Projection sets would allow you to create a dynamic editable “query” to group desired objects that you want to use for projection. This query also defines how these objects should be displayed in profile/section views/exaggerated views?.
I’ll let the image below explain itself. But generally a few key points.
ALL Objects are Available for Projection!!!
ALL Objects can be assigned labels as well as projections styles
BOTH Profile Views/Sections views have similar projection options (Crossing/Superimposed/Bounding Box limit etc, explained further below)
Queries can be assigned to objects so that they can be assigned default styles based on the point group or there layer or whatever.
The same projection set can be used for multiple profile views etc.. Its dynamic..When it updates it updates the profile view/section nview etc.
Projection Options/Types
It’s really important that we have options to filter how objects are selected/cut/displayed in section/profile views.
I’m thinking there could be two/three types.
These would be saved as styles and can be changed/updated.
Crossing Only Only objects that intersect the line are displayed
Bounded Parameters Only objects within specified parameters can be seen. I.E 25m either side of alignment. Similar to how the sample line projections work now. This should be enabled for profiles views as well of course!
Bounded Objec Only objects within a selected polygon are sampled. This would allow flexibility for users to limit things by stage boundaries etc..
I’m aware I can save changes to my command using the settings tab in toolspace.
However wouldn’t it be nicer if we could just save settings for any command we are in as we need to? Its pretty annoying to have to keep going back to the settings to tab to toggle this on and off as you need to.
It would be even nicer if we could save many defaults and reload them as we need to as well. Sort of like styles for commands?
1. There is no way to sort or “re-order materials” in either the main dialog. OR the Criteria Dialog. Very frustrating!
2. Structures added manually can’t be deleted (this is definitely a bug!)
3. When creating large criteria or editing manually. It would be good if the “delete” key worked and multiple lines can be selected at once and deleted. As having to go up to that red cross can be very time consuming when editing large criteria etc. Particularly when everytime you delete something the selection moves completely away from where you were working.
4. Find/replace functionality on the names used in the criteria would also save a lot of time as well. You want to use the criteria on a different area of your design and all you need to do is change a suffix. Otherwise the “map objects by name” doesn’t work (find replace functionality in every civil 3d list box would save a lot of time)
5. It would be excellent if shape codes could be split somewhat by a surface. So (area volume in shape code above <selected surface>/area volume in shape code below <selected surface>. This negates having to create – 4-5 extra surfaces to calculate complex geometry represented by a shape.
Civil 3D news/tips/tricks from someone like you and also some Unity Game Development stuff
