When I try to work out where the problem lies, I often use a series of elimination step. Start by hiding half the sheets and testing, until I have narrowed down which sheet it is on, then do the same for the layers involved on that sheet. Then I start eliminating the entities on the sheet, half at a time.

Often, you can use quicker export options when you narrow down a problem. For example, exporting to bmp skips most of the final conversion step, and you can usually export at a lower resolution and turn off things like antialiasing, or even export without effects on. Just test with reduced export settings first to see if it still crashes, sometimes the conditions are no longer fulfilled for the crash when you do that, but if it still does, then it is no need spending 10 mins on each elimination step when you can spend 30 secs.

As for turning off progressive jpg, I have no idea whatsoever why that would help with anything. That option is used in the final conversion step, i.e. AFTER CC3+ have rendered everything, and have a complete bitmap to convert to jpg, while for me at least, it crashed during the actual rendering step long before that option can affect anything.

I seem to be able to reliably crash it. Did some testing, and seems to be down to building 20. It is right outside the area, but to avoid weird effect clipping at the edges, the render works with a slightly larger area than you select for the export.

Delete the building, and the export should go through. (You'll probably want to redraw it of course, but it is good just testing export once before that to make sure the problem is gone for you)

These lines happens because nodes are placed in such a way that you get very sharp angles on wide lines. There are two main things that can be done:

• Use the SIMPLIFY command. This command removes nodes that are too close together, and might fix the problem. One needs to experiment a bit with the simplification distance to find the best value, as this depends on map size. For larger maps, it may be 1 or more, but for smaller maps, it may just be a small fraction. Save your map before experimenting so you can easily go back to a previous version (Undo also works)
• Stop using entities with a separate outline entity, and use effects instead. Since this problem is connected to wide lines, it doesn't affect the landmass itself, only the outline that has been applied. For example, on the Mike Schley overland, this outline is on the COASTLINE sheet. Hide this sheet, and apply an outer glow to the land instead.

That's generally a good approach. The most important for people reading your story is to identify the places they read about on the map. Then you can expand on it later with more names if you write more stories set in that location.

The ".png.bmp" filename is part of the process. If you see a file with this ending, it basically just means the export crashed halfway through.

Basically, what happens is that CC3+ needs to render the entire map before it can be converted to png, it cannot simply be exported straight to png or jpg, and the native format of windows is BMP. So what it does is that it always exports the file to .bmp first (this is the map.png.bmp file), and then at the end converts it to png (or jpeg) which results in a new file, map.png, and then the original bitmap file (map.png.bmp) is deleted. But if this file is still around, it usually means CC3+ crashed during the export so it never got to the conversion and deletion steps.

Do the crash only happens when you go up to 9000x9000? I see you mention 6000x6000 being to small, so I assume that one actually exported?