mcmerge
mcmerge copied to clipboard
hetmankp
Memory Error
Trying to shift an old large existing world down 1 block aborts with Memory Error message at 6600/85175 chunks. Same results with windows executable and --immediate switch.
I was afraid this might happen one day. This will require a bit of re-work to save progress in smaller chunks but I probably won't get around to it for a while.
The only immediate solution I have for you is lots of RAM, though your map looks kind of big. To take advantage of all available RAM over ~3GB you will need to use a 64-bit Python installation (the executable I provide is only 32-bits). You should be able to get 64-bit installers for all the necessary components I list in the README as well, they're not always on the official project pages but there are collections of 64-bit installers people have put together on the internet.
Worst case make a contour file of the shift you intend and you can execute it on the map later even after other stuff has spawned around it, once I've resolved the issue.
Thanks, the 64-bit version worked for shifting! Presumably it will work for merging, but I have other maps to get positioned in the big blank area first before doing the contour trace and then actual merge.
One of these maps is actually two that were already pasted together some time ago, with a bunch of ugly transitions. Do you think it would be feasible (for me, or you, or anyone) to add a different way to do the contour trace to check chunk boundaries for discontinuities, something like long stretches of water vs. not water, sand vs. not sand, or height differences of 3 or more? I ask this without looking at the code very much, I was trying to get it to work on the Giganto Map before delving into it.:)
It should be possible to do though sounds fairly computationally intensive. You could always add the code into mcmerge if you find it convenient to get it in there. You could even build your own stand alone utility, the contour file format is documented in COUNTOUR.md so you can build up the contour file with your own utility and still use mcmerge to do the actual merging.
To do what you want however I would personally just build a contour file manually by cutting chunks out with something like MCEdit. The mcmerge tool has fairly sophisticated commands to combine contours, remove chunks from the contour, etc, so might be worth your while looking at that.