You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In previous versions (47.14 and before), the File > Board > Save As Image option would snapshot the current map at the current display zoom level. Zooming out would thus result in a smaller file size than if the map is zoomed in.
However, in 47.15, it appears that the image is saved at the "mazimum zoom in" resolution, regardless of the currently displayed zoom level.
As an example, a 48x51 map was zoomed out to a level that, with 47.14, produced a 2.88MB image. When zoomed out to the same level with 47.15 and saved in the same way, the image file was 17MB, which was the same size as if the map had been zoomed to the largest size possible (and the image quality was the same as if that had been the case).
This makes it hard to produce an image that can be easily shared on e.g. Discord or other sites with a size cap (as well as causing a certain amount of storage bloat).
Might this be the result of changes required to implement the turn-by-turn snapshot functionality?
(It was suggested that I tag @arlith in this bug report.)
The text was updated successfully, but these errors were encountered:
This issue is still present in 47.16 - 'Save As Image' saves at maximum definition (which also means the turn-by-turn snapshots may eat peoples storage with long games on big maps). If there were some way to specify the zoom level, both for 'save as image' and for the turn-by-turn snapshots, so that it was consistent throughout the process, could that help?
MM 47.15 Standalone
Windows 10
OpenJDK 11
In previous versions (47.14 and before), the File > Board > Save As Image option would snapshot the current map at the current display zoom level. Zooming out would thus result in a smaller file size than if the map is zoomed in.
However, in 47.15, it appears that the image is saved at the "mazimum zoom in" resolution, regardless of the currently displayed zoom level.
As an example, a 48x51 map was zoomed out to a level that, with 47.14, produced a 2.88MB image. When zoomed out to the same level with 47.15 and saved in the same way, the image file was 17MB, which was the same size as if the map had been zoomed to the largest size possible (and the image quality was the same as if that had been the case).
This makes it hard to produce an image that can be easily shared on e.g. Discord or other sites with a size cap (as well as causing a certain amount of storage bloat).
Might this be the result of changes required to implement the turn-by-turn snapshot functionality?
(It was suggested that I tag @arlith in this bug report.)
The text was updated successfully, but these errors were encountered: