|
 |
Wasn't it Warp who wrote:
>TinCanMan <Tin### [at] hotmail com> wrote:
>> 2) Is it worth it to do this conversion (i.e., I have an 8Mb mesh1 object)
>
> The advantage of having a mesh2 is a smaller file size and probably a
>faster parsing. It does not affect render time or memory usage in any way.
>
> (Ok, that's not technically true. When parsing a mesh, POV-Ray uses some
>temporary data structures which take some memory. However, I think that it
>frees these when the parsing of the mesh is done and thus in the rendering
>step there is not extra memory needed.)
It just so happens that the scene I'm currently working on has a fairly
large mesh in it that I can make available in either format. I did a
quick test, and the stats are:-
Format Filesize Parse Render Total Peak
Time Time Time Memory
mesh1 11740 Kb 13s 77s 90s 14.36 Mb
mesh2 4622 Kb 6s 64s 70s 11.36 Mb
In this particular case, the difference in render time is probably
caused by the fact that there has to be a separate mesh1 object each
time there's a change in texture. In this case there were 144 meshes
(there are only 18 textures, but they change back and forth many times).
Manually hacking the meshes to produce a single mesh1 object and a mesh2
object with the same single simple texture the stats are:-
Format Filesize Parse Render Total Peak
Time Time Time Memory
mesh1 12769 Kb 25s 29s 54s 28.94 Mb
mesh2 4745 Kb 6s 27s 33s 11.42 Mb
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
