I am plan to investigate this issue and resolve it during next few weeks (after begin of Bcon3)
Thanks @sentharn for reporting and the attached scene as well. I have able to reproduce this problem on a machine with Intel® Arc™ A770 for RT HW (Embree4) path and I have also can confirm that…
@PratikPB2123 > Nvidia GPUs are reporting this error only in 3.6 (maybe we need a separate report to handle this?) Something wrong on Blender 3.6 (and 3.6 only) side with execution of this…
@sentharn I can confirm that I can observe this crash with my Intel® Arc™ A770 Graphics - but for me, a crash are happening regardless of Embree4/RTHW usage and it is related to denoising -…
I don' think that Metal and Optix are using this file at all - Metal have own version of scene_intersect*
functions in "kernel\device\metal\bvh.h" and Optix also have own version in `kernel\devic…
As I see buildbot have successfully build this PR for all platforms and all tests have beeen successfuly finished - considering this as success, I will rebase this changes and will merge them into…
In case of approval of this pull request I would prefer to keep initial 4 commit separated (if there are no objections from Blender side) - so when review part of the process will finished, I will…
Well, an idea here what when we have free slots in INTEGRATOR_SHADOW_ARRAY
tfar won't be decreased basically from base value, but as soon as we reach this condition if (num_recorded_hits + 1 >= max_record_hits) {
, then we will find maximumum t
value among all founded intersection and set it to tfar (which is supported, according to documentation "The filter function is further allowed to change the hit and decrease the tfar value of the ray but it should not modify other ray data nor any inactive components of the ray or hit." - as a result Embree will try to find any other intersection which will be closer to the ray origin that our the most distant hit - and if it will be possible, then we will got a hit, and in this intersection filter function we will replace this the most distant hit by new one (according to logic of "max_t" filtering).
@brech Considering that this problem making check of functional changes really hard (which is a problem, if you working on some CPU optimistaions) - is it possible at least add preprocess…