From a67fd4a2b3673c26a3ca008d8a1e05d7f323ef27 Mon Sep 17 00:00:00 2001 From: Hajime Hoshi Date: Sat, 15 Aug 2020 15:39:25 +0900 Subject: [PATCH] mipmap: Bug fix: Adopt 32 for tooBigScale I found the case that 64 was not enough on Huawei ALE-L02. --- internal/mipmap/mipmap.go | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/mipmap/mipmap.go b/internal/mipmap/mipmap.go index 35bd9685e..f02e37ca6 100644 --- a/internal/mipmap/mipmap.go +++ b/internal/mipmap/mipmap.go @@ -282,8 +282,8 @@ func mipmapLevelFromDistance(dx0, dy0, dx1, dy1, sx0, sy0, sx1, sy1 float32, fil // Use 'negative' mipmap to render edges correctly (#611, #907). // It looks like 128 is the enlargement factor that causes edge missings to pass the test TestImageStretch, - // but we use 64 here for environments where the float precision is low (#1044, #1270). - var tooBigScale float32 = 64 + // but we use 32 here for environments where the float precision is low (#1044, #1270). + var tooBigScale float32 = 32 if scale >= tooBigScale*tooBigScale { // If the filter is not nearest, the target needs to be rendered with graduation. Don't use mipmaps.