Crop Causing a crash.

ID:1462838
 
Jan 4 2014, 1:33 pm
(See the best response by DarkCampainger.)
Apparently cropping an image file from 1x1 to anything over 4000x4000 seems to crash the procedure. Am I hitting some sort of limit?
Jan 4 2014, 2:01 pm
May I ask why you would want an image to be bigger than the resolution of the average computer monitor?
Jan 4 2014, 3:07 pm
I've created a MapImaging procedure that can turn an entire map into a PNG the size of the map with the tiles eaching being the default 32x32 or 16x16 , 8x8 , 4x4 , 1x1.
Jan 4 2014, 4:08 pm
Do you have sleeps or set to background so there are no infinite loops?
Jan 4 2014, 4:21 pm
Best response
4096 seems to be the maximum dimension that it can handle.

You'll have to output the map in a series of "tiles" (such as 256x256 or something) that you then stitch together outside of BYOND. ImageMagick would be a good fit for this (this post has an example, you'd want the 'montage' command with the 'tile' parameter set to the number of columns)
Jan 5 2014, 9:28 am
In response to DarkCampainger
DarkCampainger wrote:
4096 seems to be the maximum dimension that it can handle.

You'll have to output the map in a series of "tiles" (such as 256x256 or something) that you then stitch together outside of BYOND. ImageMagick would be a good fit for this (this post has an example, you'd want the 'montage' command with the 'tile' parameter set to the number of columns)

Thank you.