Nicolas Alvarez napsal(a):
> Jan Dvorak escribió:
>> torus is tested only if its bound fails. It is bounded by a tight 
>> difference of two cyliders.
> 
> Interesting fact. I knew it, now that you mention it; but I didn't 
> remember (been a while since I read it).
> 
> Any idea why both torus and its bounding shape have such low hit 
> percentage?
It seems that the number of torus bound tests is used to calculate the 
success percentage. See the table, rays shot. The actual success rate 
for torus in that table is 976314/1072053=91%

Post a reply to this message

Thanks!

Sven


"Jan Dvorak" <jan### [at] centrumcz> schrieb im Newsbeitrag 
news:479d4019@news.povray.org...
> global_settings{
>   photons{
>     count image_width*image_height
>     ...
>   }
>   ...
> }
>
> untested
> Sven Littkowski napsal(a):
>> Shooting the image with those keywords... Hmm, do you mean that I need to 
>> put these two keywords inside the camera directive? To be honest, due the 
>> lack of experience and knowledge with these two keywords, i would just 
>> like to ask you to give an example where and how to use these two 
>> keywords in a scene. I think, that should help me.
>>
>> Thanks, Jan.
>>
>> Sven
>>
>>
>>
>> "Jan Dvorak" <jan### [at] centrumcz> schrieb im Newsbeitrag 
>> news:479cff7f@news.povray.org...
>>> You might decide to shoot image_width*image_height*some_constant 
>>> photons. Some_constant==1 might work well but feel free to increase for 
>>> high quality or decrease for faster render. Use the count keyword and 
>>> watch POV-ray do its best.
>>> Sven Littkowski napsal(a):
>>>> Hmm... THAT sounds interesting and promising, Jan. I looked into the 
>>>> POV help file, and see the keywords "image_width" and "image_height". 
>>>> And also some examples, how to use them. I really think, this could 
>>>> shorten the calculation time, if I can find out, how to use them 
>>>> properly in connection with my photon map creation.
>>>>
>>>> Jan, can you give me some more advice in this? If you like, I could 
>>>> post the scene file to you. Please let me know. Thanks,
>>>>
>>>> Sven
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> "Jan Dvorak" <jan### [at] centrumcz> schrieb im Newsbeitrag 
>>>> news:479c31b4$1@news.povray.org...
>>>>> try using image_width to choose the photon count/spacing
>>>>> Sven Littkowski napsal(a):
>>>>>> Hi Ben,
>>>>>>
>>>>>> but even so, based on what I heard already, meanwhile, the photon map 
>>>>>> would still take 6 days, right?
>>>>>>
>>>>>> Sven
>>>>>>
>>>>>>
>>>>>>
>>>>>> "Chambers" <ben### [at] pacificwebguycom> schrieb im Newsbeitrag 
>>>>>> news:479bdf30$1@news.povray.org...
>>>>>>> Sven Littkowski wrote:
>>>>>>>> Hi.
>>>>>>>>
>>>>>>>> I have a scene, which already takes around 6 days to create the 
>>>>>>>> photon map for, if it is done in the same resolution like the 
>>>>>>>> remaining scene.
>>>>>>>>
>>>>>>>> I would like to know, if it is possible to use a lower resolution 
>>>>>>>> (let's say: 400x300) for the photon map (with the "save_file" 
>>>>>>>> option enabled), and then to stop and continue the scene in a high 
>>>>>>>> resolution (now with the "load_file" option enabled).
>>>>>>> Sure, I do it myself.  However, since the photon map is independent 
>>>>>>> from the scene resolution, you can set the image size absurdly low 
>>>>>>> (like +w1 +h1) and still get a full-quality photon map.
>>>>>>>
>>>>>>> -- 
>>>>>>> ...Ben Chambers
>>>>>>> www.pacificwebguy.com
>>

Post a reply to this message

Definatively, I will stay tunes! I am eager for the result, as well as I am 
in such a big need for that photon map file!

Be assured, you will like what you see, as soon as you can see the image 
itself.

The object(s) even allow you to set different day or night times (which 
influences the light inside the scene), as well as you have influence on the 
object self (such as rotor rotation and anges, open doors, etc.).

Best greetings,

Sven




"Nicolas Alvarez" <nic### [at] gmailisthebestcom> schrieb im 
Newsbeitrag news:479d42ea$1@news.povray.org...
> [Posting to newsgroup since other people may be interested]
>
> Now that you sent me the files... The scene is quite slow to render 
> (55pps) even without radiosity or photons. I tried with photons, and there 
> were very long periods where the "photons shot" counter didn't change, 
> which could mean POV-Ray is shooting lots of photons but "missing the 
> object".
>
> What I'm suspecting is that POV-Ray is creating sub-optimal bounding 
> boxes. I see a lot of difference objects on your scene. POV-Ray sometimes 
> does a bad job bounding difference/intersection CSG.
>
> I'm now rendering a 160x120 image to see the raytrace statistics at the 
> end, and see if there were a lot of misses or not. Stay tuned...

Post a reply to this message

Hi Sven!

I haven't seen your scene or know anything about it, but it could be
that two of Mike's excellent tutorials could help you with your bounding
issues:

Mike's isosurface tutorial:
http://www.econym.demon.co.uk/isotut/

Mike's holes tutorial:
http://www.econym.demon.co.uk/holetut/index.htm


HTH,
Florian

Post a reply to this message

Hi Jan,

I added that line to my photon global statement, and so far, I recognize 
that POV-Ray behaves very different to how it was doing the map before.

Yes, there is a clear speed bonus, I recognized that when setting POV to a 
resolution of 160x120. Now I have started at 3200x2400, and wait until some 
result or crash comes. The blocks of photos are now much smaller (before: 
ca. 40,000 before each break, now only 320). I will keep you up to date.

