 |
|
|
|
|
|
| |
| |
|
|
From: Theo Gottwald *
Subject: SMPOV Download disabled till tomorrow, an error condition and one feature request
Date: 14 Aug 2002 14:02:23
Message: <3d5a9b2f$1@news.povray.org>
|
|
|
| |
| |
|
|
After the first few hours and some early reports and discussions,
I've decided to do some additional changes after communications in another
forum-thread
and with ABX .
We have 1 bug and 1 missing feature.
These changes will only be made in RenderAgent only.
About the bug: the 5 hrs. test has shown a memory leak condition that is a
side effekt
of new features (multithreading) that have been built in in "the last
moment".
DOWNLOAD of the new Version WILL BE DISABLED till this mistake is history.
I don't want distribute programms that crash after some time.The old version
(1 B) did not have that mistake so whoever has it can use it.
--Theo
PS: Its good to find all that small bugs as soon as possible.
Post a reply to this message
|
|
| |
| |
|
|
From: Theo Gottwald *
Subject: Download enabled, mistake was my own "greenhorn rendering-skill"
Date: 14 Aug 2002 14:26:33
Message: <3d5aa0d9@news.povray.org>
|
|
|
| |
| |
|
|
The dispersion_samples 120 and the "photon spacing 0.01 seemed to eat up
all my memory .
That was the whole problem. Maybe 120 is not the proper value for
dispersion_sample :-).
I should read the documentation before doing changes.
So download stays online, even though there is one new feature (minmize ...)
in the pipeline.
All testers welcome.
--Theo
"Theo Gottwald *" <The### [at] t-online de> schrieb im Newsbeitrag
news:3d5a9b2f$1@news.povray.org...
> After the first few hours and some early reports and discussions,
> I've decided to do some additional changes after communications in another
> forum-thread
> and with ABX .
>
> We have 1 bug and 1 missing feature.
>
> These changes will only be made in RenderAgent only.
>
> About the bug: the 5 hrs. test has shown a memory leak condition that is a
> side effekt
> of new features (multithreading) that have been built in in "the last
> moment".
>
> DOWNLOAD of the new Version WILL BE DISABLED till this mistake is history.
>
> I don't want distribute programms that crash after some time.The old
version
> (1 B) did not have that mistake so whoever has it can use it.
>
> --Theo
>
> PS: Its good to find all that small bugs as soon as possible.
>
>
Post a reply to this message
|
|
| |
| |
|
|
From: Jim Kress
Subject: Re: SMPOV Download disabled till tomorrow, an error condition and one feature request
Date: 14 Aug 2002 18:18:42
Message: <3d5ad742$6@news.povray.org>
|
|
|
| |
| |
|
|
Did anyone ever decide if your SMPOV would work for scenes with radiosity?
Jim
Post a reply to this message
|
|
| |
| |
|
|
From: Theo Gottwald *
Subject: Re: SMPOV Download disabled till tomorrow, an error condition and one feature request
Date: 15 Aug 2002 00:29:27
Message: <3d5b2e27$1@news.povray.org>
|
|
|
| |
| |
|
|
I would like to do that. Sent me one of those "radiosity" scenes and I'll
sent you the resulting picture.
Principialy I see no other restrictions then there are for animations. (No
Jittering).
But even with I have not seen problems personally.
--Theo
PS: Ot try it yourself and report me.
"Jim Kress" <nos### [at] kressworkscom> schrieb im Newsbeitrag
news:3d5ad742$6@news.povray.org...
> Did anyone ever decide if your SMPOV would work for scenes with radiosity?
>
> Jim
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Thu, 15 Aug 2002 06:29:50 +0200, "Theo Gottwald *"
<The### [at] t-onlinede> wrote:
>Principialy I see no other restrictions then there are for animations. (No
>Jittering).
It's a problem in the way radiosity works. The radiosity samples are
stored in an octree structure which is generated during pretrace and
trace. The problem is that samples from one part of the image can
affect another part of the image.
If you render the image in parts, the octree for each client will be
different and the resulting radiosity render will be different.
One thing that I've often though of but never had the time
experimenting with is merging radiosity data files. Since they are
plain ASCII files with the octree data dumped, you can try merging the
data files from all clients into one data file after the pretrace is
finished, then let them use that file in the trace step. This has the
drawback that the server will have to wait for all clients to complete
pretrace, but it may make your system useable with radiosity scenes,
which is a big plus.
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thats now the second time I hear that ...
I want to see that in real. Can you please sent me a ".pov"-File which I can
render in tiles to see the
problems ?
I've rendered nearly all the files in the distribution incl. some animations
and I could not see any such problems till now.
Doesn't mean I do not believe you, but I want to see this.
Maybe these influences are not really important ?
c.u.
--Theo
"Peter Popov" <pet### [at] vipbg> schrieb im Newsbeitrag
news:agemlukrl7ejp242e7ce7965dfgbcka3rf@4ax.com...
> On Thu, 15 Aug 2002 06:29:50 +0200, "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
>
> >Principialy I see no other restrictions then there are for animations.
(No
> >Jittering).
>
> It's a problem in the way radiosity works. The radiosity samples are
> stored in an octree structure which is generated during pretrace and
> trace. The problem is that samples from one part of the image can
> affect another part of the image.
>
> If you render the image in parts, the octree for each client will be
> different and the resulting radiosity render will be different.
>
> One thing that I've often though of but never had the time
> experimenting with is merging radiosity data files. Since they are
> plain ASCII files with the octree data dumped, you can try merging the
> data files from all clients into one data file after the pretrace is
> finished, then let them use that file in the trace step. This has the
> drawback that the server will have to wait for all clients to complete
> pretrace, but it may make your system useable with radiosity scenes,
> which is a big plus.
>
>
> Peter Popov ICQ : 15002700
> Personal e-mail : pet### [at] vipbg
> TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: So please WHERE is that file ?
Date: 15 Aug 2002 05:29:04
Message: <3d5b7460@news.povray.org>
|
|
|
| |
| |
|
|
In article <3d5b6fbd$1@news.povray.org> , "Theo Gottwald *"
<The### [at] t-onlinede> wrote:
> I want to see that in real.
How about those scenes in the "radiosity" directory in the official
distribution?
And those "problems" you do not seem to notice *do* exist. Take my word and
that of the POV-Team for it.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: So please WHERE is that file ?
Date: 15 Aug 2002 06:02:02
Message: <3d5b7c1a@news.povray.org>
|
|
|
| |
| |
|
|
In article <3d5b7460@news.povray.org> , "Thorsten Froehlich"
<tho### [at] trfde> wrote:
> In article <3d5b6fbd$1@news.povray.org> , "Theo Gottwald *"
> <The### [at] t-onlinede> wrote:
>
>> I want to see that in real.
>
> How about those scenes in the "radiosity" directory in the official
> distribution?
>
> And those "problems" you do not seem to notice *do* exist. Take my word and
> that of the POV-Team for it.
Now that I wasted my time with this to make it clear once and for all and to
end this nonsensical discussion of something that has been shown a million
times before:
Date: Thu, 15 Aug 2002 11:59:33 +0200
From: "Thorsten Froehlich" <tho### [at] trfde>
Newsgroups: povray.binaries.images
Subject: Radiosity in tiled images for those who don't get it
End of discussion.
Thorsten
____________________________________________________
Thorsten Froehlich
e-mail: mac### [at] povrayorg
I am a member of the POV-Ray Team.
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
So what you all are saying is, if you have a radiosity scene where you only
render a small portion of the full camera's view, that "tile" will not look
the same as that same area on the fully rendered picture? This does not
seem to be right. Each process started by SMPOV is simply rendering a part
of the whole camera's view, so each process would be calculating the
radiosity in the exact same way.
khaver
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: So please WHERE is that file ?
Date: 15 Aug 2002 12:55:30
Message: <3d5bdd02@news.povray.org>
|
|
|
| |
| |
|
|
In article <3d5bd44c@news.povray.org> , "khaver" <kha### [at] netzeronet> wrote:
> So what you all are saying is, if you have a radiosity scene where you only
> render a small portion of the full camera's view, that "tile" will not look
> the same as that same area on the fully rendered picture? This does not
> seem to be right. Each process started by SMPOV is simply rendering a part
> of the whole camera's view, so each process would be calculating the
> radiosity in the exact same way.
If you don't understand how POV-Rays radiosity works, just shut up, please.
Thorsten
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
