Thanks for your answer.
But this tag is necessary to obtain a correct render, right? (I've not read the renderman specification about subdivision meshes yet, but when I render without this tag, there is a wrong shading where the boundary edges are).
At least this also explains why the render is so slow when it reaches the boundary edges.
Regards,
Stéphane
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just ran into this as well,
I have 6gb of ram and quickly max it out as well as my swap partition,
with this file here http://slow67.googlepages.com/outtest.rib.tar.gz
changing/removing tags do not seem to help the problem. Both 3delight and aqsis render this mesh with relatively low memory footprints
this is with pixie-2.2.4
my operating system is 64bit ubuntu.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just ran into this as well,
I have 6gb of ram and quickly max it out as well as my swap partition,
with this file here http://slow67.googlepages.com/outtest.rib.tar.gz
changing/removing tags do not seem to help the problem. Both 3delight and aqsis render this mesh with relatively low memory footprints
this is with pixie-2.2.4
my operating system is 64bit ubuntu.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
When rendering the following RIB:
http://stephane.soppera.googlepages.com/too_much_mem.zip
with pixie 2.2.4 under windows XP, the rndr.exe process take more than 900MB of memory.
3Delight only takes ~30MB and Aqsis ~48MB.
Why is Pixie taking so much memory for this very simple scene? Have I done something wrong?
Thanks in advance for your help,
Stéphane
Hi,
The "interpolateboundary" tag seems to cause the problem. Removing it on WIN32 seems to make it works (27MB consumption).
On Linux, it works well with the "interpolateboundary" tag, Strange...
Cheers.
Hi,
Thanks for your answer.
But this tag is necessary to obtain a correct render, right? (I've not read the renderman specification about subdivision meshes yet, but when I render without this tag, there is a wrong shading where the boundary edges are).
At least this also explains why the render is so slow when it reaches the boundary edges.
Regards,
Stéphane
I just ran into this as well,
I have 6gb of ram and quickly max it out as well as my swap partition,
with this file here http://slow67.googlepages.com/outtest.rib.tar.gz
changing/removing tags do not seem to help the problem. Both 3delight and aqsis render this mesh with relatively low memory footprints
this is with pixie-2.2.4
my operating system is 64bit ubuntu.
I just ran into this as well,
I have 6gb of ram and quickly max it out as well as my swap partition,
with this file here http://slow67.googlepages.com/outtest.rib.tar.gz
changing/removing tags do not seem to help the problem. Both 3delight and aqsis render this mesh with relatively low memory footprints
this is with pixie-2.2.4
my operating system is 64bit ubuntu.
I'm experiencing the same problem with both pixie-2.2.4 and the latest svn on ubuntu linux, x86_64.
I tried removing the "interpolateboundary" directive but still get extreme memory consumption (~2GB).
You can find my scene at http://sites.google.com/site/johnhaiducek/Home/falcon.tar.gz?attredirects=0