Hi!
While building binaries, I did some testing on the new release with some of
my
bigger scenes. I find that the new oconv from 3.5 takes really much memory,
in
fact, more than I have installed in my poor old k6-2 (96MB). So I cannot
build
an octree from a scene that was fine with 3.4.1.
Is this only a result of changes in the -n and -r defaults? Or ist the new
oconv
more memory-hungry then older releases in general? I hope to get my scene
built with the new 3.5 soon on x86, as I will be able to tar a binary
distribution
than.
CU, Lars.
···
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte l�cheln! Fotogalerie online mit GMX ohne eigene Homepage!
Hi Lars,
Try running with the old -r 16384 -n 5 and see if that makes the difference. I can't think what else is new, except the maximum set size was increased.
-Greg
···
Begin forwarded message:
From: Lars Grobe <[email protected]>
Date: Sun Mar 23, 2003 3:22:30 PM US/Pacific
To: [email protected]
Subject: [Radiance-general] radiance 3.5: oconv and memory
Reply-To: [email protected]
Hi!
While building binaries, I did some testing on the new release with some of
my
bigger scenes. I find that the new oconv from 3.5 takes really much memory,
in
fact, more than I have installed in my poor old k6-2 (96MB). So I cannot
build
an octree from a scene that was fine with 3.4.1.
Is this only a result of changes in the -n and -r defaults? Or ist the new
oconv
more memory-hungry then older releases in general? I hope to get my scene
built with the new 3.5 soon on x86, as I will be able to tar a binary
distribution
than.
CU, Lars.
--
+++ GMX - Mail, Messaging & more http://www.gmx.net +++
Bitte l�cheln! Fotogalerie online mit GMX ohne eigene Homepage!
_______________________________________________
Radiance-general mailing list
[email protected]
http://www.radiance-online.org/mailman/listinfo/radiance-general