Note that you can always export the climate view from FT3+ to CC3+ just by going to File -> Save Campaign Cartographer file. There is an export setting there, Legacy Climate Only that will export the climate view, or you can make your own.

But it won't look identical to what you see in FT3+. FT3+ and CC3+ are two different programs that have different ways of doing things, the idea with the export functions is to get the actual data across so you can customize it in CC3+, not the exact visual look.

The master filter is loaded in the OnOpenMacro map note in each individual map. (The SYMICONFLOAD command)

1. If it is a vector symbol, referencing no external image file, then yes, it will be contained entirely within the .fcw file. If it uses any kind of images, either an image for the symbol itself, or a raster fill, then it will be dependent on that image.
2. For a pure vector symbol, yes, no problem at all. Additionally, if it do reference fill styles, but those fill styles are official CC3+ fills (including addons), then yes as well. Problem is only if you have brought in your own custom image to use for the fill.

Trim does this when operating on splines. The reason is that the shape of the spline is dependent on the positions of the nodes, including the following nodes, so if you simply cut it and placed a node at the end, the shape would change.

Since CC3+ is a CAD program, having the rest of the shape change shape isn't really acceptable, so instead when you trim a spline, it just hides the rest of the shape instead of removing the nodes from the entity.

There are three entities in your map that is causing problems. Not sure how they occurred, but if you erase them, the zooming problem should go away.

These are entity numbers 114189, 114190, 115004

To erase an entity by it,s number, click :CC2ERASE: then right click inside the drawing area and from the selection pop-up, select more -> Entity Tag #. The command prompt should then show a Tag #: prompt. Type in one of the entity numbers from my list above and hit enter. If you did this correctly, the command prompt should show that you have one entity selected. Now, right click again and select Do It. Repeat for the remaining two entity numbers.

Grids (and thin lines in general) are problematic when exported to an image.

The reason for this is that a grid line may be for example 1.7 pixels wide in the final export. Well, an image can only use whole pixels, so it will either be 1 pixel or 2 pixels wide. Some people may then think "easy, 1.7 obviously rounds up to 2, where is the problem?".

Well, the problem here is that if you round up all the grid lines, these pixels add up. If your map have 20 grid lines vertically, and each takes 0.3 pixels more than they should, then there are other parts of the map loosing out because there are 6 pixels that actually belong to other elements. (And while 6 pixels seems low, remember that everything in the image fights for space, it is just that the grid lines are more visible here, but the image sizing algorithm have to deal with everything).

Let us just for the sake of example try to export 5 touching parallel lines of different colors to a 8 pixel wide image. Evenly divided, each line should then be 1.6 pixels wide, right? But if we round it to 2 pixels, we really only have space for 4 lines, there won't be any pixels left for the last one. Obviously, rounding up isn't going to work. Rounding down? No, not really, with 1 pixel wide lines, we only fill the 5 first pixels of the 8 wide image, with 3 left over. The only possible way to do this is to make some lines 1 pixel wide, and others 2 pixels wide. So even if they were identical in CC3+, there are no way of doing that in the exported image as long as the export size doesn't happen to line up perfectly (For my 5 lines, both 5 pixels wide or 10 pixels wide would have worked perfectly). So this is really the problem the image exporter faces, and thus end up with different widths of the lines on the export. Image resizing algorithms tries to be as smart as possible to lessen this problem, but it is difficult to handle single thin lines.

Using a high level of anti-aliasing helps combat this, because it will merge the colors from nearby pixels, creating an illusion of lines and features that are not a full pixel wide.

These tools should work just as fine on Metric as Imperial overland maps.

I know they don't work as well in small-scale maps as large scale maps though. What is the size of those maps (the dimensions you entered in the new map wizard)?

Also, have you modified the symbol scale from the default value in the map?

In any case, if you are not happy with the distribution after running the tool, simply undo once, as this removes the trees but leaves behind the background polygon, then immediately run the Draw -> Symbols in Area command. This will bring up the dialog with the same setting the tool just used. Then modify the distances in the pattern section, hit ok, and pick the background poly you created with the tool. This will fill it with your new settings. If you still didn't quite like the result, undo once to remove the trees you just placed, and repeat. When you find a setting you like, you can save it (but I recommend NOT saving over the existing setting used by the tool, make your own)

That's a pretty good question. The earliest map I could find in my collection that I actually made and used for a game is dated 2005, but that was not the first time I used CC.

I think my first encounters was with the cut back version - Campaign Mapper - which shipped with the Core Rules 2.0 product back in 1999. I remember picking this up pretty early after it's release. I think I also got the FR Atlas around that time, probably around 2000.

Most of my early maps were simple modifications of the FR Atlas maps.

Nothing special about city maps, the special thing here is the building symbols. Symbols with shading maps (Like all proper CD3-style buildings) don't get redrawn at the end of the effects pass like other symbols do, this is to preserve the shading effects that have been applied to them I suppose. You can of course disable this behavior for all symbols with the DELAYDRAWSYM command.

Unfortunately, there isn't a selector for select by sheet, but you can select by layer by using SELBYL.

Unfortunately, that option is not straight forward when used in drawing tools, because when you select by layer, you select everything on that layer, including previously drawn entities.

I guess the best option to handle that is to have the drawing tools set up to draw on a temporary layer that is kept empty, and then you can select the entities just placed on it, do the required manipulation, and then finish off with a Change layer (CHANGEL) command to move everything to the real layer.

Unfortunately, no. You'll have to use polys for everything you need aligned fills with.