Incidentally...

Is it crashing after the passes are done and during the processing of the final image from bmp to png? If it is then the sheer size of the resulting png file may actually be the problem. Try for a JPG instead.

The Rendering engine can't manage the whole job in one go when the export is large, so it divides the map into passes - horizontal strips starting at the top of the map. The smaller your MPPP is the narrower those bands will be, and the longer it will take to render the whole map. The current default of 4 million pixels was set a while back when machines were smaller, so for most people increasing the size by a factor of 10 is a reasonable thing to do. The fewer passes the rendering engine has to do the faster the job is done.

I'm very used to waiting a minute or two for my 5000 px exports with 33% antialiasing (6666 x 6666 work size), but I have my MPPP set to 20 million instead of 40 million right at the moment, so it takes 2 passes to do that size. There's no way a render should take hours.

A number of hours?

Not really appropriate for this problem and right now, but for other maps to speed up the process type EXPORTSETMPPP and hit enter. Check your Maximum Pixels Per Pass in the command line. If its only 4 million type "40000000" (40 million) and hit enter.

Unfortunately, I don't have CSUAC so I can't do a proper actual test on the map, but maybe someone else can try?

How does it render if you drop the antialiasing to 15%, or whatever number you need to drop it to in order to reduce that work size to fractionally under 10,000px each way?

Other things you can do to help include clearing the cache before you export and exporting straight away before you pan or zoom at all. You get to the cache by clicking the Display Speed button|CC2RESMODE|. Just hit the Clear bitmap cache button. My map is only using 63 MB at the moment, but yours may be a lot closer to the limit.

Another option is to render it as JPG rather than PNG, and/or to render it in quarters using the Rectangular Section exports then stitch it together in GIMP or another bitmap editor. This export in parts idea is easier if you have a small overlap on each quarter of the map.

What size are you trying to export?

The critical number in any export isn't the size you set in the px hieght and width but the work size, which is a pair of numbers at the bottom right of the Options box. If both are significantly over 10,000 px you may have to reduce antialiasing quite a bit to bring them under that number.

When it crashes what do you mean? Does CC3 crash to desktop, or does the process just stop and not finish?

Would you be willing to upload the FCW here so that we can have a go at exporting it?

You're welcome, EdE :)

I think the numbers that really matter are the work size dimensions. Antialiasing requires that the image is exported a lot larger in the first place to a BMP file, which is then reduced to the specified size to antialiase the image.

If the render is very slow try increasing your Maximum Pixels Per Pass to 40 million rather than 4 million.

The command for that is EXPORTSETMPPP. The default value is '4000000' if you check the command line. Input '40000000' and hit return, then try again.