Thanks. I am a bit behind unfortunately, you may have noticed I haven't been able to push out all the competition maps yet. I think these are first in Queue after the competition maps, but some of the competition maps have forced me to do other areas just to have the location they go.

It's not more maps that is is needed, but the fact that many competition maps were set on overland maps that were developed at the same time, meaning I had to also process those overland maps before I could process the competition maps, leading to a delay in processing competition maps due to extra work needed up front.

Now in the atlas. Thanks for the contribution @HelenAA

This is a very worthwhile point to keep in mind. The artist's permission isn't worth anything if their work is based on something someone else had copyright on. Goes for all creative work. I've seen way to many occurrences of people use illustrations based on copyrighted works because they got permissions from the artists, where the artist didn't have any rights to make/reproduce those illustrations. A few things can fall under fair use, but most of it not.

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.