Models for gaming should aim to represent the figure with as few polygons as possible and still have enough details to look convincing. Using low-polygon models helps games to run fast and smoothly, although as hardware improves, games are able to increase the number of polygons per object. Certain models will require more polygons than others, depending on how important they are to the game. For instance, a rock on the side of the road may use less than 50 polygons, whereas a small building may use more than 500. The use of texture maps greatly enhances the model to this effect because they add a lot of detail without extra geometry.
Simple geometric objects, like my Rubik's cube, may end up with far more polygons than is needed to represent them, since most of the feature points will probably result in vertices even if they lie on the same flat surface. Once the shaped has been determined, I should find a way to consolidate the polygons. For texture mapping, I will also need to combine all the input images into one or two texture maps.
Here are some of the papers I referenced in my proposal for transforming a point cloud to a mesh along with references Serge recommended:
- H. Edelsbrunner and E. P. Mucke. “Three-dimensional alpha shapes.” ACM Trans. Graphics 13, 1994, 43-72
- J.-D. Boissonnat. “Geometric structures for three-dimensional shape representation.” ACM Trans. Graphics, 1984, 3(4):266-286.
- Amenta, N.,
- Facade - architectural models
- Canoma - fast photorealistic models
- Google Sketchup - 3D models for Google Earth
- David G. Lowe, "Distinctive image features from scale-invariant keypoints," International Journal of Computer Vision, 60, 2 (2004), pp. 91-110.
No comments:
Post a Comment