Hey. My two cents worth:

1. Wouldn't a big pale moon fit the sky nicely in this mountain flight? Hannu mentioned moonlight already in the previous comment.

2. The break in the music could be used to introduce the entrance to the cave. Perhaps slowing down and then accelerating instantly when entering the cave.

3. The bats could come into the picture as Hannu proposed, when the camera enters the cave. The camera could follow the bats through the cave. The cave could have either lanterns or torches on its walls and the fly through could be made in synch with the rhytm of the music?

4. Some new element could be introduced with the song again developing in the background (whether or not with the singing/lyrics). I was thinking some "strobing" stuff could be used to produce some excitement?

Ah yes. A cave. The idea really seems to be stuck in my head as like Kalle said, the presentation's scene had cave in it, and also, the first emails about trailer had an idea of cave full of bats in them.

I've actually been thinking about how to animate the bats flying close to camera and that is probably the main reason what makes me think about caves. :)

I was thinking, would it work if the beginning of the trailer is flying over the mountains without any bats and they start flying only after entering the cave? The transition to a closer view to the mountains & castle would be easy to create with bright moonlight shining from outside into the cave, thus blinding the camera for a moment.

This works even better than the video preview on the renderfarm.fi page! O.O

Cave? :)

This combination of WAM and Renderfarm.fi is a really, really excellent concept. :D

Getting inspired here and firing up the good old Logic to start shaping that tune. :)

Yeah, there are couple of errors there (like stars floating next to clouds!!!) but nothing that can't be easily fixed with couple of replacement frames & adding stuff in post. By the way that black & disappearing clouds can be fixed with adjusting camera's view distance settings, if someone's having similar issues with their scenes. I always forget to adjust that when animating camera close to a volumetric mesh's surface.

But, thanks for the comment & big thanks for the integration!! I feel this has brought renderfarm.fi into totally another level of usefulness & user-friendliness, and so has happened with WaM too!

Awesome looking stuff Hannu! Unfortunately there seems to be a bug around 2-3 sec. Any idea on what might have caused that?

Anyway a big hand. That session/scene is definitely worthy of being called the first Renderfarm.fi integrated session on WAM. :-)

looking nice, gotta ask if I can use the software on my worklaptop, installing on my homecomp.

99% done, the last threshold of the critical error. Hope not. well done, wam and RF.fi people.

Hehe. I think you really should use CATS, Kalle. http://www.renderfarm.fi/cats

As I just commented on Renderfarm.fi (http://www.renderfarm.fi/animations/559 - we need a link to the Renderfarm.fi node here too, we're the WAM link on our end tomorrow hopefully), this is basically the first ever shot placed on Wreckamovie.com that uses the new integration between the two services.

I think this collaboration will bring a lot good for both services in the future. Anyway more about this officially tomorrow.

Also, I didn't have in mind that we're rendering two awesome and high demanding sessions. This also decreases the time of retrieval, since the clients got fed with workunits on those two previously.

We anyway aim to decrease the time of rendering, and maybe we would be interested to dispatch the workunits to the machines of the team in priority.

Just my thoughts about the progress of a session, so you won't be disappointed nor surprised.

The general curve of progress for a session is more or less like this (especially for heavy sessions):

-start pretty slow, the workunit are distributed on the hosts depending of the demand.

- rendering a frame (or a part) takes a while, there's a timeframe of 2-3 hours before the first results return (except for i7 processors :p). At this point, it can be that many hosts return their results at the same time. A machine with multi-core would return 2-4-6 parts more or less at the same time. All those results help the session to reach a high percentage of progress rapidly.

-Then comes the last parts. The server would creates new workunits for the last part that are taking too much time to return (slow machines). At this point we can reach 99.40% for over a day. But this isn't so important as all the other images are already ready for download (except maybe few of them, like 1 or 2).

In our case, it means that we would have the animation when the encoding of the images start, meaning all the parts have been computed and returned.

Well .... let's see how long this one take now ;)

And ofcourse, everyone who has registered to Renderfarm.fi and use BOINC, don't forget to join the Wreckamovie-team!

Here's a link to team page: http://www.renderfarm.fi/team_display.php?teamid=257

Hehee.. it shouldn't be very heavy scene. There seem to be two other tasks running too, which up the rendering time. Wouldn't mind if more people install BOINC on their system though. *wink*

Kalle Max, the four hours is how long it's already rendered it, time still remaining is unknown. Might be 10 hours, might be 40 hours, we'll see :)

Eek.. maybe I should've tried to do something more spectacular than "just a start". :D Ah well, I'm too exited about this integration to worry about the quality of this particular render.

Nathan: yep, finally :)

I wonder how many wreckers there are just refreshing this shot to see the progress of rendering ;)

Yeah seems like its going to happen. And work even .

Ooh! integration!