Morevna Project

It’s time to tell about the way we organizing usage of the same models in various scenes with blender.

Imagine we have a model of… mmm… bike! And as you could see from storyboard bike is appearing on many scenes of Morevna Project demo. We do not want to include the full copy of a bike because every time we will change the original model, we will need to re-insert it into each scene and (sic!) animate it again.

Consider, what it is unavoidable to make changes in the model after it already inserted in the scenes and process of animation already begun. We can’t design the model from start till the very end - there is always something to fix during the usage. Also it could be handy to insert unfinished yet model to the scene to see how it will look, and let one artist to work on the scene and other continue develop model (like we did for truck model in scene 54).

(more…)

Well, I’m glad to introduce a new website design… Huh?! Someone already noticed? So I’m late. ^_^”

This task was a really challenge for me because… I don’t know, but for some reason it was hard for me.

And, yeah, we migrated to blender 2.46. I know, much time passed by since it come out and 2.47 is already coming, but that reworked particle system (which is really great, by the way) caused much troubles for us. Anyway, it worths so - we really needed the opportunity to properly manage external lib data, especially for Video Sequence Editor which we using to compose all scenes together. Now our project directory tree is completely transferable and we moved towards the improvements in the managing of the rendering process.

(more…)