It is a bit easier than those old instructions. You don't have to edit the XML file anymore, and you can dump the 64-bit binaries into the ImageMagick64 folder (You must create this) instead of replacing the 32-bit one in the ImageMagick folder. Make sure you get a version of ImageMagick that contains the convert.exe executable though, this is going away in newer versions, but CC3+ expects this file and it's command line arguments.

The most important (and easiest) thing of the two is Sue's trick though, as this allows CC3+ to export much larger chunks of the map at a time, both making rendering faster, and reducing the amount of potential effect artifacts that happens due to splitting up the export in sections.

The easiest way to accomplish this is to first draw the hex grid, then move the origin to the center of one of your hexes after drawing the grid. The snap grid from the hexes will allow you to place the origin perfectly in the center of a hex.

After doing this, the snap grid will be off, but just right click the grid button, and edit the "User Hexgrid" and set the grid offset to 0,0.

Note that when doing this, the origin will only be in the absolute center of the map if your map size was set up to be a proper even multiple of hexes height and odd multiple of hexes wide, otherwise, it will be pretty close to the center, but in any case, it will be in the correct center of a hex.

The issue lies in the way Windows determines the space used. Because all the add-ons are installed to the same directory, it basically ends up counting most of it for each add-on as it can't separate what belongs to each.

It is similar to your steam installation in the same image taking up 116 Gigs. Obviously, steam doesn't take that much, but Windows things the installed games are part of the installation.

You're not going to reclaim all that much by uninstalling the CC3+ add-ons. If you uninstall everything, you'll get back that ~40GB once, but not for each add-on.

Unfortunately, the Microsoft Print to PDF printer driver is pretty basic, so you can't control much when using that one.

But the general way to make thing the correct size for print is to rely on scaling, not margins. In the print dialog, switch to scale factor instead of fir to page, and make sure scaling is correctly set up. If your drawing is properly scaled from the outset, you should be able to calculate this rather easily, but if not, it may require some trial and error. You can also use the Distance command from the info menu to measure distances in your map, such as the width, to properly calculate the scale needed.

Obviously also set the tiling option to the desired value, adding overlap if desired.

This should ensure that your drawing end up the right size in the PDF, and you should then be able to print the document from the pdf using the the documents internal margins without the printer adding any more. You might need to print it with pdf software that allows more control over the printing process so that the scale of the document can be kept intact, like adobe reader to do that, I am not sure the built in pdf-viewer in windows handles that properly.

A symbol definition isn't really all that complicated. You have the symbol definition entity with the basic properties, and that entity contains a sublist with regular CC3+ entities that make up the symbol.

A raster symbol is basically just the same as a vector symbol, the difference is that it usually only contains a single picture entity that reference the png image. I don't have all the flags in my head, but there are some flags to set to indicate that the picture refers to a proper 4-resolution image (which is preferred over using a just a single image for the symbol)

And yea, a symbol catalog is just a regular drawing where the drawing list is filled by symbol definitions.

Personally, I would probably have done it as an XP to take advantage of the features provided, but also as a way to gain familiarity with the toolkit.

You are probably looking at quite a bit of work to assemble all the pieces though, and considering how easy it is to copy symbols between symbol catalogs and build your own from inside CC3+, i don't know if it is worth the effort.