News for hackers. Stuff that matters.

A comment on 0.30000000000000004. Parent comment

Re:0.30000000000000004 by munchbunny on Monday December 02, 2019 @04:04PM (#21686923)
That's really interesting - hadn't thought of that before. To fix that, would you be able to do a square of the magnitude comparison with the radius and just bump the borderline cases, or is it more efficient without the extra branching?
[ Parent | on HN ]
Re:0.30000000000000004 by _bxg1 on Monday December 02, 2019 @04:11PM (#21686992)
I just did it across the board; since the error is in the floating-point noise I don't know if I'd even trust a comparison on that. Plus, the discrepancy between "bumped" and "unbumped" samples might cause some visible artifacts.
[ Parent | on HN ]
Re:0.30000000000000004 by cellular on Monday December 02, 2019 @07:51PM (#21688827)
Direct3D used to have a Z-bias for a similar problem: rendering pictures hanging on walls at a far Z depth. Their whql tests even tested for it.

It was fun discovering all the corner cases while debugging drivers.

[ Parent | on HN ]