Since I started working on this car project, I’ve been getting a lot of positive feedback which really helped me move the project forward. It’s only fair that I return the favor and share a bit of what I learned here. (The full scene file including model, lighting, material and texture is available at my site)

The entire scene is rendered with the built-in renderer.  It gives me more artistic control than a photon-tracer, and is also much faster.  Blender is a capable renderer; learn to use it!

Supposedly, like eyes, car headlights defines the character of a car.  There is really no shortcut to making a sparkly looking headlight, I just modeled everything as geometry and applied a lot of reflection/refraction to the material.  As long as the geometry is there, all the cool effects happen automatically once you hit render.  i also placed a lamp at where the light should be, to throw in a bit of extra lumen.

A lot of the magic happens in compositing.  Here you can see my postprocessing setup.

For the animation, I rendered out the entire video at 1280×720, as PNGs.  Because PNG is only 24bit, extra dynamic range is lost, which made all the post-processing and cross-fading look half-assed.  Next time I’ll definitely render to floating-point EXR formats, which should help when I start applying more aggressive processings.  I also realized that a single computer is NEVER fast enough;  The 40 second clip would have taken 83 days to render on a single core, but with the help of 24 cores spanning across 4 PCs, I managed to push out the video in less than 4 days.  Dropbox made file synchronization embarrassingly simple.

A lot of the technical issues with the video (bad driving dynamics; black pixels; flickering) only cropped up last minute in the final rendering, at which point I am just too annoyed to re-render it.  So hopefully I’ll fix these distractions later and release a better version soon.

That’s it for now.  Hope you like what I have so far.

into something prettier:

The visualization data is coming from EwE6, a well-respected ecosystem modeling software.  Blender uses inputs such as biomass, water turbidity and light level to create a realtime visualization that allows the user to ’swim’ around in the ocean, watch the schools of fish interact, and see their population change over time.

To accomplish all this, the project consists of 3 layers:

The server core does all the heavy computation while the visualization layer does all the graphics, AI, as well as user interaction.  To facilitate the communication across these two separate processes, a third layer (called the GameClient) is created, providing the bridge.

Being a Blender artist, my main focus is on the visualization layer: the Blender Game Engine.  In the following few posts, I will outline the process in creating this application, and describe some of the issues we faced.  Please leave a comment if you are interested, it will motivate me to write more :)

1. Get Blender 2.5 Alpha, also go for the 64bit version if you have 3GB or more of RAM.  2.5 is simply a lot faster and refined than Blender 2.49.  The tools and interface is also much cleaner and more intuitive.  Also, a lot of work has gone into optimizing the sculpting feature in Blender 2.5.

2. Start with a base mesh, then apply the multires modifier.  Do not use a default cube and rely on the multires modifier to do *all* the sub-division.  It’s always better to start with a base mesh with a few thousand polygons, and use multires with a sub-division level of 2-5.

3. Turn off “Double Sided” in the Object Data panel.  This will significantly speed up the redraw.

4. Delete UV texture data and Vertex Color data *might* help speed things up, but I don’t really know for sure.

5. Turn on VBO in the Preference menu.  This will further speed up drawing speed.  (Thanks Gustav!) Okay apparently it doesn’t according to another commenter, since sculpt mode already uses VBO by default.

So without further ado, here is the packed Blender file of the BMW.

The car is modeled and rendered entirely in Blender 2.5.  Render time is around 20 minutes at 3200×2400.

A few of you asked me how I setup the material/lighting/rendering options.  Without releasing the Blender file (yet), here is a screenshot that might help:

From left to right, you can see the world settings, world texture settings, car body material, and finally car body texture.

PS: Happy New Year!

Render Stats for the above screen capture:

~1.6million Faces
~10MB of texture
~3 light sources + 1 HDR EnvMap
~Ray traced reflection, refraction, and Approximate Ambient Occlusion
~500MB RAM use
~Intel Quad @ 3.0Ghz
720p resolution at 1 minute a frame. (5 minute a frame when 5x motion blur is enabled)

Edit:

No crazy DoF effect on this one…  I also found out that approximate ambient occlusion causes some artifact on the car body, mainly in how it treats subtle curved panels.  So I am going back to real AO.

And since a few of you asked about what lighting system I used, here is the setup I am using:

Sorry to disappoint.  Yes the car is lit with just a single Hemi light source.  (Take that David!)  The rest is done with Ambient Occlusion using an HDR image texture.

The reason why it’s such a tight crop (and lit with low key light) is because the rest of car aren’t detailed yet. :D

Edit: first beauty render