|
 |
Hi Chris
Let me first tell you, that I take your and the comment from Gilles really
serious and also think about them.
Its not that I am not intrested about what people say. However he did not
try the program and so
he comments something that he think about not the real thing that you can
download there.
You can use Radiosity and still use SMPOV with an 100% result. If ... IF
you have more then 1 picture to
render. Anyone who uses the program should knows that.
Therefore I recommend anyone first to try it and then to comment it.
HOW ?
Simply tell the program to make only 1 TILE out of each file.
Then SMPOV sends the WHOLE Picture to the diffrent render-CPU's wheter they
are local or they are remote, so long they are currently free.
Therefore all Radiosity calculations are perfect and still all CPU's stay
busy, without you having to worry about that.
Simply put all the pictures in the SMPOV-Que and on the next morning look
the results.
If you don't want "tiling" you can still serve up to 4 CPU's using the
actual SMPOV-Version.
This is not "the real thing". However its the logical consequence of the
history
of SMPOV and my contact with POV-Ray as an exampel for many
who have SMP-Mainboards and look for programms beeing able to use them.
Its in no-way a judgement about anyone who may know things better out of
experiences in his field
of (view) work.
History:
Last version of POV-Ray I had (and used) was on the AMIGA 1000.
Then long time I used other programms which had SMP-Support.
Lastly I found about that POV supports "photons" and therefore true
refraction
even if its "simulated".
I always wanted to use that in my pictures, so I switched to POV as a
person who is really new to that stuff how it is actual.
I quickly found that POV does not use the processors, and though noone told
me that there is the
"SAB-Renderfarm" already avaible (just didn't find that link that time), I
begun to do something
myself and for myself, however in mind that if its ready, and I like it, I
would share it with people.
I do that with all tools I make till now (see my homepage).
So this is where we are. I have no knowledge about radiosity or
possibilities, even theoretical HOW I could solve that problems. If someone
can explain that to me, I can think about IF I can put it in there.
At the moment I am using my freetime, to learn and to understand the
language from POV and I use SMPOV for quickly getting pictures out.
That is what is NOW. And it works really good.
Comment:
What I did here was just what the FAQ about SMP-Support "you can only start
two instance, each rendering a part of the picture" (FAQ about POV and
Multiprocessing). Show me a theoretical way to make it better, then I'll
think if I can implement that. Its NOT that I don't WANT to support special
features. I just don't know enough about HOW.
Future:
Currently I sent the code to Michael Vickery (he is as new with POV as
myself but he also likes the resulting pictures as I do) however he'll make
a PicPender version thats not ore dependent on any runtimes even under W9x,
so I can remove the 1 MB runtimes from the downloads-page and then no
installation will be required for noone.
I've no idea if he has plans to make other changes in the code, but he may
do so, AFTER he tested the programm himself and therefore has not only
theoretical knowledge of the program, but also a "feeling" how it is to use
it practically.
And last - but not least ...
***
are written with respect to the demands and wishes of those
> actually using the program. Therefore most of us are used to getting 'an
> open ear' when suggesting technical improvements
***
I agreee100% to you about that. If I had been upolite with my last reply I
may excuse at this point
and push a bit of that to my bad english :-).
I rather tried to explain that I see no way to implement that with my
current knowledge.
And I tried to explain that that may change if someone can tell me HOW to do
it.
But SO LONG thats not the case ...its usable -as is-.And its better to have
it then NOT to have it
as my personal experience.
If anyone can explain me a technical -clear- possibility to make SMPOV
better,
I'll maybe do that (after i understood it).
***
you can't seriously recommend
> your tool if you don't have some realistic experience using POV-Ray
***
My experience is with the scenes that are supplied with the
standard-distribution of
POV-Ray. I can render 90% of them faster then anyone else using SMPOV & POV
3.5.
That does NOT include the Radiostity-scenes (if the artifacts are a
problem)... but still 90% scenes left.
I render them in less then half the time they render on my Athlon 2000+ .
Isn't that worth a recommendation ?
I have 1 GB RAM here in this PC, if thats enough give me those files,
however
they are not part of the distribution and so I don't know how I shall
include them in my
decisions.
One last word. I really did that tool primarily for myself, not for selling
it and not for
getting popular. And I believe that those meals that you cook primarily for
yourself
are not the worst.
At last I hope you see that I am always open for comments, critics and
ideas.
--Theo
"Christoph Hormann" <chr### [at] gmx de> schrieb im Newsbeitrag
news:3D61FD55.7BE1B259@gmx.de...
>
>
> Theo Gottwald * wrote:
> >
> > [...]
> >
> > It's like with anything in the world. use it - or leave it. If you're
not
> > shure try it.
> >
>
> It's your right to think this way, but you should notice most successful
> extensions and tools developed around POV-Ray (and of course POV-Ray
> itself) are written with respect to the demands and wishes of those
> actually using the program. Therefore most of us are used to getting 'an
> open ear' when suggesting technical improvements. If you say "i don't
> need it, therefore i won't implement it" that's fine, just don't expect
> anyone to use the program.
>
> > CPU's cause I wrote it for myself and I like it.
>
> Gilles made an important point about that, you can't seriously recommend
> your tool if you don't have some realistic experience using POV-Ray. This
> includes writing your own scenes with several hundred megabyte of data and
> memory use for example.
>
> Christoph
>
> --
> POV-Ray tutorials, IsoWood include,
> TransSkin and more: http://www.tu-bs.de/~y0013390/
> Last updated 13 Aug. 2002 _____./\/^>_*_<^\/\.______
Post a reply to this message
|
|