Sven



"Sven Littkowski" <sven [] jamaica-focus [] com> schrieb im Newsbeitrag 
news:479d75c1@news.povray.org...
> Thanks!
>
> Sven
>
>
> "Jan Dvorak" <jan### [at] centrumcz> schrieb im Newsbeitrag 
> news:479d4019@news.povray.org...
>> global_settings{
>>   photons{
>>     count image_width*image_height
>>     ...
>>   }
>>   ...
>> }
>>
>> untested
>> Sven Littkowski napsal(a):
>>> Shooting the image with those keywords... Hmm, do you mean that I need 
>>> to put these two keywords inside the camera directive? To be honest, due 
>>> the lack of experience and knowledge with these two keywords, i would 
>>> just like to ask you to give an example where and how to use these two 
>>> keywords in a scene. I think, that should help me.
>>>
>>> Thanks, Jan.
>>>
>>> Sven
>>>
>>>
>>>
>>> "Jan Dvorak" <jan### [at] centrumcz> schrieb im Newsbeitrag 
>>> news:479cff7f@news.povray.org...
>>>> You might decide to shoot image_width*image_height*some_constant 
>>>> photons. Some_constant==1 might work well but feel free to increase for 
>>>> high quality or decrease for faster render. Use the count keyword and 
>>>> watch POV-ray do its best.
>>>> Sven Littkowski napsal(a):
>>>>> Hmm... THAT sounds interesting and promising, Jan. I looked into the 
>>>>> POV help file, and see the keywords "image_width" and "image_height". 
>>>>> And also some examples, how to use them. I really think, this could 
>>>>> shorten the calculation time, if I can find out, how to use them 
>>>>> properly in connection with my photon map creation.
>>>>>
>>>>> Jan, can you give me some more advice in this? If you like, I could 
>>>>> post the scene file to you. Please let me know. Thanks,
>>>>>
>>>>> Sven
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> "Jan Dvorak" <jan### [at] centrumcz> schrieb im Newsbeitrag 
>>>>> news:479c31b4$1@news.povray.org...
>>>>>> try using image_width to choose the photon count/spacing
>>>>>> Sven Littkowski napsal(a):
>>>>>>> Hi Ben,
>>>>>>>
>>>>>>> but even so, based on what I heard already, meanwhile, the photon 
>>>>>>> map would still take 6 days, right?
>>>>>>>
>>>>>>> Sven
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> "Chambers" <ben### [at] pacificwebguycom> schrieb im Newsbeitrag 
>>>>>>> news:479bdf30$1@news.povray.org...
>>>>>>>> Sven Littkowski wrote:
>>>>>>>>> Hi.
>>>>>>>>>
>>>>>>>>> I have a scene, which already takes around 6 days to create the 
>>>>>>>>> photon map for, if it is done in the same resolution like the 
>>>>>>>>> remaining scene.
>>>>>>>>>
>>>>>>>>> I would like to know, if it is possible to use a lower resolution 
>>>>>>>>> (let's say: 400x300) for the photon map (with the "save_file" 
>>>>>>>>> option enabled), and then to stop and continue the scene in a high 
>>>>>>>>> resolution (now with the "load_file" option enabled).
>>>>>>>> Sure, I do it myself.  However, since the photon map is independent 
>>>>>>>> from the scene resolution, you can set the image size absurdly low 
>>>>>>>> (like +w1 +h1) and still get a full-quality photon map.
>>>>>>>>
>>>>>>>> -- 
>>>>>>>> ...Ben Chambers
>>>>>>>> www.pacificwebguy.com
>>>
>

Post a reply to this message

Thanks, Florian. I am gonna check 'em out.

Sven



"Florian Brucker" <tor### [at] torfboldcom> schrieb im Newsbeitrag 
news:479dbd61$1@news.povray.org...
> Hi Sven!
>
> I haven't seen your scene or know anything about it, but it could be
> that two of Mike's excellent tutorials could help you with your bounding
> issues:
>
> Mike's isosurface tutorial:
> http://www.econym.demon.co.uk/isotut/
>
> Mike's holes tutorial:
> http://www.econym.demon.co.uk/holetut/index.htm
>
>
> HTH,
> Florian

Post a reply to this message

>> I tried with photons, and there were very long periods where the 
>> "photons shot" counter didn't change, which could mean POV-Ray is 
>> shooting lots of photons but "missing the object".
> 
> Photon count went up until a minute of shooting passed, then it got 
> stuck at 41294 photons shot. Been at that number for *20 minutes*.

12 hours later, 208446 photons shot.

Post a reply to this message

My PC came to around 32,000, before it crashed. Let's see...

Sven



"Nicolas Alvarez" <nic### [at] gmailisthebestcom> schrieb im 
Newsbeitrag news:479dfa02$1@news.povray.org...


>>> I tried with photons, and there were very long periods where the 
>>> "photons shot" counter didn't change, which could mean POV-Ray is 
>>> shooting lots of photons but "missing the object".
>>
>> Photon count went up until a minute of shooting passed, then it got stuck 
>> at 41294 photons shot. Been at that number for *20 minutes*.
>
> 12 hours later, 208446 photons shot.

Post a reply to this message

Sven Littkowski escribió:
> My PC came to around 32,000, before it crashed. Let's see...
> 

I added autostop 0.0. It's supposed to improve speed. The manual says 
"always use autostop unless it causes problems". I can't tell if it 
"causes problems" until I see the final image :)

Post a reply to this message

> 12 hours later, 208446 photons shot.

Elapsed: 17h 41m
Photons shot so far: 249561

I still see extremely long periods of the counter not moving.

Post a reply to this message