It is easier** to drive animations from outside of Pro/E-Creo. I've used VBA from Excel to generate trail/training files. It can use Part mode, or any other mode that allows screen image capture, to generate frames. The downfall is that it is open loop, so if Pro/E-Creo whatever can't regen, the trail file dies and the process stops. Using ProE this way allows features to be incrementally created - like an edge with a radius can move from .00001 to .25 to animate the change.
Today I'd go with AutoIT as it can be set to respond interactively to software failures, and can screen cap anything even if the app doesn't support it, and can drive other applications in concert.
Possibly the best combination is to drive part/assembly creation within Pro/E Creo; export to another format; render elsewhere, such as POV Ray or Blender, where it is much easier and very reliable to handle perspective, material appearances, and accurate light effects (caustics, radiosity, HDR) and there is significant experience and tools dedicated to rendering and animation.
**Other methods are more work for simple animations, but the Pro/E ceiling is very low and cumbersome to get any more than rudimentary results. Blender, for example, can motion track your model to captured video, matching perspective. POV Ray does a terrific job for texture animation and caustics. Both of them handle cameras in an easy, understandable manner.
youtube dot com/watch?v=104ou2vG3SM "Blender 3d Scene Camera Tracking / Matching" by" Play -Fair-Play"
www dot youtube dot com/watch?v=D2c7GFVbdSw "03. Camera Tracking Blender 2.5 - Dragón Marino [Making Of]" by ChincheArt