Warp wrote:
>   In the official povray the maximum value for nearest_count is 10. I have
> used 10 in my image. Can it be bigger in megapov?

I used 12 but didn't check warnings.

-----------------------------------------------------------------------
Kari Kivisalo                                          www.kivisalo.net

Post a reply to this message

Kari Kivisalo <kar### [at] kivisalonet> wrote:
: I used 12 but didn't check warnings.

  At the beginning of radiosit.h there's this line:

#define MAX_NEAREST_COUNT 20

  I think it means that I'll try with nearest_count 20. Will post again when
the render is finished...

-- 
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

Warp <war### [at] tagpovrayorg> wrote...
>   I'm quite happy with the overall illumination (altough the contrast is
> too high compared to the original) and color bleeding, but there are
> horrible blotchy spots in the corners.
>   I just can't get rid of them.

I'm pretty sure there's a bug in there somewhere (still remaining from the
official version), but I haven't been able to find it.  :-(

-Nathan

Post a reply to this message

Btw. Since the radiosity values cited in the megapov documentation work
quite well with most scenes and usually one have to modify a couple of them
for specific scenes, wouldn't it be a good idea to make those values the
default values when they are not specified? Or are they already?
  It would be a lot easier to just write something like:

radiosity
{ count 100
}

instead of that gigantic block :)

  If some default value is not good for a specific scene, then one can just
specify a better value in the radiosity block when needed.

-- 
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

In article <3937d08c@news.povray.org> , Warp <war### [at] tagpovrayorg>  wrote:

>  You will immediately see them when you look at the
> resulting image:

Looks like you need more practice putting up wallpaper properly ;-)


       Thorsten

Post a reply to this message

Warp <war### [at] tagpovrayorg> wrote...
>   Btw. Since the radiosity values cited in the megapov documentation work
> quite well with most scenes and usually one have to modify a couple of
them
> for specific scenes, wouldn't it be a good idea to make those values the
> default values when they are not specified? Or are they already?
>   It would be a lot easier to just write something like:
>
> radiosity
> { count 100
> }
>

That is the way it works now.  (But the defaults are currently the
low-quality settings, not the high-quality ones.)

-Nathan

Post a reply to this message

you can always add any blocks you use regularly to the 'insert' menu of
pov.  that's one way to avoid typing.

Warp wrote:
> 
>   Btw. Since the radiosity values cited in the megapov documentation work
> quite well with most scenes and usually one have to modify a couple of them
> for specific scenes, wouldn't it be a good idea to make those values the
> default values when they are not specified? Or are they already?
>   It would be a lot easier to just write something like:
> 
> radiosity
> { count 100
> }
> 
> instead of that gigantic block :)
> 
>   If some default value is not good for a specific scene, then one can just
> specify a better value in the radiosity block when needed.
> 
> --
> 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 just found out recently I could make my own inserts. Saves having to type
commonly used items like camera and light_source.

ryan constantine wrote:

> you can always add any blocks you use regularly to the 'insert' menu of
> pov.  that's one way to avoid typing.
>
> Warp wrote:
> >
> >   Btw. Since the radiosity values cited in the megapov documentation work
> > quite well with most scenes and usually one have to modify a couple of them
> > for specific scenes, wouldn't it be a good idea to make those values the
> > default values when they are not specified? Or are they already?
> >   It would be a lot easier to just write something like:
> >
> > radiosity
> > { count 100
> > }
> >
> > instead of that gigantic block :)
> >
> >   If some default value is not good for a specific scene, then one can just
> > specify a better value in the radiosity block when needed.
> >
> > --
> > main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
> > ):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

--
Samuel Benge

E-Mail: STB### [at] aolcom

Visit my isosurface tutorial at http://members.aol.com/stbenge

Post a reply to this message

ryan constantine <rco### [at] yahoocom> wrote:
: you can always add any blocks you use regularly to the 'insert' menu of
: pov.  that's one way to avoid typing.

  I have never typed a whole radiosity block entirely by hand anyways.
  It looks, however, much nicer with just one or two settings.

-- 
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

The only effect of raising the nearest_count was a raise in rendering
time as well; this time it was 2 hours 14 minutes. The results are perhaps
a bit better, but not good:

http://www.cs.tut.fi/~warp/cornell/cornell.jpg

-- 
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