Community Tip - Have a PTC product question you need answered fast? Chances are someone has asked it before. Learn about the community search. X
For the past month, I have been trying to find out this feature in Creo Parametric.
This feature does not allow parts to intersect and causes other parts in the assembly to move with their constraints. I've attempted to find this feature on Creo Help, PTC Community, and even Youtube.
I have seen this feature in Creo Wildfire. How do you access it in Creo Parametric?
I have a feeling that the feature is hidden in plain sight, or I am not thinking.
Thanks if you know what I'm talking about!
If you mean evaluation for collisions see here:
http://learningexchange.ptc.com/tutorial/2622/evaluating-playback-results-for-collisions
There is a "Drag Components" button in assemblies and again in Mechanism. The "realistically" part of your question is vague. Dragging components can move things into a locked position that cases an error.
Secondly, you can change relation to change a specific component and let the relations drive the rest. It has been done with Trail files.
But ultimately, the best way to demonstrate motion is to apply mechanism with a motor. Now you can easily see what is going on and if you have conflicting contraints, it will not resolve and you have to alter some parameters.
Maybe expand on your question a bit.
I am having a similar situation, what I would like to do is be able to drag a part in an assembly (slider connection) left to right and have an opposite handed part move right to left the same distance have tried a relation but I may not be preforming this correctly or it simply does not like relations between slider connection. I am familiar with dragging components and animations. I'm not looking for a simulation I need to be able to manipulate this connection as if it were real in the real world. simply put drag one part one way have the other part move the opposite way the same distance. I am presently running Creo Parametric 3.0, any help would be greatly appreciated. thank you
Scott A.