That means you are picking the polygon in the wrong spot when you pick the polygon to trace. The spot you use to pick it is very important, as the trace line will always go through that point, so it needs to be on the section you intend to trace.

More here.

That's a consequence of using the drawing tools from the "wrong" style. Did you start this as a Mike Schley overland map in the first place?

See this FAQ entry for how to import the missing fills.

Also note that the trick by clicking the :CC2SYMICOND: button only works if you have started a map in the appropriate style (i.e CC3 Mike Schley Overland or SS4 Dungeons of Schley styles). Otherwise you will need to load them manually as JulianDracos describes.

If you want to keep the temporary files (the tiles) when using the large exports annual scripts, you can just comment out the line that deletes them from the @Annual\Issue 129 - Large Exports\tile.cmd script:

DEL /q tile*.png

(This line appears two places in the script due to branching paths)

Do remember that this also means you need to manually clean them out before doing the next export however, or the stitching process will get confused.

And if you just want the tiles generated, and not stitch them together at all, you can comment out the two lines in the script starting with magick mogrify and magick montage.

And yea, you do absolutely need to use png when working with large images, as stated above, jpg cannot do these image sizes. But if you just export things as tiles from CC3+, you could switch that export to jpg to get jpg files instead of png tiles, since each tile is small enough, it's only when stitched together it becomes too large.

In the final deep zoom images I have made for the atlas (like Sanctuary) I exported as png from CC3+, but the final tiles used by the deep zoom script itself are jpg images as this gives much better performance due to smaller file sizes.

I would say that's completely optional. According to Scott's description, those are "deep underground". They're also continent-scale, so his map isn't at a detail level that would show any potential dungeon levels, so if you want a connection, it could be as simple as putting a trapdoor/hidden stair in any room and saying it leads to a long tunnel going down to the Darklands, or as you mention, just describing one of your chasms as being really deep....

The effect employed here require it to be a polygon, you can't do the same with a line.

One way to handle this is to just let the poly extend beyond the border of the map. The part sticking out will be hidden by the map border and the screen. The end result should be that it looks like a line.

I have a couple of videos on creating symbol catalogs which may help:

vthumb(dRRa6ctWPJY|Creating Symbols - Part 1 - Finding and Preparing Images)

vthumb(cYxAIPa7dak|Creating Symbols - Part 2 - Creating a Symbol Catalog)

You're using the wrong version of the installer. The one you are using is the one for CC3, not for CC3+ which is what you have. You'll find the right one on your registered user download pages.

Not sure why you're referencing DRM here though, a technical issue like this doesn't have anything to do with DRM. This is just a compatibility issue where CC3 add-ons can't be used with CC3+ and vice versa, not a protection scheme.

Wooden walls are unfortunately somewhat lacking in Base DD3. There is the 'Woodgrain Bitmap' fill, but it is not the best.

There are some wood wall fills in the free Jonathan Roberts dungeon annual, showing the tops of standing beams, which may or may not be what you need.. There are also fills appropriate for wooden walls in Symbol Set 2 and Symbol Set 4.

You'll have to :CC2EXPLODE: the symbol, that gives you access to the individual parts of it.