POV-Ray : Newsgroups : povray.unofficial.patches : Is anyone working on a distributed / stochastic / Monte Carlo ray-tracing patch for 3.7? Server Time
2 Mar 2024 02:48:47 EST (-0500)
  Is anyone working on a distributed / stochastic / Monte Carlo ray-tracing patch for 3.7? (Message 11 to 17 of 17)  
<<< Previous 10 Messages Goto Initial 10 Messages
From: clipka
Subject: Re: Is anyone working on a distributed / stochastic / MonteCarloray-tracing patch for 3.7?
Date: 23 Jul 2014 15:52:39
Message: <53d01287$1@news.povray.org>
Am 23.07.2014 20:18, schrieb Nekar Xenos:

> What I would like to see with radiosity is a system that distinguishes
> between different materials. Smooth shiny materials should have a
> smaller cone of scattering than cement which should have a very wide
> angle of scattering.

Well... no, not really. In smooth shiny materials, the primary direction 
of the cone of scattering virtually always depends on the angle of the 
incoming light, approaching classic specular reflection as the object 
gets even smoother.

To model such cases, POV-Ray's radiosity approach is inherently 
unsuited, because the sample information needs to be very 
memory-efficient and thus quite limited - POV-Ray only stores a single 
weighted average of all the light coming in, so any information about 
the direction of the incoming light is lost entirely.

What really kicks ass for smooth shiny (but not perfectly polished) 
materials is blurred reflections; with a strong blur it can even give a 
subtle edge to comparatively dull materials


That doesn't mean your idea would be all nonsense though - see the stuff 
I happen to have just shown off in the "Brilliant Spheres" thread on 
povray.binary.images ;-)

(Actually it's not /that/ much of a coincidence: As a first approach at 
"replacing" radiosity I plan to actually just keep using it but not 
cache the results (plus make sure that the secondary rays shot are 
different each time); and as I want UberPOV to fully support non-default 
brilliance settings, I figured that I might just as well add that to 
POV-Ray's radiosity first... And then one thing led to another, and I 
found myself adding all those fancy finish improvements that had been on 
my agenda for so long...)


Post a reply to this message

From: Alain
Subject: Re: Is anyone working on a distributed / stochastic / MonteCarloray-tracingpatch for 3.7?
Date: 23 Jul 2014 17:21:57
Message: <53d02775@news.povray.org>


> (Actually it's not /that/ much of a coincidence: As a first approach at
> "replacing" radiosity I plan to actually just keep using it but not
> cache the results (plus make sure that the secondary rays shot are
> different each time); and as I want UberPOV to fully support non-default
> brilliance settings, I figured that I might just as well add that to
> POV-Ray's radiosity first... And then one thing led to another, and I
> found myself adding all those fancy finish improvements that had been on
> my agenda for so long...)
>

And you did a marvelous job at that. Tank you very much :)


Post a reply to this message

From: Nekar Xenos
Subject: Re: Is anyone working on a distributed / stochastic / MonteCarloray-tracing patch for 3.7?
Date: 24 Jul 2014 11:58:37
Message: <op.xjienol6ufxv4h@xena.home>
On Wed, 23 Jul 2014 21:52:32 +0200, clipka <ano### [at] anonymousorg> wrote:


> (Actually it's not /that/ much of a coincidence: As a first approach at  
> "replacing" radiosity I plan to actually just keep using it but not  
> cache the results (plus make sure that the secondary rays shot are  
> different each time); and as I want UberPOV to fully support non-default  
> brilliance settings, I figured that I might just as well add that to  
> POV-Ray's radiosity first... And then one thing led to another, and I  
> found myself adding all those fancy finish improvements that had been on  
> my agenda for so long...)
>

You're our hero :)

-- 
-Nekar Xenos-


Post a reply to this message

From: clipka
Subject: Re: Is anyone working on a distributed / stochastic /MonteCarloray-tracing patch for 3.7?
Date: 24 Jul 2014 13:53:24
Message: <53d14814$1@news.povray.org>
Am 24.07.2014 17:58, schrieb Nekar Xenos:
> On Wed, 23 Jul 2014 21:52:32 +0200, clipka <ano### [at] anonymousorg> wrote:
>
>
>> (Actually it's not /that/ much of a coincidence: As a first approach
>> at "replacing" radiosity I plan to actually just keep using it but not
>> cache the results (plus make sure that the secondary rays shot are
>> different each time); and as I want UberPOV to fully support
>> non-default brilliance settings, I figured that I might just as well
>> add that to POV-Ray's radiosity first... And then one thing led to
>> another, and I found myself adding all those fancy finish improvements
>> that had been on my agenda for so long...)
>>
>
> You're our hero :)

