This is a VERY rough animatic test of a test video shot as a time-lapse and high visibility. It's midnight here and I mislabeled the video as high-speed photography. It's really the reverse of that; timelapse photography. The visibility present here is 500m from the origin point, which is 1000m in circumference.
A few things I noticed: First, despite taking 35 minutes to film, I STILL had the camera objects move too fast. I need to slow them down by half in order to get good, smooth motion. Right now this looks a little too much like stop motion.
In order to get a sharper picture, I would have to cut out each frame and reassemble it on a new timeline cut instead of just speeding up the raw video.
Particles also do not render continuously at such slow frames per second. The average FPS for this video was about 1 frame per 8 seconds.
A few trees are popping in. This isn't a rendering error, but they pop in because those trees have visibility radii on them. I should enable fade-in models the next time I try this, but I doubt it will have any effect.
I'm also experimenting with multiple camera objects and seamless transitioning between them so that I can do that complex flyover move of the town square. But it turns out that I miscalculated on two of the camera rotations. They appear as jump cuts here in this movie, but it is supposed to be a fluid motion. The normal-speed test worked out but I must have messed up on the division to translate the RPMs over to the correct speed. Seems I got them a bit too slow.
Excellent video, I also liked the choice of music.
flashcode0 5 months ago