Yea, that's DELAYDRAWSYM.

That setting is system-specific and not map-specific, so it won't be automatically turned on when people load the map unless is it is added to the map loading macro.

I wrote a tool for that: http://cc.monsen.cc/tools/cc3monsentools.html

All those unknowns means your image database file is out of date. I just updated the one on the site, if you download the zip file again and put the xml file from it into your CC3+ data directory, overwriting the one there, it should identify the rest of those files too....

I think that's because those images are using the wrong relative reference. They are using the #-reference, which means the CC3+ installation directory, instead of the @-reference which means the CC3+ data directory.

Try running the FFIX command first before running my command again.

AA in itself can't really be the issue. All turning on AA does is making CC3+ export a slightly larger image than requested, so the imagemagick processing after export can generate AA by reducing it down to the requested size.

Now, what I did notice is that when I export at 5000x5000, it is completed in a single pass, but if I bump it to 33% antialias, the resulting size increase leads to a 2-pass operation. Is that what you see as well?

My suspicion is that something weird is happening with the color key with that gigantic entity, but in this case, because turning on antialias forced it to become two-pass, it became divided over two smaller ones instead which was then handled correctly.

Also make sure you have a proper hex snap grid selected (Right click the Grid button in the lower right). Having the right hex grid snapping active is what triggers the automatic resizing to fit the grid. Not that if you had a symbol on your cursor when setting the snap grid, you need to pick up a new symbol from the symbol catalog to trigger the sizing.

Not sure what would cause the numbering. I am unable to reproduce that behavior myself. Note that it will only put numbers in fully complete hexes, so the rightmost row is expected to not have labels, even if they are mostly complete, they are not fully complete, and that is what CC3+ looks for. But I am honestly not sure why the A00 label is missing; from the other labels is clear that CC3+ sees that there is a hex there. On all my own tests, that one appear just fine. Could you post the .fcw file you are using where you experience this issue?

As for the missing line in the top left, I notice that sometimes happen if the hex is incomplete, as in your example there, it is missing the rightmost edge node where that line should end. Not sure why/when this happens, but since it is just a single line, the quickest fix is probably just to put it in my hand, just place a line on the same sheet and layer as the existing grid lines. The grid is really just a series of lines anyway. The same is probably the easiest fix for the numbering as well, just copy one of the existing number labels into place and use :CC2EDIT: to change the text. This also allow you to manually add labels to those incomplete hexes as well if you want. Keep in mind that the grid is normally grouped by default, but you can temporary unlock groups with the "Locked" button in the lower right of the GUI and temporarily unfreeze the HEX/SQUARE grid layer from the layers dialog so you can work with it.

@Ricko I have processed most of these but I was unable to process the Saquare and Cenotes maps due to the maps being attached to here being incomplete unfinished versions. Could you upload the finished versions for these?

Just type the numbers ate the command line instead of clicking with the mouse.

For example, if your map is 200 by 200 map units and you wish to export in 4 parts, simply do four rectangular section exports, and when CC3+ asks for the corner, type in 0,0 and 100,100 for the first 0ne, 0,100 and 100,200 for the second one and so on.

If you prefer to use the mouse, you can also set up an appropriately sized snap grid where each snap division is the size of the section to export. You can set up snap grids by right clicking the Snap button in the lower right.

Or, you can use my tile export macro from Annual issue 129.