Thanks. Sometimes I am. ;-)


Post a reply to this message

From: jhu
Subject: Re: Is anyone working on a distributed / stochastic /MonteCarloray-tracing =
Date: 1 Sep 2014 12:20:00
Message: <web.54049bc4b743e78d19b0ec40@news.povray.org>
clipka <ano### [at] anonymousorg> wrote:
> Am 24.07.2014 17:58, schrieb Nekar Xenos:
> > On Wed, 23 Jul 2014 21:52:32 +0200, clipka <ano### [at] anonymousorg> wrote:
> >
> >
> >> (Actually it's not /that/ much of a coincidence: As a first approach
> >> at "replacing" radiosity I plan to actually just keep using it but not
> >> cache the results (plus make sure that the secondary rays shot are
> >> different each time); and as I want UberPOV to fully support
> >> non-default brilliance settings, I figured that I might just as well
> >> add that to POV-Ray's radiosity first... And then one thing led to
> >> another, and I found myself adding all those fancy finish improvements
> >> that had been on my agenda for so long...)
> >>
> >
> > You're our hero :)
>
> Thanks. Sometimes I am. ;-)

How difficult would it be to adapt this to GPU rendering via OpenCL or CUDA?


Post a reply to this message

From: clipka
Subject: Re: Is anyone working on a distributed / stochastic /MonteCarloray-tracing =
Date: 1 Sep 2014 15:57:39
Message: <5404cfb3@news.povray.org>
Am 01.09.2014 18:16, schrieb jhu:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 24.07.2014 17:58, schrieb Nekar Xenos:
>>> On Wed, 23 Jul 2014 21:52:32 +0200, clipka <ano### [at] anonymousorg> wrote:
>>>
>>>
>>>> (Actually it's not /that/ much of a coincidence: As a first approach
>>>> at "replacing" radiosity I plan to actually just keep using it but not
>>>> cache the results (plus make sure that the secondary rays shot are
>>>> different each time); and as I want UberPOV to fully support
>>>> non-default brilliance settings, I figured that I might just as well
>>>> add that to POV-Ray's radiosity first... And then one thing led to
>>>> another, and I found myself adding all those fancy finish improvements
>>>> that had been on my agenda for so long...)
>>>>
>>>
>>> You're our hero :)
>>
>> Thanks. Sometimes I am. ;-)
>
> How difficult would it be to adapt this to GPU rendering via OpenCL or CUDA?

Very. At least that's what I still suspect.


Post a reply to this message

From: jhu
Subject: Re: Is anyone working on a distributed / stochastic /MonteCarloray-tracing =
Date: 2 Sep 2014 09:55:01
Message: <web.5405cb1c65080cc0d19b0ec40@news.povray.org>
clipka <ano### [at] anonymousorg> wrote:
> Am 01.09.2014 18:16, schrieb jhu:
> > clipka <ano### [at] anonymousorg> wrote:
> >> Am 24.07.2014 17:58, schrieb Nekar Xenos:
> >>> On Wed, 23 Jul 2014 21:52:32 +0200, clipka <ano### [at] anonymousorg> wrote:
> >>>
> >>>
> >>>> (Actually it's not /that/ much of a coincidence: As a first approach
> >>>> at "replacing" radiosity I plan to actually just keep using it but not
> >>>> cache the results (plus make sure that the secondary rays shot are
> >>>> different each time); and as I want UberPOV to fully support
> >>>> non-default brilliance settings, I figured that I might just as well
> >>>> add that to POV-Ray's radiosity first... And then one thing led to
> >>>> another, and I found myself adding all those fancy finish improvements
> >>>> that had been on my agenda for so long...)
> >>>>
> >>>
> >>> You're our hero :)
> >>
> >> Thanks. Sometimes I am. ;-)
> >
> > How difficult would it be to adapt this to GPU rendering via OpenCL or CUDA?
>
> Very. At least that's what I still suspect.

Oh well. Knight's Landing is just around the corner so OpenCL/CUDA might be
moot, but hopefully it's not too expensive.


Post a reply to this message

<<< Previous 10 Messages Goto Initial 10 Messages

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.