 |
 |
|
 |
|
 |
|  |
|  |
|
 |
|
 |
|  |
|  |
|
 |
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] aol com
Visit my isosurface tutorial at http://members.aol.com/stbenge
Post a reply to this message
|
 |
|  |
|  |
|
 |
From: Warp
Subject: Re: Help me with megapov radiosity (Cornell box)
Date: 3 Jun 2000 08:05:12
Message: <3938f478@news.povray.org>
|
|
 |
|  |
|  |
|
 |
ryan constantine <rco### [at] yahoo com> 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
|
 |
|  |
|  |
|
 |
From: Warp
Subject: Re: Help me with megapov radiosity (Cornell box)
Date: 3 Jun 2000 08:07:00
Message: <3938f4e3@news.povray.org>
|
|
 |
|  |
|  |
|
 |
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
|
 |
|  |
|  |
|
 |
|
 |
|  |
|
 |