 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I have just rendered the scene I'm working on in both POV 3.1g and
3.5beta4, and noticed a significant difference in peak memory use. While
3.1 uses 167MB 3.5 uses 339MB - more than twice as much. Is this normal,
or have I overlooked some change in the default settings, that can
explain the difference?
/Ib
----------------------------
Gallery: http://www.ibras.dk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
IIRC Norbert Kern got a similar problem (have a look to his thread in p.b.i)
--
Jonathan
"Ib Rasmussen" <ib### [at] ibras dk> ha scritto nel messaggio
news:3BB78B4A.5D4E4BB8@ibras.dk...
> I have just rendered the scene I'm working on in both POV 3.1g and
> 3.5beta4, and noticed a significant difference in peak memory use. While
> 3.1 uses 167MB 3.5 uses 339MB - more than twice as much. Is this normal,
> or have I overlooked some change in the default settings, that can
> explain the difference?
>
> /Ib
> ----------------------------
> Gallery: http://www.ibras.dk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
yes, I had strange problems with memory usage in 3.5.
The problem was texturing of maketrees which consist of many cones and
spheres (and a mesh for the leaf).
Each cone and sphere was initially defined with the same texture.
In megapov 0.7 my tree needed 21 MB, but in 3.5 >100 MB.
After making a union and texturing the tree as whole entity, memory behavior
was normal and my scene with 8 trees needs now 600 MB less, which is ok. :-)
> IIRC Norbert Kern got a similar problem (have a look to his thread in
p.b.i)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3bb9ee6a@news.povray.org> , "Norbert Kern"
<nor### [at] t-onlinede> wrote:
> yes, I had strange problems with memory usage in 3.5.
>
> The problem was texturing of maketrees which consist of many cones and
> spheres (and a mesh for the leaf).
> Each cone and sphere was initially defined with the same texture.
> In megapov 0.7 my tree needed 21 MB, but in 3.5 >100 MB.
> After making a union and texturing the tree as whole entity, memory behavior
> was normal and my scene with 8 trees needs now 600 MB less, which is ok. :-)
I am not sure if this is possible to detect at all, but do you know how it
behaves in 3.1g in similar cases? Who knows, maybe some code that reduces
memory usage got broken in 3.5 beta. It can't hurt to post in the
p.beta-test and ask for someone to confirm it.
Thorsten
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
