The main reason for parenting the aircraft and camera to the null, is that you want to establish the visual relationship between them. The altitude of the camera and aircraft above the ground plane can be adjusted by changing the null object's "Y" axis value. In the shot we're traveling at mach two, which is approximately 680 meters per second, so you just divide 680 meters by 24 frames to get the value you need for frame 24. To increase or decrease the speed at which everything is traveling, I only need to adjust the keyframe value on frame 24. Usually I prefer to make a keyframe on frame zero and another at frame 24, based on the scene's frames per second, and then set the keyframe's pre-behavior and post-behavior settings to "linear" in the graph editor. It had two keyframes which determined the speed at which everything traveled in the shot. Using a low res model doesn't slow your computer system down, and at this point in the project you want to be able to make changes quickly.Ī null object was used as a parent object for the three aircraft and the camera. Terragen and Lighwave "units" are both based on meters, so if you use real world scales the two software packages work seamlessly together. The important thing here was that the model was built in real world scale. So here are some of the step by step things I went through in Lightwave.Īt the beginning, we were undecided about the type of aircraft to be used, so I modeled a proxy aircraft based on a SU27 fighter. As with any shot, in retrospect I would do it completely different if I had to do over, but that just goes to show you never stop learning. That's because it's easy to add additional cameras, apply motion modifiers like Noisy Channel, or load from scene, etc. I've been using Lightwave since the mid 1990's, so it has become second nature for me to use it to setup and previs a shot. Thanks for your interest in the "Terragen for VFX" series and comments, and I'm happy to answer any questions here about how we used Lightwave in this production. I think Kevin Kipper is making the tutorials. Especially new users use unneeded high settings.Īnyway curious about the next tutorials too. Regarding clouds they could have rendered separately at a little lower resolution and comped later etc.Īnd mostly you don't need always the highest settings of the node-render settings. Using an obj does have some other caveats of course.Īn exported heighfield-displacement map could have been better maybe. So should be rendering relatively fast.įor my last animation i exported the terrain as an OBJ and render time got faster. I am curious too for the next videos.īut from my own scenes what i have seen is until you go to a certain threshold clouds takes longer to render (that depends actually too on the settings).īut if you have a very displaced terrain with many nodes that can take a long time to render too (with compute nodes etc).īut this terrain doesn't look like that kind of terrain.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |