Jimsocks wrote:OK so I have been mapping it up today after seeing the new release, and I have a question: why does it take a lifetime for the program to complete a landmass "difference merge"?
I work on really large maps (40x40 inches at 300 ppi), so that's a factor, but I am running on intel i9 9900K, an RTX 2080, all solid-state hard drives, and 64 GBs of DDR4 3200 RAM. This beast can run oodles of photoshop renders on gigantic 600 ppi images in mere seconds, yet it takes around 30 minutes to do a difference merge on a few landmasses. What gives on that? On a rig this speedy, I ain't used to waiting on anything to process so it really stands out- 30 mins seems like a lifetime.
Glad you liked the archipelago option!
On your question, the short answer is that OWM does true Bezier path merging (that is, it doesn't turn the shapes to linear vectors to do this), so it's a CPU intensive operation.
One factor maybe that your landmasses have a lot of points when so many may not be needed (that depends on how your created them). You can try the "reduce points" tool from the tool menu and different tolerance values to see if OWM finds points to simplify. You can look at the landmasses and see if the simplification is too much (it normally shouldn't be with a tolerance of 1 or less px).
Let me know if that makes the merge operations go a bit faster.
Alejandro S. Canosa
Three Minds Software