For that map, line widths less than 1 seem to be a bit to small to be visible, especially when zoomed all the way out. Using effects like that is a fine way to make lines more visible, or you could bump the line size a bit. I am guessing that doubling the size of the rivers should be fine.

Sorry to hear you have so much troubles, but hopefully you'll manage to sort it out.

When you say wiped 40% of your map, make sure to check out things like sheets and sheet order. You may end up with something on an unexpected sheet after ungrouping, which means things may just be hiding out under something, like below instead of above your landmass or other terrain.

This is an issue with the old FT3 that is fixed in the newer FT 3.5.

The issue is that FT3 saves its settings in the program directory, which windows only allows if you run the program as administrator (Right click the shortcut -> Run as administrator)

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.

It does. It is easy to see where the problem lies though. If it crashes while converting the final file, you'll be left with a fully functional temporary bitmap (the filename.bmp.jpg file) that contains the complete export, and if you looked at the export dialog during export, you'll also see that it is done with all the passes over the sheets.

On the other hand, if it crashes while CC3+ is rendering, the temprary bitmap will be corrupted (probably look like a half-finished export), and you'll also notice that the crash happened at the middle of rendering a sheet if you were looking at the export dialog.

ImageMagick is smart enough to use the disk as a cache if needed though, so even the 32-bit version should normally be able to handle any size output CC3+ is capable of producing.

In that case, I suggest you contact technical support, they'll hopefully sort you out.

You find the support from by logging into your registered user pages and going to the support tab.

Me neither.

I think it is time you send in a tech support request so Ralf can look a bit closer at this, seems to be a weird problem here. You can reference to this thread in the request.

If the poly is filled or not is determined by the line width. If the line width is 0, you get a filled shape, but if the line width is greater than zero, you get an outline of that specified width.

As for being on top of everything else, there are two things to keep in mind

• Layers, doesn't control ordering, sheets do. So it doesn't matter what layer you put it on, you need to put it on the appropriate sheet
• When drawing something, it will always appear on top of everything immediately upon drawing it. It finds it's correct place in the drawing order the next time the map is redrawn (redraw command, zooming, scrolling will all cause that)

Everything that overlaps itself in CC3+ causes that effect. It is a result from calculating what is on the outside (not to be filled) and what is on the inside (to be filled) of the shape.

The solution to that problem is always to ensure a line or poly doesn't overlap itself. If you need to have an overlap, then split the line into two separate lines. If split along an edge and not in a corner, you wont' visually see it is two different lines.

Any entity can be moved with the :CC2MOVE: command [MOV]. (For pure command line options, non-visual move may also be appropriate [MOVE]).

Important thing when moving a landmass with stuff on it is obviously to select everything. If you just select the landmass, you'll only move the landmass, not the terrain and symbols, so you normally need to do a selection window to grab the right bits, but an alternative could be to hide all the sheets containing stuff you don't want to move (or better, but more complicated, freeze all the layers containing stuff you don't want to move) and then just select everything with the All (a) selection and move it.

To be able to move something, it is important that it is not on a frozen layer. If you are unable to move something in particular, check what layer it is on with the LIST command, and see if that layer is frozen.