fabien <fab### [at] skynetbe> wrote:
: I hope that this dynamic range stuff will be implemented in POV-Ray
: someday.

  I suppose that it would take about 10-20 lines of code to implement it
(plus the code needed for a new keyword in global_settings...). And perhaps
not even that much.

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Ari-Matti Leppanen wrote:
>
> // Lstm:  Meridian of your local timezone (+1 hour =  +15 deg)
> //        in degrees (east = positive, west = negative)

Still not the same position as in other entrys or I have
the axes mixed up. I'm just going to leave it as it is.
This time I use the original sandstone maps because in
some reference images the color is less saturated.


_____________
Kari Kivisalo

Post a reply to this message

Will we be seeing a patch by you for the next MegaPOV? :)

Post a reply to this message

Kari Kivisalo <ray### [at] engineercom> wrote:
: Still not the same position as in other entrys or I have
: the axes mixed up. I'm just going to leave it as it is.

  Why the light source location in my original code wasn't good? I set it
with the instructions given in the site.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Tony[B] <ben### [at] catholicorg> wrote:
: Will we be seeing a patch by you for the next MegaPOV? :)

  If someone explains me how this dynamic range thing is calculated, then
why not?

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Gilles Tran wrote:
>
> How much memory is required, BTW ? Is it possible to render it in chunks, as
> this can reduce greatly the necessary memory ?

This one used 150MB peak and sysmon reported 500kB free ram at the
end of the render. Took 12 hours.

I'm trying it now at full res, without pretrace, saving rad data
and with normal on. If it starts to swap I assume I can just
stop and start a new partial trace. I changed nearest count from
6 to 12 to see if the noise smooths out.

  radiosity{
    save_file "sibenik3.rad"
    pretrace_start 1
    pretrace_end 1
    count 1200
    recursion_limit 3
    nearest_count 12
    error_bound 0.1
    normal on
  }


_____________
Kari Kivisalo

Post a reply to this message

Warp wrote:
>
>   Why the light source location in my original code wasn't good? I set it
> with the instructions given in the site.

The problem here is that the task is poorly specified.
Nowhere in the rules page I see explicitly specified
sun position. Nobody knows where it's supposed be so my
guess is as good as anyone's.

He says "you are not allow to change the lightsituation.!!!"
but doesn't say what the light situation is :(


_____________
Kari Kivisalo

Post a reply to this message

3C1F6A14.4AF9068C@engineer.com...
> He says "you are not allow to change the lightsituation.!!!"
> but doesn't say what the light situation is :(

Look at the "rules" page. There are some graphics too.


1 June 2001, 14:00
Timezone 1, no daylight saving
The camera must be looking south.

--

**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message

On Tue, 18 Dec 2001 18:08:52 +0200, Kari Kivisalo <ray### [at] engineercom> wrote:
> The problem here is that the task is poorly specified.
> Nowhere in the rules page I see explicitly specified
> sun position. Nobody knows where it's supposed be so my
> guess is as good as anyone's.

I don't participate this competition but I remember there were explanation about
sun. Isn't it good enough ?
http://hdri.cgtechniques.com/~sibenik2/competition/rules%20Kopie.gif

ABX

Post a reply to this message

Kari Kivisalo <ray### [at] engineercom> wrote:
: The problem here is that the task is poorly specified.
: Nowhere in the rules page I see explicitly specified
: sun position. Nobody knows where it's supposed be so my
: guess is as good as anyone's.

  The images at
http://hdri.cgtechniques.com/~sibenik2/competition/rules.htm?board=sibenik&action=display&num=1007893821

show quite clearly that the light should be coming from a direction which is
-1 unit in the x-axis, 3 units in the y-axis and 5 units in the z-axis. Thus
the light should be located at <-1,3,5>*Distance.
  It does not specify the distance, but as it should be the Sun, a distance
large enough should be used. This is what I did (I used <-1000,3000,5000>).

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message