Problems using --scale 0.0000001 about potreeconverter HOT 2 CLOSED

Maybe it's because

v = static_cast<int32_t>(detail::sround((value - offset) / scale));

overflows for x and y but not z?
One problem could be that offset is always 0 and therefore we already lose quite a bit of the integer range.
Offset should probably be the min value of the bounding box or something like that.
I've only initialized the bounding box in https://github.com/potree/PotreeConverter/blob/master/PotreeConverter/include/LASPointWriter.hpp
and was under the impression that it automatically initializes the offset but maybe that is not the case since one of the las files I've converted has a 0 0 0 offset.

A warning, or even better abortion, should occur if the integer range is not enough to hold all values for a given scale and bounding box extent.
And maybe a warning if scale is < 0.001 because hardly any 3d scanner has a sub mm accuracy. Besides, laz compression suffers from unnecessary low scale.

from potreeconverter.

Could be. X and Y values are around 900, while Z is between 0 and 12.

from potreeconverter.