Direction of a Surface Towards a Point – Examples

I have described earlier a pretty confusing procedure, which does something…but no one knows what exactly. The first example will be about a stable (in terms of change in Parent orientation) Shape Fillet:


As we can see in the clip, change in Join orientation doesn’t ruin Shape Fillet. And you can control orientation through a change in the position of stabilizing point.

Another example with trim operation:

The beginning shows what’s going on (everyone’s seen such case…), how orientation of the surface entering the Trim changes – Trim collapses. Next, after stabilization with the template described, change in the Parent orientation doesn’t cause breakdown of Trim operation, because Inverse that originated from that Join will automatically deactivate/activate and maintain direction towards the stabilizing point.

Another example is regarded as a bow towards design in the context :



A behavior analogical to the previous ones, but you can already make a theory, that everything “adopted” should be stabilized. That relieves from having to mind orientation, for example, during skeleton switching – just like this, a Constructor X stabilizes orientation once, and after, he totally doesn’t care what will happen in subsequent synchronizations…


Examples can be multiplied, but they will be definitely useful for templates, i.e., maybe it’s better to add a point and lose thinking about input orientation.


But do we really have to create a procedure that is as “complicated”? When starting something, a man has the tendency to overthink, but a procedure like that I described several years ago, in a nice way, so I threw it in here too.

Besides, you can do that in a sporty way :-)… A bit more about stabilizations later…


One would love to have automatically programmed Point Tab in an Inverse operation – but that you can do yourself, so what’s the point… nah, I’m joking – maybe after 10 years I’ll be mature enough to analyze, why Dassault didn’t make it… In Split and trim operation we have a “point” that “fool” the orientations.

And here’s available for download the previously described template :



It has of course its limitations, which will come up once you delve into its structure. But I encourage you to test it and write about what’s wrong with it. It’ll be improved on an ongoing basis – maybe it’ll turn out to be a good primer, to use something else than HD2 for the purpose of some particular case.


Comments: Be first

Recent Posts

I welcome everyone interested in CATIA . I will […]

Each Part in CATIA has its own UUID identification. It’s […]

The matter might seems trivial… it gets a bit […]

In the previous entry, I have described some of […]

And now an entry for Fetishistic B-Rep Dodgers 🙂 […]