Bricks in Motion
We are a friendly filmmaking community devoted to the art of stop-motion animation using LEGO® and similar construction toys. Here, you can share your work, join our community of other brickfilmers, and participate in periodic animation contests!
A place to discuss, share, and create stop motion films.
Ad
You are not logged in. Please login or register.
Droids vs Clones
I got slightly fed up with spending months and months on single story projects with little advancement. So I set myself a goal, create, animate, and render a video in one day. Six days later I present to you this video!
The basic premise was: LASERS!
Wow, I totally didn't see this. Sorry about that.
I think it looks a bit rushed, and some of the animation looks too slow, much slower than it should be. I know that you didn't really have a lot of time to make this video though, and for six hours you did a lot more than I though possible. I can really appreciate how much time it took to render all of that. Out of curiosity, about how long did it take to render?
Edit: wow, I totally didn't pay attention to the time. Six days isn't bad though.
Last edited by BGanimations (October 17, 2010 (05:53pm))
I think it looks a bit rushed, and some of the animation looks too slow, much slower than it should be. I know that you didn't really have a lot of time to make this video though, and for six hours you did a lot more than I though possible.
I think you might have been a bit rushed in your reading. 
Though I wish this had been done in 6 hours, it was actually 6 days. I really don't think a project of this type, on the first try, could have possibly been created in 6 hours. Pre-production, modeling, animating, lighting, and rendering... just not even concevable that this could have been done in 6 hours, or even 1 day as was my original plan. 
I can really appreciate how much time it took to render all of that. Out of curiosity, about how long did it take to render?
I started out doing very detailed rendering, or at least more detailed then I ended up using. And that took time. Originally it was about 5 minutes per frame, which would have been fine, except I would render 50 or so frames over a night, wake up in the morning and see massive mistakes. I started getting into the "feedback" cycle which results when you have long render times. So about half way through I stopped rendering at a higher detail and got the render times down to about 1:30 for each frame. So in the end, rendering wasn't as big of a problem as actually trying to work in the scenes I had created. The last "flyover" scene had over 7 million vertexes in parts...
Not much to say. But if we must, we can get into the details. Obviously, a plot is lacking, but we don't care about that for this vid. We saw more of the droids walking than the clones. The droid movements (at least for the B1 Battle droids) are obviously duplicated from one walk sequence and re-timed so there's no dynamic movement in them. Same goes with the B2 Super Battle droids. Not much to say about the clones other than they look like they're wobbling their way into the frontlines.
But the scenery, the improvements to the physically stiff-leg-and-arm plastic Battle droids is to be commended...if only we could get a closer look at them.
I find brick-ified terrain unnecessary. Too many vertices to handle. I mean, it's understandable to have studs for them to walk on, but in the background, they're redundant. If you have a render farm in your arsenal, then it's trivial and you can handle it, but if you only got one computer burning its CPUs to handle a thousand background cylinders and cubes one can barely see, you might want to consider some compromises.
Posts [ 5 ]
