![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
???? Well, is it? Please! Help me!
--
H.E. Day
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <38C291B7.811AADAE@fci.net>, Pov### [at] aol com wrote:
> ???? Well, is it? Please! Help me!
You might get faster results with an isosurface or isoblob in some
cases. I'm not sure though...I have never done any testing of their
relative speeds.
Also, make sure "sturm" is off, but that applies to the official version
as well...
--
Chris Huff
e-mail: chr### [at] yahoo com
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> You might get faster results with an isosurface or isoblob in some
> cases. I'm not sure though...I have never done any testing of their
> relative speeds.
Nope, not any faster.
> Also, make sure "sturm" is off, but that applies to the official version
> as well...
I mean the basic blob, or the code that makes it. Can you possibly speed
this up?
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
In article <01bf8705$ff3346c0$910a3ea6@default>, "H. E. Day"
<Pov### [at] aol com> wrote:
> I mean the basic blob, or the code that makes it. Can you possibly speed
> this up?
Hmm, it might be possible to add a third type of solving algorithm which
works the same way the isosurface code does, but with hard coded
functions. It would be faster than isosurfaces or isoblobs(I don't know
how much though), and might be faster than the two current methods. Or
it might be slower. Actually, I think this is how the isoblob shape got
started-an enhancement to the blob shape giving it a solving algorithm
which works like the isosurface's.
--
Chris Huff
e-mail: chr### [at] yahoo com
Web page: http://chrishuff.dhs.org/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nieminen Juha
Subject: Re: Is it possible to speed the blobs up in MegaPov?
Date: 6 Mar 2000 09:37:05
Message: <38c3c290@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Manual bounding might help a bit.
I have noticed that the automatic bounding calculates a bounding object
which is a lot larger than the actual shape of the object.
I have not tested the speed difference, though.
Btw: Would tesselation of the blob speed up the rendering? Is rendering
a mesh faster than a blob?
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Nieminen Juha <war### [at] sarakerttunen cs tut fi> writes:
>
> Btw: Would tesselation of the blob speed up the rendering? Is rendering
> a mesh faster than a blob?
Why keep people wanting to tessellate everything? I like the fact that
povray has clean and smooth primitives. They don't need a lot of
memory and are nice from a mathematical point of view.
Thomas
--
http://thomas.willhalm.de/ (includes pgp key)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nieminen Juha
Subject: Re: Is it possible to speed the blobs up in MegaPov?
Date: 6 Mar 2000 10:39:40
Message: <38c3d13c@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Thomas Willhalm <tho### [at] willhalm de> wrote:
: Why keep people wanting to tessellate everything?
I didn't say I want to tesselate it. I was just asking.
--
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Thomas Willhalm wrote:
>
> Nieminen Juha <war### [at] sarakerttunen cs tut fi> writes:
> >
> > Btw: Would tesselation of the blob speed up the rendering? Is rendering
> > a mesh faster than a blob?
>
> Why keep people wanting to tessellate everything? I like the fact that
> povray has clean and smooth primitives. They don't need a lot of
> memory and are nice from a mathematical point of view.
No one is arguing that POV-Ray should tesselate every object by default.
In fact I know I would never suggest such a thing. But there are certain
features that could be added if POV-Ray could be set to tesselate objects.
Some features that would benefit from this would be -
1. The ability to export .pov objects and scenes to other 3D file formats
2. Surface subdivision - currently only possible with meshes and only
can be done through use of memory and process intensive operations.
3. Displacement mapping - more accurate surface representations than are
currently possible with surface normal alone.
And this is just a sampling of the things you can do with tesselated
POV-Ray primitaves.
--
Ken Tyler - 1300+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html http://www.povray.org/links/
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: Nathan Kopp
Subject: Re: Is it possible to speed the blobs up in MegaPov?
Date: 6 Mar 2000 16:04:57
Message: <38c41d79$1@news.povray.org>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Ken <tyl### [at] pacbell net> wrote...
> Some features that would benefit from this would be -
>
> 1. The ability to export .pov objects and scenes to other 3D file formats
>
> 2. Surface subdivision - currently only possible with meshes and only
> can be done through use of memory and process intensive operations.
>
> 3. Displacement mapping - more accurate surface representations than are
> currently possible with surface normal alone.
And in some cases speed. Meshes render faster than objects such as
isosurfaces and probably faster than blobs.
-Nathan
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
From: H E Day
Subject: Re: Is it possible to speed the blobs up in MegaPov?
Date: 6 Mar 2000 20:35:14
Message: <38C45B96.4943336@fci.net>
|
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
> Manual bounding might help a bit.
I always bound manually. It the only possible way I could use blob to make
any models.
--
H.E. Day
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |