- 30 10月, 2021 6 次提交
-
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
Null-valued member variables were leading to trying to initialize std::strings with nullptr rather than printing "nullptr".
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
-
- 29 10月, 2021 3 次提交
-
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
Update filesystem/ and stb/ to latest versions. Start using git submodules for lodepng (and update to latest.)
-
由 Matt Pharr 提交于
Reduce the epsilon to better resolve fine shadows (especially in the Moana Island scene.) Also add a hack to fix a rare infinite loop when finding all intersections along a ray for subsurface scattering with quadric shapes (root cause bug not yet chased down.)
-
- 28 10月, 2021 5 次提交
-
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
The Future class is now gone, and its functionality ("is the result ready?", "give me the result value") is now folded into AsyncJob. This allows retrieving the result from multiple threads, with synchronization handled in AsyncJob. (This is more flexible than std::future allows, since we don't need either move semantics or the ability to pass along exceptions when the future is harvested.) This fixes a number of race conditions that helgrind was flagging during startup with complex scenes. (Our prior use of std::future wasn't correct in that we had unprotected access attempts from multiple threads.)
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
This allows users to not need to worry about thread safety in their callback implementations. In particular, this fixes a race in the BVHAggregate's use of ThreadLocal that rarely led to crashes or complaints about malloc heap corruption during BVH construction.
-
由 Matt Pharr 提交于
Given C++'s rules for initialization of statics, I don't think this is strictly necessary, but it makes helgrind happy and causes no harm.
-
- 27 10月, 2021 9 次提交
-
-
由 Matt Pharr 提交于
There were two signed integer multiplications that readily overflowed. They are now both unsigned, which is well-defined under overflow. Issue #177.
-
由 Matt Pharr 提交于
(Rather than just printing a warning.) Issue #152.
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
Not only could this make the scale go negative for half of the possible orientations, it could go to NaN as well. Fixes #130.
-
由 Matt Pharr 提交于
Fixes #146; thanks to @kanition for noting it.
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
- Pass along as much metadata as is still valid - Update pixelBounds when --crop, --repeatpix, or --flipy are used - Also updated the semantics of --crop's parameters to be w.r.t. the full image resolution
-
由 Matt Pharr 提交于
Also, add a color space check to checkImageCompatibility().
-
由 Matt Pharr 提交于
This is especially important for keeping track of what RGB color space images are in...
-
- 26 10月, 2021 6 次提交
-
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
For 3-channel images, write out the channels, whatever they are. For 4+, write R, G, B channels only (and error if not present)
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
If the first PDF was too large, it would become infinity when it was squared, which in turn would lead to a NaN being returned.
-
- 25 10月, 2021 2 次提交
-
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
Before, e.g. "float foo" "bar" would not lead to an error being issued.
-
- 23 10月, 2021 1 次提交
-
-
由 Matt Pharr 提交于
-
- 22 10月, 2021 1 次提交
-
-
由 Matt Pharr 提交于
-
- 21 10月, 2021 3 次提交
-
-
由 Matt Pharr 提交于
-
由 Matt Pharr 提交于
Instead it's computed as needed. (No performance impact in practice even though it does introduce some redundant computation.)
-
由 Matt Pharr 提交于
-
- 17 10月, 2021 2 次提交
-
-
由 Matt Pharr 提交于
And remove last (unused) vestiges of Oren-Nayar...
-
由 Matt Pharr 提交于
-
- 15 10月, 2021 1 次提交
-
-
由 Matt Pharr 提交于
-
- 12 10月, 2021 1 次提交
-
-
由 Matt Pharr 提交于
Issue #196 via @shadeops.
-