If you go to the following web page you'll hopefully get my drift.
Im only gettting 13pps on a P90 with POV.win.
I think it's the superellipsoids, but doing an 8x640x320 animation
means-35hrs.
I now appreciate I could cut down on my lights (6 of).

Go here....Please...Please...Please....
http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html

Stu### [at] ozemailcomau

Post a reply to this message

Stuart Johnston wrote:
> 
> If you go to the following web page you'll hopefully get my drift.
> Im only gettting 13pps on a P90 with POV.win.
> I think it's the superellipsoids, but doing an 8x640x320 animation
> means-35hrs.
> I now appreciate I could cut down on my lights (6 of).
> 
> Go here....Please...Please...Please....
> http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html
> 
> Stu### [at] ozemailcomau

Merging superellipsoids on a P90 is your most likely culprit along with the
fact you have transparent objects in the scene which are inherently slower
to render than other objects anyway.

Have you considered overclocking your system to boost performance ?
http://www.tomshardware.com/overclock.html

-- 
Ken Tyler

See my 850+ Povray and 3D Rendering and Raytracing Links at:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Ken wrote:
> 
> Have you considered overclocking your system to boost performance ?
> http://www.tomshardware.com/overclock.html
> 

And get a whole of 15pps? :)
Anyway, the P90 generally isn't very overclockable... I seriously recommend
upgrading.

Margus

Post a reply to this message

Margus Ramst wrote:
> 
> Ken wrote:
> >
> > Have you considered overclocking your system to boost performance ?
> > http://www.tomshardware.com/overclock.html
> >
> 
> And get a whole of 15pps? :)
> Anyway, the P90 generally isn't very overclockable... I seriously recommend
> upgrading.
> 
> Margus

Any speed improvement on a P90 is noticable :)

  I also recommend manual bounding of the merge operation to help speed things
up.

-- 
Ken Tyler

See my 850+ Povray and 3D Rendering and Raytracing Links at:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Yes, those superellipsoids are one of POVs slow to render primitives
if you difference or merge them from each other. The latest renders I
just posted at p.b.i. has them and it is much slower if they are made
hollow via a removal of their interiors.
Manually bounding seems to slow these further.
You might try using a 'fade_distance' in your lights.
Animated Gif of that res is going to be a large file, Mpg would be so
much better, even a decent Avi.

Bob

Ken <tyl### [at] pacbellnet> wrote in message
news:37C77070.4DFF6E76@pacbell.net...
>
>
> Stuart Johnston wrote:
> >
> > If you go to the following web page you'll hopefully get my drift.
> > Im only gettting 13pps on a P90 with POV.win.
> > I think it's the superellipsoids, but doing an 8x640x320 animation
> > means-35hrs.
> > I now appreciate I could cut down on my lights (6 of).
> >
> > Go here....Please...Please...Please....
> > http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html
> >
> > Stu### [at] ozemailcomau
>
> Merging superellipsoids on a P90 is your most likely culprit along
with the
> fact you have transparent objects in the scene which are inherently
slower
> to render than other objects anyway.
>
> Have you considered overclocking your system to boost performance ?
> http://www.tomshardware.com/overclock.html
>
> --
> Ken Tyler
>
> See my 850+ Povray and 3D Rendering and Raytracing Links at:
> http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Bob, I tried to email you on this one but the email connect didn't
respond.
Do you know anything more about POV to animation.

I've Javascripted a series of POV's I generated. go to the page below to
view my situation.
http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html

Bob Hughes wrote:

> Yes, those superellipsoids are one of POVs slow to render primitives
> if you difference or merge them from each other. The latest renders I
> just posted at p.b.i. has them and it is much slower if they are made
> hollow via a removal of their interiors.
> Manually bounding seems to slow these further.
> You might try using a 'fade_distance' in your lights.
> Animated Gif of that res is going to be a large file, Mpg would be so
> much better, even a decent Avi.
>
> Bob
>
> Ken <tyl### [at] pacbellnet> wrote in message
> news:37C77070.4DFF6E76@pacbell.net...
> >
> >
> > Stuart Johnston wrote:
> > >
> > > If you go to the following web page you'll hopefully get my drift.
> > > Im only gettting 13pps on a P90 with POV.win.
> > > I think it's the superellipsoids, but doing an 8x640x320 animation
> > > means-35hrs.
> > > I now appreciate I could cut down on my lights (6 of).
> > >
> > > Go here....Please...Please...Please....
> > > http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html
> > >
> > > Stu### [at] ozemailcomau
> >
> > Merging superellipsoids on a P90 is your most likely culprit along
> with the
> > fact you have transparent objects in the scene which are inherently
> slower
> > to render than other objects anyway.
> >
> > Have you considered overclocking your system to boost performance ?
> > http://www.tomshardware.com/overclock.html
> >
> > --
> > Ken Tyler
> >
> > See my 850+ Povray and 3D Rendering and Raytracing Links at:
> > http://home.pacbell.net/tylereng/index.html

