Yea, I meant fixed. That's what happen when you type from memory.

The memory cache keeps bitmap images in memory instead of reading them from disk, which makes the loading faster. The -1 default size automatically allocates half the available memory, although I am uncertain if this is half of the max memory CC3+ can address [4GB] or half the system memory, I need to ask the developer about that. If the former, then you could potentially get some performance by increasing it above 2GB, but that really only helps if CC3+ needs that much memory (see the currently in use value). Increasing it if CC3+ doesn't need it won't help with anything.

To force the highest quality (Not normally required) just click :CC2RESMODE: and set it to Manual - Very High

That would be the Like modifer (F2). Just press F2 after selecting select by color (or fill style or line style, etc) and CC3+ should ask you to pick an entity to take the property from.

What is your anti aliasing settings? These affect max export size in a big way.

My standard export size for the community atlas maps is 8192 pixels in the largest dimension, with 25% antialiasing which normally gives me no trouble at all.

In any case, a way to export maps beyond your capabilities is to export them in tiles instead of the whole thing at once.

And yes, running out of memory in this context is running out of the 4gb it can address.

The SYMBOL DEFINITION layer is where all the symbol definitions live. When this layer is hidden, all symbols in the map gets hidden.

What you see on the BATTLES layer is the symbol references, that point to the definition on that layer.