Setting + locking component pivot points

[designfilter]

I'm struggling with the pivot points of components. When I go to move a component, the pivot location is can sometimes be a great distance away from the actual component location within the model space. Hopefully, I can get the answers to these questions..

- How is the pivot point location set when a component is initially created?

- What if a component is imported, how is the pivot point location set..? relative to the imported component or relative to the modelspace I am importing into..? 

- MOST IMPORTANTLY.... How do I lock the components' pivot point location; if I choose to relocate it through the move command tab..? I find I can move the pivot point location, and then move the component with the new pivot point, however once i finish that move command, the pivot point will default back to where it was previously.

[jeff_strater]

There is no such thing in Fusion as a persistent/editable pivot point for Move operations.  The pivot for Move depends on a few things:  The tool used (free move vs translate vs rotate) in the Move command, and the selection method.  For instance, if you select a component in the graphics area, using the Free Move mode, the pivot point and coordinate system are based on pick location.  However, if you pick the component in the browser, different logic is used (I cannot remember if it is center of gravity or component origin, but I think it is one of the two).  The Set Pivot function is only in place for the duration of the command - that new pivot is not stored with the component at all.

[davebYYPCU]

Components are created with an Origin.

File and Component Origins are initially located at 0,0,0, in 3d space.

Component Origins are capable of being relocated, File Origin is fixed.

Joints, and the Move Tool use a pivot point.

Joints and the Align Tool, use snap points.

Move and Align Tools should be a very low priority over using Joints, in relation to Components.

More explanation of your problem, may prompt answer addressing the problem.

Might help…..