Post a reply to this message

Don't know why my email wouldn't be right.
  inv### [at] aolcom?subject=Pov-News

If anyone email me without "Pov" in the subject line I probably don't
see it. I'm sorry if anyone has and I never sent replies.

Anyway, I saw your web page again, the animation shows you got it
working out pretty good afterall.
You asked about RAM, quick answer is yes.  Anything to keep from going
to disk. There's probably some differences in the platforms used (DOS,
Windows, Mac, etc) but I don't have a clue about that.

STILL SOME PROBLEMS.....
1. I had to colour the sectioning plane for each object to make it
show the colour.
Otherwise the the individual objects would only render as hollow
surfaces.
    Q2.Why can't it section to a solid surface?

Are you putting textures after at the end of CSG, ie. difference
{object{Object1}object{Object2} texture {Here}}?
Rule is that any object (primitive, previous CSG, etc) that is
textured before another CSG will retain that texture instead of
acquiring the whole of a final CSG. If texture (or just pigment,
finish, etc.) is applied within a object (or primitive) statement
within the CSG it also retains it's own texture.  If no texture exists
in the object being used as a basis for CSG and a secondary part used
does not exist and also no final texture at the end of the CSG
operation then you get those black empty interaction zones.

2. To rotate around the sectioning plane on the left, I had to stuff
around with finding the "vector". I tried to work it our
geometrically, but gave up.
    Q3.I would prefer POV to find the vector of intersection of two
surfaces and rotate about that. Any ideas?

I give up too, but think there may be solutions from what I understand
of it.  Say you get the vdot of two pivot points for example and
vrotate maybe.  But I'm just throwing out guesses so I'll be quiet.
Others may have ideas.

    Q4.Im using Paintshop Pro 5.01's animation shop for animating to
gif (any better suggestions)?.

The Gif animation you have uploaded to your web page wasn't too bad.
I managed to go through the sequences okay. Although it needed
explanation of each segment if anything.  There are certain
specialized animation programs like Flash and such "for the web" type
things that might be great for this. Again I couldn't tell about any
of it.

Bob

Stuart Johnston <stu### [at] ozemailcomau> wrote in message
news:37E04EAA.7497F36B@ozemail.com.au...
> Bob, I tried to email you on this one but the email connect didn't
> respond.
> Do you know anything more about POV to animation.
>
> I've Javascripted a series of POV's I generated. go to the page
below to
> view my situation.
> http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html
>
> Bob Hughes wrote:
>
> > Yes, those superellipsoids are one of POVs slow to render
primitives
> > if you difference or merge them from each other. The latest
renders I
> > just posted at p.b.i. has them and it is much slower if they are
made
> > hollow via a removal of their interiors.
> > Manually bounding seems to slow these further.
> > You might try using a 'fade_distance' in your lights.
> > Animated Gif of that res is going to be a large file, Mpg would be
so
> > much better, even a decent Avi.
> >
> > Bob
> >
> > Ken <tyl### [at] pacbellnet> wrote in message
> > news:37C77070.4DFF6E76@pacbell.net...
> > >
> > >
> > > Stuart Johnston wrote:
> > > >
> > > > If you go to the following web page you'll hopefully get my
drift.
> > > > Im only gettting 13pps on a P90 with POV.win.
> > > > I think it's the superellipsoids, but doing an 8x640x320
animation
> > > > means-35hrs.
> > > > I now appreciate I could cut down on my lights (6 of).
> > > >
> > > > Go here....Please...Please...Please....
> > > > http://www.ozemail.com.au/~stuartjohnston/POV/POV_html.html
> > > >
> > > > Stu### [at] ozemailcomau
> > >
> > > Merging superellipsoids on a P90 is your most likely culprit
along
> > with the
> > > fact you have transparent objects in the scene which are
inherently
> > slower
> > > to render than other objects anyway.
> > >
> > > Have you considered overclocking your system to boost
performance ?
> > > http://www.tomshardware.com/overclock.html
> > >
> > > --
> > > Ken Tyler
> > >
> > > See my 850+ Povray and 3D Rendering and Raytracing Links at:
> > > http://home.pacbell.net/tylereng/index.html
>
>
>

Post a reply to this message