Those spikes are miter joints, the issue happens when nodes are placed to create very sharp corners on wide lines. It happens more easily on highly detailed coastlines.

One way to get rid of them is to manually go in and remove some nodes from the coastline to fix it. Remember, it is caused by two close nodes at the base of the spike, there isn't a node at the end. And note that you only need to edit the coastline, which is a separate entity from the landmass. This problem doesn't happen to filled entities like the landmass is.

The second option is to just drop the coast outline altogether, and use a glow effect on the landmass instead, as this completely avoids the problem.

Those are the floorplan and battlemap collections right? If so, yea, they are already included in various other products/annuals

These needs to be installed separately.

Yes

For a full backup, you do need the data directory, install directory, and registry data. No dll's needs to be registered. But I'll normally recommend just backing up the data directory, and instead of backing up registry/install, do a new install and then copy over the data directory (avoid overwriting newer files).

I just love everything you can do with CC3+ thanks to its CAD roots. I've lost count of how many weird things I've done with it that doesn't have anything to do with mapping (Well, I guess some of them can be called mapping in a very wide definition of the term).

For all practical purposes, yes.

As far as I know, no, it can't be automated. There isn't a macro-version of this command

This button is a relic from the time before styles, where you only had a single "set" of symbols. The catalog buttons are meant to load the catalogs belonging to the current active style, and no styles come with a simple catalog, so it is basically useless (and confusing) on modern installs. Unless you hard-code it to the old simple catalog, it is going to just display an empty catalog list most of the time. If a style does define a simple catalog (The main DD3 style actually does this for legacy reasons, put it is just a pointer to the old catalog, and not really a DD3-version of it) you can easily find it by clicking the :CC2SYMICOND: button yo get all catalogs defined for the current stylke.

Everything in the bundle is compatible. Just make sure that when downloading the installers from your profantasy registred user page that you grab the ones that are labeled as being for CC3+ if there are more than one to choose from.

Also, make sure to (re-)install the latest CC3+ update as the last thing you do, as that do some fixing up.

These messages are due to a library file being accidentally copied by an installer into the installation directory. Please close down CC3+ and delete cc2per.dll from your installation directory (c:\program files(x86)\ProFantasy\CC3Plus)

These are normal errors when you are using a style that doesn't have certain tools. Not all styles have all tools. This isn't normally an installation error. For example, dungeon styles doesn't have landmass tools. It can also happen if the style of your map has been changed, which can be changed from :CC2PRESETS:

The forum account is separate from your ProFantasy account, so your credentials will probably work fine over at the registered user's page. If not, you'll have to contact ProFantasy support to fix that.

Note that of course, there is always a chance that your installation is messed up, but in 99% of cases, it is only a map issue (map set up to use wrong style, or style have been manually changed, or map style simply doesn't have those tools) rather than something being wrong with the CC3+ install.

Note that newer products won't neccessarily say this at all, because they are ONLY compatible with CC3+, and nothing else. Every ProFantasy product have been compatible with CC3+ for several years now. However, if you own some very old products from the CC2-era, some of them require a paid upgrade to the new version, but since you said you got the CC3+ bundle deal, everything in that bundle would have been compatible from day 1.

For trace to work, you need to be using a drawing tool, not one of the basic shapes from the right hand toolbars, and you need to place down the first node before you can proceed with the trace. There are some types of drawing tools that don't support trace, but all standard straight/smooth/fractal tools should have the trace option.

You can also check out DogTag's trace tutorial video or my command of the week article.

Looked back in time a bit, and found that the references to those files are found in the official DD3 template for CC3. I don't have the actual image files there either, so I don't believe they were never part of the intended install, just leftover references.

The templates for DD3 for CC3+ have been cleaned up, and don't have those references anymore.

Not easily. While I guess technically CC3+ has all the tools required to accomplish this, this isn't a normal workflow the program is made to do, and hence, would have to be done manually, there are no quick shortcuts.

You can use modifiers like endpoint when moving the section to position it precisely, but once it is in place, you need to deal with all those contours. I assume you wish to have them as continuous contours, which means you need to reduce those polys to lines, chop out the pieces you don't need, and join them together again. Not even sure if Combine Paths will be happy with those contours with a huge number of nodes. As an alternative to chopping and cluing together, you could instead use the trace functionality of a drawing tool, and basically create a new contour by tracing the outlines of the pieces that forms the contour crossing the map pieces. This may be simpler. But no matter the method, each contour must be done individually.

Unfortunately, it is very difficult to stop single spammers posting a single post. As long as a physical human being is willing to spend the time and register manually on the forum, it is impossible to stop them without also be very hostile to legitimate newbies.

The forum is utilizing public spam lists to avoid those people jumping from forum to forum to register and spam, and it also have rate limits to prevent a spammer from doing things like filling the front page with spam (using manual or automated means), as well as edit limits to prevent the classic "post a generic but not spam post, and then go back and edit it after moderators have read the original post and moved on" but the single individual posts will continue to appear, and we remove them as soon as we notice. As already mention, use the Flag link in the post to report it.