The reason I did all that is because that doesn't just bring the flat image into PM, but also the height data and surface normals for a better representation. You only strictly need the surface map if you don't have anything else (which would be the result from making it using wonderdraft as the video did), but it can look better with normals and height map, and since FT3 do have the ability to export these, I added them to take as much advantage of the FT3 - PM combo as possible.

As for your seas, I guess you exported that one from the Gaia view in FT3. It is designed to be a simple pretty view, but it isn't configurable at all. Try basing the export on the altitude view or the texture climate instead. I believe that will give you better results.

What happens here is that CC3+'s drawing tools are set to stop at the map border, and the map border itself is identified by entities on the MAP BORDER layer. What has happened here is that you have somehow gotten some extra entities on that layer, which basically redefines the map border.

Open up the layers dialog by clicking on the L: indicator in the status bar. Hide all layers except MAP BORDER. It should now be quite obvious which entities do not belong here. The map border itself should normally just be a thin outline around your map, there shouldn't be anything in the middle. Now either :CC2ERASE: the offending entities, or just use :CC2MCHANGE: to move them to another layer.

Not too fond of how the text glow visually looks more of a blob behind the text rather than an outline of the text. I suggest reducing the blur radius, or switching to the Outer Glow effect instead.

I don't think there any videos out there for creating starmaps with Cosmographer.

There's not any tool that will populate the map randomly with systems, you'll have to do that manually.

My most important tip for new users is to make sure to understand the program properly before jumping into a large-ish custom project. As you said, it can be a bit overwhelming at first, so if you haven't done so already, I highly recommend working through the basic tutorials in the user manual, even if they aren't about space and sci-fi.

That list shows the fill available in the current map. If you want fills from another style you need to import them into the map first, then they will be available to pick from that dialog.

None of the tools do that automatically as far as I know. You'll need to manually place each node. Turn on Snap and it should be real easy to place the nodes precisely.

When CC3+ renders a map to an image, it does so in sections. It does this because there usually isn't enough memory to calculate the entire image in one go. This value controls how many pixels each such pass should contain. The default value is on the lowish side when it comes to modern computers, so increasing it allows us to export the drawings in fewer passes, and the issue you were having usually occurs on the edge of each pass.

Once you've entered this command, it is the new default until you set a new value, it is not a per-map setting. And it is a good setting for everyone to use unless you have an old computer with very little memory (below 8 gigs)

I don't see any reason why they have to be 10' wide, unless they at some time had to be widened to that point to bring large objects through. In the real world, quite a lot of underground passages are narrow things, not even 5'.

No, trace won't work on entities on frozen layers