Hi!

I hope someone can tell me, why my picture needs maaaaany hours rendering a
wall!? The wall is created with the mur.inc macro from Steven Pigeon. You
can find it here: http://home.pacbell.net/tylereng/index.html

I use the standard textures from the example file (nothing too special I
think, some dents as I see it).

The macro creates the wall by placing brick by brick. Every brick is a
superellipsoid.

The wall takes hours, even at 512*384 pixel without anything like radiosity
or photons or focal blur on a athlon 1800+! Is it the superellipsoids which
slow the system so much down?

I guess, the time can't be reduced, but I would like to understand, WHY it
takes so long?!

Regards,

frozen

Post a reply to this message

Hi!

I think it are the superellipsoids which slow down the process. You may try
to use rounded boxes instead, altough you need to edit the macro for that.

JWV

"frozen" <fro### [at] thefrozenno-ipcom> wrote in message
news:web.414eda6f5c5e51dd102354040@news.povray.org...
> Hi!
>
> I hope someone can tell me, why my picture needs maaaaany hours rendering
a
> wall!? The wall is created with the mur.inc macro from Steven Pigeon. You
> can find it here: http://home.pacbell.net/tylereng/index.html
>
> I use the standard textures from the example file (nothing too special I
> think, some dents as I see it).
>
> The macro creates the wall by placing brick by brick. Every brick is a
> superellipsoid.
>
> The wall takes hours, even at 512*384 pixel without anything like
radiosity
> or photons or focal blur on a athlon 1800+! Is it the superellipsoids
which
> slow the system so much down?
>
> I guess, the time can't be reduced, but I would like to understand, WHY it
> takes so long?!
>
> Regards,
>
> frozen
>
>

Post a reply to this message

>
> The wall takes hours, even at 512*384 pixel without anything like
radiosity
> or photons or focal blur on a athlon 1800+! Is it the superellipsoids
which
> slow the system so much down?
>
It's been a while since I played with that one, but I seem to remember that
the wall itself didn't take that long after I remmed out the grass and
trees.  There is a lot of detail in both of them, and the more detail, the
longer the computer has to think before it can plot.  The more detailed the
scene, the longer it's going to take.

Greybeard

Post a reply to this message

Thanks!

Since the scene takes very long even without everything except the walls, I
should try the rounded boxes. If I ever need a wall again.. ;-) Right now
it renders and since it renders for hours now, I will not stop it! ;-)

But can anyone explain, WHY the rendering of superellipsoids takes so long?

Thanks again,

frozen

Post a reply to this message

> But can anyone explain, WHY the rendering of superellipsoids takes so
long?

Well I cant help you there but...  You might have a look at the macro and
try substituting a Mesh for each SE.  Create one mesh and scale  it etc in
the same way the SE's are scaled.  Might be quicker.

Post a reply to this message

"Josh" <som### [at] microsoftcom> wrote:
> > But can anyone explain, WHY the rendering of superellipsoids takes so
> long?
>
> Well I cant help you there but...  You might have a look at the macro and
> try substituting a Mesh for each SE.  Create one mesh and scale  it etc in
> the same way the SE's are scaled.  Might be quicker.

Thanks! I will try this when I need a new wall...

Regards,

frozen

Post a reply to this message

"frozen" <fro### [at] thefrozenno-ipcom> wrote in message
news:web.414eecf4bf1ad50e102354040@news.povray.org...
> Thanks!
>
> Since the scene takes very long even without everything except the walls,
I
> should try the rounded boxes. If I ever need a wall again.. ;-) Right now
> it renders and since it renders for hours now, I will not stop it! ;-)
>
> But can anyone explain, WHY the rendering of superellipsoids takes so
long?
>
Somethings wrong, I removed the grass and trees, 1M, 37S to render.

2.4ghz Celeron, 256M memory, 800 X 600.  Time to render with trees and
grass, 1 Hr 17 M.

Greybeard

Post a reply to this message

"GreyBeard" <r.b### [at] sbcglobalnet> wrote:
> "frozen" <fro### [at] thefrozenno-ipcom> wrote in message
> news:web.414eecf4bf1ad50e102354040@news.povray.org...
> > Thanks!
> >
> > Since the scene takes very long even without everything except the walls,
> I
> > should try the rounded boxes. If I ever need a wall again.. ;-) Right now
> > it renders and since it renders for hours now, I will not stop it! ;-)
> >
> > But can anyone explain, WHY the rendering of superellipsoids takes so
> long?
> >
> Somethings wrong, I removed the grass and trees, 1M, 37S to render.
>
> 2.4ghz Celeron, 256M memory, 800 X 600.  Time to render with trees and
> grass, 1 Hr 17 M.
>
> Greybeard

I suppose, you used the same example scene, which uses mur.inc? With the
same lightsource, the same sky and the changed walls?

I can't understand, how this is possible? Maybe it is because I use windows
2k at the moment?

Thank you very much,

frozen

Post a reply to this message

>
> I suppose, you used the same example scene, which uses mur.inc? With the
> same lightsource, the same sky and the changed walls?

Nothing changed from original.
>
> I can't understand, how this is possible? Maybe it is because I use
windows
> 2k at the moment?
>
Haven't tried it on my 2K machine, I ran it under 98SE.  TImes I got are
about the same on my XP Home edition machine, but that's a 2gig, should run
slightly slower.  I think times were similar under SuSe 9.1 Linux, but
haven't played with that one for a while.  (The Win2K machine is dual boot,
20 gig allotted to Win, 100 gig given to Linux.  2.6ghz Pentium 4c with 1gig
memory.  Yeah, it's fast.)

Greybeard

Post a reply to this message

Hey Greybeard,

thank you very much for your efforts on testing it! I don't have any idea,
what might cause these very slow renderings. I guess, I will have to do
some more tests, when the picture it's rendering now is done.. This will
still take a while.. 1d2h working, 43% reached... :-(

Regards,

frozen

Post a reply to this message