Hi Hadrian, good to see you.

You shouldn't let atlas maps holding you back. Those are for working on when you have the time and desire (and computer that agree with you) to do so, they're not a requirement. I'd rather see people without maps, than no people at all :)

Just do it whenever you have the time. I'll just add them to the atlas whenever I have the time after receiving them.

Make sure the names of the descriptive text files match the name of the map files.

From your screenshot it looks to me like when you are loading the symbol catalog, you are going into the artwork folder itself, picking an image and hitting OK instead of loading the .FSC file in the parent directory.

The reason this is important is that all such settings are store in the symbol catalog file (the .fsc). Going into the artwork folder and picking an image is an alternate way of getting the images into the symbol catalog window that is best suited for when you have a folder full of artwork that has NOT been made for CC3+, i.e. it doesn't come with a symbol catalog file. But loading it this way just loads them as "dumb" images, nothing of the smartness of the CC3+ symbols will come with.

So for any official or properly prepared CC3+ symbols, always load it through the symbol catalog file, not the artwork folder.

Yes, you have to go through :ICON_CATALOG: to open it if it doesn't show up in the list of catalog settings, but once you click that button and get the Symbol Catalog dialog, you have two options, either find the .FSC file for the catalog (@Symbols\Cities\SS6\MS Color\SS6C_Ruins.FSC) and open that, which is the right approach and loads the actual catalog with all the symbol behavior, OR navigate all the way into the artwork directory (@Symbols\Cities\SS6\MS Color\Ruins) pick an image file, and hit ok, which is the non-optimal way, as it will just populate the symbol catalog window with the images in the folder without any symbol behavior like grouping, because all that is stored int he symbol catalog file.

Yes. Well, CC2 files actually, but they are fully compatible with CC3.

Does it look like this inside CC3+, or only on the exported image.

If the latter, try this

I also noticed that there doesn't seem to be a light source located in the torch in question, while the torch north for it, as well as the one on the south wall both have 2 light sources in each. (Use Dungeon - Lights -> Show light symbols to visually see their location)

Finally got these atlasified. Thanks for the contribution @JimP

Are all the folders in the proper locations? Those blank entries in the latest screenshot of yours is typical indication of symbol catalogs not being where they are supposed to be. Basically, the config in CC3 says that a catalog should exist, but the actual catalog file is not found.

For example, that top catalog file in the screenshot is expected to be found at

@Symbols\Medieval Symbols\Artisan Buildings Wooden Shingle.FSC

(Remember that @ represents the location of your CC3+ data directory, so with a default CC3+ install, this would be c:\ProgramData\ProFantasy\CC3Plus\Symbols\Medieval Symbols\Artisan Buildings Wooden Shingle.FSC)

If there are any differences at all here (such as an extra folder in the middle or that path, or a missing folder) it indicates that things are not where they are supposed to be, and something has gone wrong at some point.

@ is the standard CC3+ reference to the CC3+ data directory, the default location unless you changed it during installation is c:\ProgramData\ProFantasy\CC3Plus

System is a folder within the data directory.

Just changing the number on the top doesn't work unfortunately, as the code that created the import explicitly sets a color for every border, and it uses 15 if it gets (what it considers) an invalid color from travellermap.

What you need to change are the color values:

#COLORS
#======
color names = red:2|blue:9|olivedrab:12|orange:8|yellow:4|purple:7|green:13|lightgreen:1|lightblue:9|pink:187|brown:11|cyan:5|hotpink:6|lime:118|darkred:165|darkkhaki:130|gray:14|slategray:67|darkslategray:66|white:15|indigo:58

This section is also what makes Darian and Sword Worlds the same color. Travellermap sends color blue for one of them and lightblue for the other, and if you look at the config, those are both set to be color 9.

You can also get it to use those html colors just by inserting them into the list, like I did here, this should cause the white sections on Spineward Marches to come out as yellow:

color names = red:2|#e32736:135|blue:9|olivedrab:12|orange:8|yellow:4|purple:7|green:13|lightgreen:1|lightblue:9|pink:187|brown:11|cyan:5|hotpink:6|lime:118|darkred:165|darkkhaki:130|gray:14|slategray:67|darkslategray:66|white:15|indigo:58

The way we handle these colors was written before travellermap started putting those html color codes in there, so I am afraid this is a manual process for now to identify and insert appropriate replacement, the importer would need an update to be able to parse those automatically. Personally, I would probably just do some quick manual color changes on those entities after loading the map. While having everything correct out of the gate is obviously preferable, the main work is in drawing the sectors after all.

Also note one thing about the import dialog. It caches the setting sin memory when you load the file, so if you make tweaks to the config file with CC3+ open and want to test the new settings, you need to click the change export settings button and browse for the file again, even if the dialog indicates it is already the right file.