SPPM renderer (CPU-only)

[Dade]

An interesting finding today. I decided to try diamond cauchy settings with my sppm luxball. (viewtopic.php?f=14&t=5598) But I noticed that it took much longer to calculate the hit points. I am guessing this is due to the high IOR. Any thoughts?

May be, if there are a lot of internal reflections, the average length of eye paths will much much higher, leading to longer time for the eye path.

[patro]

hi,
i'm playing with the win 64 build shared by LordCrc and BinaryCortex.
with the last build from BinaryCortex that not includ the latest submissions, we find out that the build hate render resolution that contains "0".
luxrender seams to start but then it crash.
600X450 crashed
800X600 crashed photon independent

799X598 working like a charm, we also noticed that the ram usage decreased from 3Gb to 2Gb for same resolution

thanks for the toy

[neo2068]

hi,
i'm playing with the win 64 build shared by LordCrc and BinaryCortex.
with the last build from BinaryCortex that not included the latest submissions, we find out that the build hate render resolution that contains "0".
luxrender seams to start but then it crash.
600X450 crashed
800X600 crashed photon independent

799X598 working like a charm, we also noticed that the ram usage decreased from 3Gb to 2Gb for same resolution

thanks for the toy

On my system all runs ok. Did you use a particular scene or crashes it with all scenes?

[patro]

On my system all runs ok. Did you use a particular scene or crashes it with all scenes?

every scene, this heppen to me and BinaryCortex.

[neo2068]

On my system all runs ok. Did you use a particular scene or crashes it with all scenes?

every scene, this heppen to me and BinaryCortex.

Ok, I updated to the latest changeset and now luxrender crashes, too. The problem seems to be introduced with after changeset 939419d8bf91. That was my previous testbuild.

I investigated the changes that have been made since my working testbuild and i found the culprit. It has something to do with changeset d63d81b99bc5

SPPM: moved UpdateFilm() method to HitPoints class and it now uses the PixelSampler

[neo2068]

Neo,
wich is your render resolution limit with 8GB?
with 4Gb we can't go over 900x7.. thought..... above resolution make the computer freeze.

Yes, I crashed my pc with 1100x1100. That's the reason I was gone in IRC suddenly. I had to restore my RAID.
With 900x900 and the cornell box lux uses approx. 5 GB of memory. With 1000x1000 it uses approx. 6,3 GB. With 1100x1100 it has to swap the memory to harddisk and the pc freezes.

[Dade]

The above problems should have been fixed by latest commits

[binarycortex]

The above problems should have been fixed by latest commits

I think it was fixed by LordCrc's out-of-bounds memory fix. It's working now for me.

[binarycortex]

O_O

14 minutes

[tomb]

O_O

default.jpg

some really hard lightpaths captured there!