| Anonymous | Login | Signup for a new account | 2013-05-21 23:25 PDT |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0000222 | LuxRender | Core | public | 2008-06-10 23:13 | 2009-11-25 00:29 | ||||
| Reporter | radiance | ||||||||
| Assigned To | Dade | ||||||||
| Priority | urgent | Severity | major | Reproducibility | always | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000222: black bounding boxes on some objects in some renders | ||||||||
| Description | Hi, look here: http://www.luxrender.net/forum/viewtopic.php?f=30&t=723&p=5720#p5720 [^] - supraserv (render of church building, black boxes) and here: http://www.luxrender.net/forum/viewtopic.php?f=12&t=717&st=0&sk=t&sd=a&start=30 [^] (render by pinko on bottom of page, black boxes) and here: http://www.luxrender.net/forum/viewtopic.php?f=8&t=645 [^] (renders of interior, black boxes on table) i think this might be a bug in the new tabreckkdtree. will post a testscene to replicate the problem in 1-2 hours here. Radiance | ||||||||
| Tags | No tags attached. | ||||||||
| Mercurial Changeset # | |||||||||
| Requires Documentation Update | |||||||||
| Requires Exporter Update | |||||||||
| Attached Files |  tab1.png [^] (584,693 bytes) 2008-06-11 05:50 tab2.png [^] (318,052 bytes) 2008-06-11 05:51 | ||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0000604) radiance (reporter) 2008-06-11 05:52 |
tested and confirmed. using tabreckdtree creates black boxes/errors in some scenes. switching to unsafekdtree solves the problem. i've emailed you a testscene dade to reprodude it. attached some pics to this bug to show difference. Radiance |
|
(0000609) Dade (developer) 2008-06-11 08:44 |
It looks like the problem is in the use of the combo waldtrianglemesh/tabreckdtree. tabreckdtree when used with barytrianglemesh. waldtrianglemesh has a fast path for orthogonal X/Y/Z triangles. I guess the combo of waldtrianglemesh fast path and tabreckdtree leads to some numerical problem (i.e. self-shadowing probably). I'm looking for the exact source of the problem at the moment. |
|
(0000613) Dade (developer) 2008-06-11 11:26 |
The problem was in the both in the scene and waldtrianglemesh. The scene includes degenerate triangles (i.e. a triangle where 2 or 3 vertices have the same position). waldtrianglemesh was returning a false hit on degenerate triangles with t = NaN. I added a fast path to correctly handle degenerate triangles. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2008-06-10 23:13 | radiance | New Issue | |
| 2008-06-10 23:13 | radiance | Status | new => assigned |
| 2008-06-10 23:13 | radiance | Assigned To | => Dade |
| 2008-06-11 05:50 | radiance | File Added: tab1.png | |
| 2008-06-11 05:51 | radiance | File Added: tab2.png | |
| 2008-06-11 05:52 | radiance | Note Added: 0000604 | |
| 2008-06-11 08:44 | Dade | Note Added: 0000609 | |
| 2008-06-11 11:26 | Dade | Note Added: 0000613 | |
| 2008-06-11 11:29 | Dade | Status | assigned => feedback |
| 2008-06-12 08:11 | Dade | Status | feedback => resolved |
| 2008-06-12 08:11 | Dade | Resolution | open => fixed |
| 2009-11-25 00:29 | jeanphi | Status | resolved => closed |
|
Issue History |
| Copyright © 2000 - 2012 MantisBT Group |
 |