Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I found the aswer here: https://steamcommunity.com/app/431730/discussions/0/1741103267279077227/
it loses quality if you do not use the saved file,but the current file.
in my own python project i use a reserved image,and every time it scales.
i use the reserved image,not the current image.
so basic this is a programming problem.
where it scales the current image over and over again,instead of using a reserved full quality image.
scale'ing always effects the quality,even if you use a reserve image.
that just happen when you let the computer draw/scale your image.
the amount of pixels changes,thus it effects the quality.
a reserved image resets it every time,but in the end the drawing is modified.
its scaled.
this effect is clearly visable if you modify your image from like 32x32 to 128x128.
some line will be too thick other lines too thin....
a loss in quality.
only the original is pixel perfect.
let say i have 10 pixels, 5 red 5 blue,divide by 2 is no problem.
but now i scale to 11 pixels.
should it become blue or red? ( now we have a problem)
scale to 12 no more problems.
see how quality is lost.
we can end up with a remainder.
letting the computer modify/zoom/scale your file,will thus always effect the original.