SQBVH

[Dade]

Found an odd bug with sqbvh, using it with this scene causes the instanced objects (the lamp housings) to just disappear!

I should have fixed this problem, it was triggered by the usage of no-triangle primitives (i.e. an area light with a sphere as primitive and instances): http://src.luxrender.net/lux/rev/3db8cbbf6887

[jensverwiebe]

Found an odd bug with sqbvh, using it with this scene causes the instanced objects (the lamp housings) to just disappear!

I should have fixed this problem, it was triggered by the usage of no-triangle primitives (i.e. an area light with a sphere as primitive and instances): http://src.luxrender.net/lux/rev/3db8cbbf6887

I verify commit fixes the issue ( JT's lamphousings are rendered now ).

Jens

[J the Ninja]

Found an odd bug with sqbvh, using it with this scene causes the instanced objects (the lamp housings) to just disappear!

I should have fixed this problem, it was triggered by the usage of no-triangle primitives (i.e. an area light with a sphere as primitive and instances): http://src.luxrender.net/lux/rev/3db8cbbf6887

I verify commit fixes the issue ( JT's lamphousings are rendered now ).

Jens

Yep. All's fine now. Thanks Dade!

Btw, this also seems to fix the crash I had on the previous page. That scene has sphere lights and instances as well, so I'm guessing it was something to do with that.

[Dade]

Btw, this also seems to fix the crash I had on the previous page. That scene has sphere lights and instances as well, so I'm guessing it was something to do with that.

Yup, for sure.

[neo2068]

There are still some cases where the sqbvh accelerator produces holes in the mesh.
The pictures show the result with different geometry and additional scattering media.

And sometimes I get this:

Code: Select all

[...]2012-03-16 16:35:53 Info: 12] A primitive of type class lux::InstancePrimitive, used in a SQBVH, isn't a triangle, falling back to bounding box clipping for building
[2012-03-16 16:35:53 Error: 13] SQBVH unable to handle geometry, too many primitives with the same centroid
[2012-03-16 16:35:53 Error: 13] SQBVH unable to handle geometry, too many primitives with the same centroid
[...]

Resulting in this:

[Dade]

There are still some cases where the sqbvh accelerator produces holes in the mesh.

The holes are more a side effect of the problem than the problem itself. QBVH can not store more than 64 triangles in a leaf. When the code is forced to produce a leaf and there are more than 64 triangles it has to discard all triangles after the first 64. This usually happen because it has reached the max. tree depth or because there are degenerated triangles.

At the moment, SQBVH seems to have some numerical stability problem and some time it starts to loop over the same split reaching the max. depth of the tree. There is a simple temporary workaround (i.e. http://src.luxrender.net/lux/file/12824 ... l.cpp#l481) to just stop spatial splits when thing starts to become too "small" but I'm looking for a solution of this problem. This is also one of the reasons why SQBVH performance can vary a lot on different scenes.

Neo2068, can you post the sources of the problematic scene ?

[neo2068]

There are still some cases where the sqbvh accelerator produces holes in the mesh.

The holes are more a side effect of the problem than the problem itself. QBVH can not store more than 64 triangles in a leaf. When the code is forced to produce a leaf and there are more than 64 triangles it has to discard all triangles after the first 64. This usually happen because it has reached the max. tree depth or because there are degenerated triangles.

At the moment, SQBVH seems to have some numerical stability problem and some time it starts to loop over the same split reaching the max. depth of the tree. There is a simple temporary workaround (i.e. http://src.luxrender.net/lux/file/12824 ... l.cpp#l481) to just stop spatial splits when thing starts to become too "small" but I'm looking for a solution of this problem. This is also one of the reasons why SQBVH performance can vary a lot on different scenes.

Neo2068, can you post the sources of the problematic scene ?

Here are the scene files. This is a ripped version of a more complex scene. Thus there are some unused and some strangely named materials. The walls are divided to fit a water surface which has been removed. There are some very long and thin triangles.

[jeanphi]

The holes are more a side effect of the problem than the problem itself. QBVH can not store more than 64 triangles in a leaf. When the code is forced to produce a leaf and there are more than 64 triangles it has to discard all triangles after the first 64. This usually happen because it has reached the max. tree depth or because there are degenerated triangles.

That's something I always wondered: could we just do an arbitrary split of the triangles when something like this happens? Less efficient than having all triangles in the same set, but better than degrading the rendering.

Jeanphi

[Dade]

The holes are more a side effect of the problem than the problem itself. QBVH can not store more than 64 triangles in a leaf. When the code is forced to produce a leaf and there are more than 64 triangles it has to discard all triangles after the first 64. This usually happen because it has reached the max. tree depth or because there are degenerated triangles.

That's something I always wondered: could we just do an arbitrary split of the triangles when something like this happens? Less efficient than having all triangles in the same set, but better than degrading the rendering.

We could definitively do an arbitrary split but this condition should happen, for QBVH, only if all the triangles in the leaf are degenerated or with the same centroid (i.e. "unable to handle geometry, too many primitives with the same centroid"). So it will something useful only if you have more than 64 degenerated/equal triangles in a leaf (i.e. it should be quite a corner case).

[Dade]

There are still some cases where the sqbvh accelerator produces holes in the mesh.

I should have fixed this problem with the latest patch.