Create two input parameters, rename one, delete the other. Subassembly composer freezes.
been there since 2013! please fix
Have been told that this will be fixed in the later release!
Create two input parameters, rename one, delete the other. Subassembly composer freezes.
been there since 2013! please fix
Have been told that this will be fixed in the later release!
You might be already well aware you need a custom subassembly (CS) because things are getting hectic, so you can skip this article
It is always a good idea to stop and determine “if I even need to” though. So, if you’re not sure, here are some general rules of thumb to follow to determine if you need a CS.
You should create a CS if:-
1. Your Corridor Model requires you to transition daylight slopes smoothly over distance. I.E 1:2 up to 1:6 and back to 1:2 over specified distances
2. Your corridor model has a complicated target list, say 5 or more targets you need to specify. Particularly elevation/grade targets. These can take longer to manage as they are usually all different targets, unlike surfaces which are typically all just EG and can be set all at once.
This list can grow long very quickly! Particularly when you start changing the targets between regions etc.
3. Managing your codes (point/link/shape) is becoming difficult to manage
4. You want to develop multiple stages to calculate volumes over time. Similar to above.
5. You wish to calculate internal materials that differ from the generic/road based subassemblies provided by the software. (plus making surfaces is difficult due to differing boundary conditions)
These are a few good signs that creating a CS will benefit you. However as an umbrella rule,
if it is taking too much time….. take some time… to create a CS.