: On a 'classical' 800x600 image, there is only 480 000 pixels.
: With 100 000 cylinders, that give about 4.8 pixels per cylinders.
: I do not even bother to render, it cannot be interesting (no details).

  You forget that cylinders can be semi-transparent and show other cylinders
behind them.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

> On a 'classical' 800x600 image, there is only 480 000 pixels.
> With 100 000 cylinders, that give about 4.8 pixels per cylinders.
> I do not even bother to render, it cannot be interesting (no details).

You forgot animations, where the scaffolding could be a part of the story.

Post a reply to this message

In article <3bf09650@news.povray.org>, "Greg M. Johnson" <"gregj;-
)56590\""@aol.c;-)om> says...

> I once tried to make scaffolding for a WTC-sized tower out of cylinders,
> easily more than 20,000 of them.  The result was essentially an
> unworkable file, as it only rendered slowly and with much disk-swapping
> on my 384MB RAM, 1GHz Athlon.

Only 20k cylinders fill up 386MB?
Last year I made a christmas-tree, with IIRC a bit below 50k cylinders. 
It rendered fine with MegaPov .6 and needed almost exactly 256 MB RAM.

Perhaps you had a complex texture assigned to each individual object?

Lutz-Peter

Post a reply to this message

On Tue, 13 Nov 2001 19:31:22 +0100, Lutz-Peter Hooge <lpv### [at] gmxde> wrote:
> Only 20k cylinders fill up 386MB?
> Last year I made a christmas-tree, with IIRC a bit below 50k cylinders. 
> It rendered fine with MegaPov .6 and needed almost exactly 256 MB RAM.

I just rendered this scene

 #declare Test=union{
  #local C=0;
  #while(C<40000)
    cylinder{0,1,2}
    #if(mod(C,100)=0)#debug concat(str(C,0,0),"\n")#end
    #local C=C+1;
  #end
  pigment{color rgb 1}
 }

and it returns "Peak memory used:         18142448 bytes"
but of course it not play with light buffer and other things

ABX
--
#declare _=function(a,b,x){((a^2)+(b^2))^.5-x}#default {pigment{color rgb 1}}
union{plane{y,-3}plane{-x,-3}finish{reflection 1 ambient 0}}isosurface{ //ABX
function{_(x-2,y,1)|_((x+y)*.7,z,.1)|_((x+y+2)*.7,z,.1)|_(x/2+y*.8+1.5,z,.1)}
contained_by{box{<0,-3,-.1>,<3,0,.1>}}translate z*15finish{ambient 1}}//POV35

Post a reply to this message

news: 3bf09650@news.povray.org...
> Have you ever been afraid to try something for fear you're only going to
> lock up your system or exceed the abilities of the software?

For this picture,
http://www.oyonale.com/ldc/english/chasm.htm

I was happily working on it until the computer started complaining due to
the combination of high-quality radiosity, isosurfaces, large image maps and
very large models. So I bought 512 Mb of RAM to be able to complete it
(remember that Norbert Kern bought a new computer to finish his IRTC winner
"Insects" picture).
Of course now that I'm used to 640Mb some projects can't get done at all so
I won't even start them (rad + iso + ior + focal blur + etc.).

G.





--

**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message

In article <16q2vts7h3eudo20jt542k3f2qmom1ns7u@4ax.com>, abx### [at] babilonorg 
says...

> and it returns "Peak memory used:         18142448 bytes"
> but of course it not play with light buffer and other things

I don't know exactly what parts of the scene needed the memory, but I 
know it swapped heavily with 128MB. Probably the lightbuffers ate a lot 
of RAM, there were lots of lightsources.

Lutz-Peter

Post a reply to this message

As always, if you have a group of cylinders which repeats itself a lot,
you can model a cylinder with smooth triangles and then make this group as
a mesh containing all those triangles approximating the cylinders. Then
you can copy this mesh exactly as you had copied the original group of
cylinders.
  The bigger the group and the more you can copy it, the more you'll save
memory. The rendering speed should increase more or less as well.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -

Post a reply to this message

"Gilles Tran" <tra### [at] inapginrafr> wrote in message
news:3bf16e03$1@news.povray.org...

> I was happily working on it until the computer started complaining due to
> the combination of high-quality radiosity, isosurfaces, large image maps
and
> very large models. So I bought 512 Mb of RAM to be able to complete it
> (remember that Norbert Kern bought a new computer to finish his IRTC
winner
> "Insects" picture).

I fear I'm reaching that point with my current picture Radiosity+media
+complexCSG+100'sMB of image_maps...
so I bought a new computer!!!

Mick

Post a reply to this message

On Mon, 19 Nov 2001 17:06:32 -0000, "Mick Hazelgrove"
<mic### [at] mhazelgrovefsnetcouk> wrote:
>> very large models. So I bought 512 Mb of RAM to be able to complete it
>> (remember that Norbert Kern bought a new computer to finish his IRTC
>winner
>> "Insects" picture).
>
>I fear I'm reaching that point with my current picture Radiosity+media
>+complexCSG+100'sMB of image_maps...
>so I bought a new computer!!!

So what did you buy?? And when are you switching to 64-bit addressing
to break the 2 GB limit ?? Hmm, I wonder how POV-Ray compiles to
64-bit, I may be able to get access to our new hot development box on
the unix side (Compaq Tru64 with 6 GB). I better try my hands on a
unix-like compile on my barely scratched Mandrake setup first.

/Erkki

Post a reply to this message

"Gilles Tran" <tra### [at] inapginrafr> wrote in message
news:3bf16e03$1@news.povray.org...

de
> news: 3bf09650@news.povray.org...
> > Have you ever been afraid to try something for fear you're only going to
> > lock up your system or exceed the abilities of the software?
>
> For this picture,
> http://www.oyonale.com/ldc/english/chasm.htm
>
> I was happily working on it until the computer started complaining due to
> the combination of high-quality radiosity, isosurfaces, large image maps
and
> very large models. So I bought 512 Mb of RAM to be able to complete it
> (remember that Norbert Kern bought a new computer to finish his IRTC
winner
> "Insects" picture).
> Of course now that I'm used to 640Mb some projects can't get done at all
so
> I won't even start them (rad + iso + ior + focal blur + etc.).
>
> G.
I am running into the same brick wall.... I had a really nice entry for
October 2001 (Warfare) but my machine (800MHz Duron, 256MB DDR) choked hard
on it.  I increased it to 512 and it still won't go.  I used some of the
same ingredients (radiosity, isosurfaces with max trace=11+, ior, fog) and
the additional burden of huge parametric meshes (about 25 MB worth).  I'm
currently experimenting with creating immense terrain images with POV and a
custom INI for use with height fields.  I really like the results so far
(it's a bit of a memory hog but not egregiously so).  I might even get an
entry in this time.
>
>
>
>
>
> --
>
> **********************
> http://www.oyonale.com
> **********************
> - Graphic experiments
> - POV-Ray and Poser computer images
> - Posters
>
>
>
>

Post a reply to this message