AC3D Forums - View Single Post

lisa · 21st May 2007, 07:49 PM

Correct.

The physical size of the model shouldn't effect the memory usage, but the poly count will.

However, exceptionally large and exceptionally small models are sometimes difficult to work with for other reasons. If your model is too large, your graphics hardware may not have enough z-buffer precision, and you'll experience z-fighting\flimmering. This is not an AC3D-specific issue; it's just the nature of 3D hardware. Small objects can make the camera difficult to work with.

A common trick most game and movie studios use is to break very large models up into multiple pieces, and then only assemble them or use a low-lod (reduced level-of-detail) or "imposter" model when the entire object must be in the shot. This also allows different artists to work on different parts of the model at the same time.

21st May 2007, 07:49 PM	#6
lisa Senior Member Professional user Join Date: Mar 2005 Location: Phoenix, AZ Posts: 917	Re: large size? Correct. The physical size of the model shouldn't effect the memory usage, but the poly count will. However, exceptionally large and exceptionally small models are sometimes difficult to work with for other reasons. If your model is too large, your graphics hardware may not have enough z-buffer precision, and you'll experience z-fighting\flimmering. This is not an AC3D-specific issue; it's just the nature of 3D hardware. Small objects can make the camera difficult to work with. A common trick most game and movie studios use is to break very large models up into multiple pieces, and then only assemble them or use a low-lod (reduced level-of-detail) or "imposter" model when the entire object must be in the shot. This also allows different artists to work on different parts of the model at the same time.