I assume you mean "programdata" here and not "programfiles", as I can clearly see references to c:\programdata in your original screenshots.

You can't split your data directory like that. If you picked d:\ProFantasy as your directory during install, that's fine, but then you'll need to stick to it and keep putting everything there. CC3+ won't recognice the programdata directory in that case (it can only have one data directory), so anything you put there will be guaranteed to make red X'es, because all the templates and symbol catalogs refer to your data directory (which is d:\ProFantasy for you)

It depends.

But TRACED can be an excellent option here. You're probably ending up with a polygon that is easier to edit if using the "old way", since traced will need to place more nodes to approximate that rounding, and because TRACED runs on an image rendered from the entity, there can be artifacts like pixel steps. But you also often end up with a result that looks nicer.

CMB makes things into a single polygon, which cannot contain both smooth and straight elements, it has to be either a straight poly or a smooth one (I don't remember if CMB can work with smooth lines or not at all, but you can in any case convert the poly to smooth after finishing combining it.)

And no, you can't change the number of segments LTP creates unfortunately.

Yea, basically the same as I foun, just about any solid entity will work, but the entity have to be within view, so since exports are done in multiple passes, you won't necessarily need one line per symbol, but there must be one within view for each segment of the export.

One thing I didn't try yet, but which may work is just making that part of the symbol. A symbol can contain entities in addition to the image. Of course, those entities would be part of the symbol and get the same effects.

I've notified the developer, maybe he can give some more insight in exactly what is happening here.

The scale symbols are always made to be placed with scale factor 1.0, because it is important to get those absolutely correct, and using a factor of 1.0 makes the precision perfect.

Most other symbols are designed for an imperial scale, and are then simply scaled down when used in metric maps through the default symbol scale for the map.

Did you add that line of yours near those lights too? When exporting, CC3+ exports the map in sections, and it can't "see" what's outside the current section. I am guessing it is the same strange issue as above, and there isn't a "fix" in the section those lights happen to lie in.

Sounds like you are not running with the latest update. The hammer icon should supply four options (small, medium, large, x-large), the single option for just large icons was replaced a while ago now, along with fixes to make things work better on high resolution displays.

Remember, you should always (re-)install the update after installing add-ons.

You need to use one of the selection techniques described in the editing chapter in the manual to select just the fill and not the outline. I prefer to first select both entities by clicking on the edge, then combining it with NOT Color 0 to remove the outline from the selection, but you can also use list on the entities and find their entity tags, and then do a select by entity tag to just pick the fill.

There is a copy button in the effects dialog. Just highlight the effects to copy and hit it.

Welcome choppinIt.

Which format are these maps in? If they are just flat images, such as scans of the original WWII-era maps, I don't think there will be any good options other than hand tracing then.