> ensight, theres no loop constructs, its all straight mesh data. Granted its
> indexed face sets (mesh2 objects), so I'm not sure how that will get
> represented internally, but since the file is ascii and its internal
> representation will be binary, I assumed the memory image would be smaller
> than the file size.

	Ok, for mesh2{} it is indeed reasonable to guess that the object will
take less space in memory than its plain ascii description (particularly if
vertice coordinates are written with a sufficient precision) *unless* the
mesh carries individual texture(s) for each of its triangles.
	Is it the case in your file?

	- NC

Post a reply to this message