It's mainly CPU-bound, but the speed of your drive (for loading artwork) and speed of your RAM will influence things. And while things like effects do take advantage of multiple cores, I also find it helpful to have a CPU with a high single-core performance. It's better with a handfull of cores and high performance per core, than a huge heap of cores with lower performance per core.

I find it a nice resource. It should install fine with CC3+, but the procedures do require some manual unzipping of some zip files, so it is important to unzip these exactly as described in the guides, as ending up with one more or one less folder in the path is guaranteed to lead to red X'es.....

Note that symbols in CC3+ are just standard .png files. To get the right size, they should be 20 pixels per map unit for overland maps (so 20 pixels/mile), but you can also scale them inside CC3+ itself.

The difference is because the command increases the number of pixels that will be handled in each pass. This means that a bigger chunk of your map is processed in each pass, and therefore requiring fewer passes overall.

Not sure exactly how the algorithm is working internally, but it seems to like keeping the start/end node of the polygon (which would be located where you started drawing the poly in the first place.)

A few ways to deal with this:

• Try taking out smaller chunks, doing it over several operations.
• Draw a completely new polygon instead, using the trace feature of the tool to trace the part of the coastline you want to keep, instead of using the edit feature.