10-11-2015, 09:01 PM
This is intended behavior. The 1049b.png is about 4 million pixels and gets downscaled automatically.
We set the the limit the image render to about 2 million pixels (around 1080p resolution, exact number I forgot). The reason for this is Windows SDK cannot reliably handle large resolution images. From what I recall a 16megapixel picture can take up a few hundred megabytes of memory. It uses absurd amount of memory which can crash the app since all Windows store apps are memory limited.
Perhaps we can add some sort of option for you manually limit the render size, and issue a warning of crash. Like an "Automatically Downscale" checkbox setting.
I've reported the SDK bug to Microsoft awhile ago and they are not fixing it
We set the the limit the image render to about 2 million pixels (around 1080p resolution, exact number I forgot). The reason for this is Windows SDK cannot reliably handle large resolution images. From what I recall a 16megapixel picture can take up a few hundred megabytes of memory. It uses absurd amount of memory which can crash the app since all Windows store apps are memory limited.
Perhaps we can add some sort of option for you manually limit the render size, and issue a warning of crash. Like an "Automatically Downscale" checkbox setting.
I've reported the SDK bug to Microsoft awhile ago and they are not fixing it