Two years ago there was a "Strange cuts on rendered objects" thread in
this forum, where the objects were satellites in orbit as view from the
At the time, the work around employed was povr's -mb v3.6 restoration
fix. A working -mb bypassed all object bounding and depended instead on
the mesh's internal bounding.
The original problem was thought to be due the use of floats over
doubles in our bounding code - especially given the large scene dimensions.
I've confirmed using doubles for bounding fixes the original numerical
accuracy issue for both bounding methods 1 & 2. The current povr branch
code has moved bounding to doubles(a).
(a) Using all doubles for performance more than accuracy (related to
Github issue #363).
Aside: We have still have an issue where older, pre server crash, news
articles are not on the news server. Access via thunderbird is then
impossible. Hence, the brand new thread for the followup.
Post a reply to this message