Rule 1 – Do not use Template Transitions
This tool is impossible for novices to understand. It is also impossible for experts to understand. It is doubtful that even the creator of the tool understands. It is messy. It is ugly. It is unworkable. Do not under any circumstances use this tool. If your road is transitioning, well then, make the templates do the transitioning.
If your road is to suddenly lose its curb and gutter, then let it. If it needs some additional details after the curb and gutter, then use a separate, simple template that does the work. No one but the original modeler will understand the template transition, if they even do understand it. Make things simple for yourself. Use modular and simple templates.
Rule 2 – Avoid Corridor Clipping
Clipping corridors is hard for anyone to notice. It is also hard for the modeler to remember he clipped the corridor. This is confusing and hard to remember.
So why do it?
If you want two things to meet in the middle while not looking silly, then model it right the first time around. Choose which corridor ought to have a gap and then, well, give it a gap. Drop the same template twice, one on either side of the gap. For extra design intent, put a template whose only point is a Null point, invisible to all, within the gap. That way, all modelers know that the gap was intentional. Keep your templates and corridors modular and simple.
Rule 3 – Stop doing End Condition Exceptions
There is absolutely no need for this ridiculous button.
The idea is to make side slopes disappear at certain parts of a corridor. It works with a template’s swarm of special points. Only they aren’t special; they’re over complicated. If you wish for a side slope to not appear along a corridor, then do not drop a template there. If you had a modular and simple template and you wanted it to run a mile down a corridor except for 100 feet near the middle, then you would apply two template drops; one before the gap and one after the gap. Done. Did you need extra points on your template to control End Condition Exceptions? No! Why make everyone have to peel back layers of the model to figure out why you placed an End Condition Exception? Why hide your secrets inside a template’s 80 points? Make your templates modular and simple.
Rule 4 – Skip Design Stages
Design stages are meant to increase the number of template drops as the project moves to completion.
Why do this at all?
The only argument is that it saves on computer loading times. If the corridors were modular and simple, then computer loading times are never an issue. Toss this thing out. It muddies up modeling. The simpler modeling is, the better.
Rule 5 – Use Parametric Constraints and Point Controls
These are the only things you need when modeling templates.
Do you see the simplicity now?
A simple lane template, modeled with Parametric and Point Controls. Any novice can understand that. Any new grad can be onboarded in less than a few weeks. Anyone on your team can help you when the deadline is this week. The more simple models are, the more people can help you. The more simple models are, the less costly mistakes are. The more simple models are, the less miserable you are.
