 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Christoph Hormann <chr### [at] gmx de> wrote:
> ingo wrote:
>>
>> Playing a bit with the saving and loading radiosity data option in
>> MegaPov, to get rid of the blue images when using a blue sky_sphere.
>> Blue_blue_rad.jpg shows the standard situation, radiosity with a blue
>> sky_sphere.
>> Blue_wh_rad.jpg, here the radiosity data are used of a rendering with
>> a white sky. In the final there is of course the blue one.
>> Blue_red_rad.jpg, now with the radiosity data of a red sky.
>> Blue_wh_nc_rad.jpg, white radiosity data, but in the final all object
>> colours are removed.
>>
> That looks interesting, have you also tried changing the light sources?
Yeah. Maybe try it with no light sources at all, and ambient set to 0.
That would give a good idea exactly how much radiosity is doing in different
cases.
Geoff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in <3AEEB0B4.9AF46A99@gmx.de> Christoph Hormann wrote:
> That looks interesting, have you also tried changing the light
> sources?
>
Not yet, as it currently takes two renderings per image. It would be
nice if the whole process could be automated within POV-Ray. Do the
pretrace, save data, flip the value of a switch/constant, parse the
scene again and render with the gathered radiosity data.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in <3aeef957@news.povray.org> Geoff Wedig wrote:
> Yeah. Maybe try it with no light sources at all, and ambient set
> to 0. That would give a good idea exactly how much radiosity is
> doing in different cases.
>
Is this what you mean. Radiosity data gathering passage, one white
light_source and a sky:
pigment {gradient y color_map {[0, rgb 0.6] [1, rgb 1]}}
Rendering passage no light, no sky.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
Attachments:
Download 'rad.jpg' (9 KB)
Preview of image 'rad.jpg'
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ingo <ing### [at] homenl> wrote:
> in <3aeef957@news.povray.org> Geoff Wedig wrote:
>> Yeah. Maybe try it with no light sources at all, and ambient set
>> to 0. That would give a good idea exactly how much radiosity is
>> doing in different cases.
>>
> Is this what you mean. Radiosity data gathering passage, one white
> light_source and a sky:
> pigment {gradient y color_map {[0, rgb 0.6] [1, rgb 1]}}
> Rendering passage no light, no sky.
Exactly. However, I didn't realize that radiosity makes standard lighting
irrelevant, which it obviously does, or the objects wouldn't be so bright.
I thought it was just an 'extra' light that was added when the color was
determined.
So I learned something from the pic, at least. ;)
Geoff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ingo <ing### [at] homenl> wrote:
> in <3AEEB0B4.9AF46A99@gmx.de> Christoph Hormann wrote:
>> That looks interesting, have you also tried changing the light
>> sources?
>>
> Not yet, as it currently takes two renderings per image. It would be
> nice if the whole process could be automated within POV-Ray. Do the
> pretrace, save data, flip the value of a switch/constant, parse the
> scene again and render with the gathered radiosity data.
Should be pretty easy using the clock variable. Just animate a sequence of
two shots, and #if the variables that change.
Geoff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1 May 2001 16:54:14 -0400, ing### [at] homenl (ingo) wrote:
>Not yet, as it currently takes two renderings per image. It would be
>nice if the whole process could be automated within POV-Ray. Do the
>pretrace, save data, flip the value of a switch/constant, parse the
>scene again and render with the gathered radiosity data.
You could do that with the Pre_Scene_Command and Post_Scene_Command
INI file options.
Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG e-mail : pet### [at] tagpovrayorg
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in <dvqvetgsa97drekp8a1d6nunenfuhrtoq9@4ax.com> Peter Popov wrote:
> You could do that with the Pre_Scene_Command and Post_Scene_Command
> INI file options.
>
My problem with this and Geoff's solution is that you have to render
the complete image twice. The render data are saved when the first
render is completly done, not just after the the pretrace is done.
When rendering the second image, the pretrace sequence seems to be
done again. Or is this just the reading of the data file?
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ingo <ing### [at] homenl> wrote:
> in <dvqvetgsa97drekp8a1d6nunenfuhrtoq9@4ax.com> Peter Popov wrote:
>> You could do that with the Pre_Scene_Command and Post_Scene_Command
>> INI file options.
>>
> My problem with this and Geoff's solution is that you have to render
> the complete image twice. The render data are saved when the first
> render is completly done, not just after the the pretrace is done.
> When rendering the second image, the pretrace sequence seems to be
> done again. Or is this just the reading of the data file?
I would assume (perhaps incorrectly) that the pretrace would read in the
file, just as it does when you do it manually. Or is there something funky
you do in the manual reads?
Geoff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
in <3af01891@news.povray.org> Geoff Wedig wrote:
>> Or is this just the reading of the data file?
>
> I would assume (perhaps incorrectly) that the pretrace would read
> in the file, just as it does when you do it manually. Or is there
> something funky you do in the manual reads?
Changed count from 80 to 1000 to see if there is a time difference.
First pass the pretrace is finished after 18 min. Total render time, 45
min.
Second pass, reading the data/ pretrace, 4 min. Total render time 6
min. Quite a big difference, I didn't notice in the earlier experiments
as the total rendertime's where mutch shorter.
Ingo
--
Photography: http://members.home.nl/ingoogni/
Pov-Ray : http://members.home.nl/seed7/
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
ingo <ing### [at] homenl> wrote:
> in <3af01891@news.povray.org> Geoff Wedig wrote:
>>> Or is this just the reading of the data file?
>>
>> I would assume (perhaps incorrectly) that the pretrace would read
>> in the file, just as it does when you do it manually. Or is there
>> something funky you do in the manual reads?
> Changed count from 80 to 1000 to see if there is a time difference.
> First pass the pretrace is finished after 18 min. Total render time, 45
> min.
> Second pass, reading the data/ pretrace, 4 min. Total render time 6
> min. Quite a big difference, I didn't notice in the earlier experiments
> as the total rendertime's where mutch shorter.
Yes, that'd make a big difference. adding the always_sample off might also
make a difference.
Geoff
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
