brompton | 3D 2D 3D

today i placed my brompton bike in its folded position into a living room. with my DSLR camera i shot 130 photos from different angles. see the image above.

i then loaded the images into autodesk reCap Photo, a program for creating 3D objects from ordinary photographs. the last experiment with a telephone went well, so i wanted to try the same process with a much more complex object.

the result was sort of a shock: instead on concentrating on the folded bike, recap had measured the whole room:

autodesk recap interpretation of 130 photos

the scene looks so real because the textures were stitched in high resolution. the photo below is no photo, it’s a 3D computer scene. the black elements are parts of the wall, seen from the outside.

[all images on this page are (c) copyrighted!]

i exported the 3D scene and loaded it into autodesk maya. it arrives with yet another surprise: we see lots of camera icons, 130 in total!

here’s a closer look at the brompton. the whole scene consists of about 5 million polygons:

once the scene is in a 3D app such as maya you are free to move around. here is a view from the top:

back in recap photo you can pre-render the scene as xray:

or in a wireframe mode; it looks almost like a pencil sketch:

using arnold as the default maya render engine, you can get results like these:

and with the scene reduced to the geometry of the bike, you can build your own environments, for example by introducing a smooth light and a reflective surface for the bike:

here you see the problems: the spokes on the rear wheel are missing, the spokes on the front wheel are visible, but they are pieces of texture, not real geometry.

from a distance like in the image above, the bike looks convincing. not so with a very close look:

computer animation, especially for gaming, is about mesh reduction. that means you don’t want so many polygons. in the screenshot below you see three bikes which look almost the same. but the left one consists of 700,000 polygons, the middle one of 140,000 and the right one of 9,000 polygon “faces”.

the wireframe visualisation tells the technical truth:

and when you remove the complex texture from the 3D structure, the poly count becomes even more obvious. in other words: you don’t need that much geometry when you have excellent textures.

if you want to get serious about modeling and animating a bicycle in 3D, the 3D scan is a good starting point. and even if you use the geometry only as a reference for modeling, you might actually appreciate the rich texture which comes with the scanning process.

i stick to the bike as it is for now. but i’ll give it a face lift ;-)