Photoreal animation straight from SU

vkirchner

Thank you for the quick response. I can simplify the path to a straight line if the motion can keep a constant speed from the starting point to the end point. No part of the car is used in the rendering, only a camera following a path through the village. Can the "SU Animate" do this?

The final render animation need not be photorealistic, but it cannot be cartoonish like the standard Sketchup windows either. To save time and energy, I planned to use many models from the 3D Warehouse with slight modifications to complete the task in a reasonable timeframe. I have tried to take many Sketchup models into Rhino4.0 with mixed results. Normally the textures are skewed, distorted, or omitted. I have tried Softimage also but the textures are always an issue. I suspect that C4D will also be this way, do you have any experience with the texture issue?

I have acess to the following packages and renderers.

Rhino3.0 with Flamingo, Penguin, Treefrog, and Rhinorender
Rhino4.0 with Rhinorender
Softimage with Mental Ray, and Indigo
Carrara 5.0 Pro
Bryce 6.0
Light3D from Optis (http://www.optis-world.com)http://www.optis-world.com/new_pages/archi_lighting/lighting.asp

Regards
Vince

vkirchner

Thank you, I will look at the suggested scripts.

Regards
Vince

kwistenbiebel

If no object animation will be used, yes, Suanimate or flightpath2 are helpful to get smoother animation paths.

Suanimate:http://www.ohyeahcad.com/suanimate/

flightpath2.rb on the smustard website:
http://www.smustard.com/script/FlightPath2

They both are commercial plugins .
I wish they had demos to try them out before buying.
(some youtube clips to accurately show how the flightpath2.rb works would help)

plot-paris

just bought flightpath2 two days ago (7$ is not that much). you have more advanced control over the camera focus compared to the (free) first version of flightpath. you can for example choose on path for the camera motion and another one for the camera aim. you can get quite sleak results. only important thing is to check that your path is smooth enough (has enough vertexes).

I would suggest you try flighpath for free. with this version the camera will always point straigt in the direction of the path.

if you need more control, go for flightpath2

vkirchner

Thanks, I did not realize that the older script was free. It sounds like it will do everything that I need, so as soon as I can get the models inserted, then I can smooth a spline and give it a try.

Thanks
Vince

vkirchner

I cannot tell if the free script will hide the path curve, that would ruin a nice driving animation if the path curve is visible. That would make the $7.00 cost to obtain the newest script mandatory.

plot-paris

as far as I know, it does put the path on a layer, which is hidden.

if it doesn't, you can do that manually. or you could even delete the path for it is not necessary anymore once the scenes are created (not advisable though, in case you want to redo the animation-generation)

something that can really help you in terms of flexibility is to select all scenes (with Shift) of your animation and then uncheck all checkboxes in the scene editor except for camera position. thus you can change things like styles or shadow settings lateron. you could even create scene tabs for different styles (with the "include in animation" box unchecked)...

vkirchner

Wow, that really sounds like a powerful option. Then I could create pencil drawn style, and possibly a Sin City style.

Julius

@plot-paris said:

just bought flightpath2 two days ago (7$ is not that much). you have more advanced control over the camera focus compared to the (free) first version of flightpath. you can for example choose on path for the camera motion and another one for the camera aim. you can get quite sleak results. only important thing is to check that your path is smooth enough (has enough vertexes).

I would suggest you try flighpath for free. with this version the camera will always point straigt in the direction of the path.

if you need more control, go for flightpath2

there's also a free script called flightpathtool (you can find it at http://www.crai.archi.fr/RubyLibraryDepot/Ruby/em_cam_page.htm)

features of the three scripts:

flightpath:

Target: Camera Path Nodes creates pages with the camera looking toward the next vertex of the camera path

flightpathtool:

Target: Camera Path Nodes creates pages with the camera looking toward the next vertex of the camera path
NEW! Target: Single Point asks you for a single point that is the focus for the camera as it moves along the path
NEW! Target: Two Points asks for two points. As the camera moves along the path, the target point moves between the two selected points
flightpath2:
Target: Camera Path Nodes creates pages with the camera looking toward the next vertex of the camera path
NEW! Target: Single Point asks you for a single point that is the focus for the camera as it moves along the path
NEW! Target: Two Points asks for two points. As the camera moves along the path, the target point moves between the two selected points
NEW! Target: Path allows you to select a target path. <---so basically you pay the 7$ only for this.

plot-paris

@julius said:

NEW! Target: Path allows you to select a target path.[/u] <---so basically you pay the 7$ only for this.

you are right. but unfortunately this is exactly what I need.

honestly. a camera-aim path gives you a great deal of control over the sequence. only difficulty is to properly synchronise the two paths to achieve the desired change of focus at the right time.

after a lot of trial and error I found out, that you best create two cubic bezier curves (fredo6's bezier tool plugin) with exactly the same number of control points. thus you can exactly see which point of the camera-aim path is connected to a certain point on the camera path...

flightpath2 askes you for a speed (like 14 m per second). a scene is created at every vertex of the camera path and the transition times are set individually to retain the desired speed.

however, I find it more useful, if all the scene transition times are the same - thus the number of vertexes on the path defines the speed (many vertexes, slow speed; few vertexes, high speed). unfortunately you need another script for resetting all the transition times back to default. you can get this script along with flightpath2 with the "presentation bundle2" for 16$

it is a bit unnecessary, if you are comfortable enough with the free versions. but you definitely have total control over your animation.