Nice to know before "cooking" a map_c file
#1

Working on my Denmark map I was consistently getting very large "cooked" map_c files, in the order of 56000 kB or more (close to the limit, 65535 kB). However, inspecting the cooked map_c file revealed many chunks (32x32 pixel areas) seemingly "all white" were present (only one "all white" chunk should be in the cooked file). It turns out that during a previous blurring operation many of the white areas had been in fact assigned values between 230..254. This of course is detected as a "non-all white" and subsequently saved, drastically increasing file size. Thresholding all values between 128 (lowest land level) and 255 to 255 reduced the file size to approx. 19000 kB.

Hope this helps...
Reply


Messages In This Thread

Forum Jump:


Users browsing this thread: 1 Guest(s)