by Aaron » Fri Jan 29, 2016 12:57 pm
Hi Mistahgrizzly,
I've included the fix in the latest dev build (16.01 build 3), which is on the Pro downloads page now. This fault occurred for maps larger than 2048 x 2048 and smaller than 8192x8192, where L3DT uses a memory-mapped page file to store the map data (smaller maps are in memory, larger maps are paged to disk using mosaic maps). The recent update I did to use non-contiguous memory was not properly applied to the memory-mapped case, and I neglected to test a map in this size range (I think I was running 16k x 16k tests at the time.) Anyway, resizing should now complete OK.
Please note that you may get a set of errors during the mipmap generation after the resize. These errors complain about tile lock counts during tile saving, but these don't stop calculations or prevent saving, so you can safely ignore them. I will try to debug those errors now, but it might take a few more days.
Thanks again for the bug report.
Best regards,
Aaron.