Digging a bit, I found that transparency only works for images if they are set to use alpha transparency in CC3+.

Use the :CC2EDIT: on the image, and switch it to alpha transparency, and it should work fine. (remember to thaw that frozen layer first, otherwise you can't edit it)

Talking a bit with Joe here, it turns out that the problem is with the api from travellermap that we use with the importer.

If you look at the metadata for your sector, you see that travellermap simply do not give us a color for the sectors at all:

# Other
#
border 0107 0207 0307 0406 0506 0605 0606 0507 0407 0308 0208 0109 0108 0107

# Other
#
border 1821 1921 1920 1919 2019 2119 2219 2319 2418 2419 2420 2521 2522 2421 2322 2222 2123 2122 2021 1922 1821

# Other
#
border 1201 1302 1401 1501 1601 1701 1601 1502 1402 1303 1203 1202 1201

Normally, the color should be last on the the line for every border entry, and this is where the importer finds the color to use. And without travellermap providing us with a color, CC3+ defaults to white.

Here's an example of another sector which do provide colors correctly, notice the color names at the end of the border statements, after the coordinates:

# Plavian League
#
label 1814 Plavian League
border 1412 1512 1612 1712 1811 1911 2010 2011 2012 2113 2013 2014 2015 2016 2017 1918 1818 1718 1617 1616 1615 1614 1514 1413 1412 hotpink

# Renkard Union
#
label 3033 Renkard Union
border 3029 3129 3128 3227 3226 3227 3328 3329 3330 3331 3332 3333 3334 3335 3235 3135 3034 3033 3032 3031 3030 3029 red

# Swanfei Free Worlds
#
label 2721 Swanfei Free Worlds
border 2520 2619 2618 2718 2817 2918 2919 2920 2921 2821 2722 2621 2521 2520 white

I have no idea why travellermap doesn't give us the color for your sector, as there are clearly colors on the visible map.

Each sector is a polygon though, so it shouldn't be too time consuming to just change colors in CC3+ after the import.

The already selected sheet in the move to sheet dialog doesn't indicate what sheet the entities are already on, it indicates which sheet is the currently active working sheet. The only way to see what sheet something is on is by using the list command. (This goes for all the properties, the graphical dialogs shows the currently active "working" properties, not the ones from the selected entities.)

In addition to making sure the text is on the right sheet, it is also important that the glow effect you have is strong enough to actually be visible, a weak glow may be more or less invisible.

I prefer Maptools myself, but I have a weird setup as we do our gaming face to face, but uses Maptools for a digital battle mat instead of physical miniatures, but everything else (rules, dice rolls) are handled the traditional way.

Personally, I do enjoy the fact that it is NOT an online application, so we can run everything locally. No subscription fees, no limits to map sizes, full control. Bit more work to get started than just going to a webpage obviously, but for my use, it is great.

I run the server (in player mode) on the machine connected to the projector so it only displays what the players see (I use combined vision from all the player tokens, no individual view) and then run a client on my laptop in GM mode to control it. Players can connect to the server if they want to, or just use laser pointer to point on the screen to tell me to move their token. This is a great setup since I can update things secretly using the GM client (like adding enemies, or even add a completely new map) without any disruption to the player view while I work.

When you make a map in CC3+ and insert symbols and fills the proper way (i.e. use the provided symbol catalogs and drawing tools), the map will reference the CC3+ data directory. This means you can move the map wherever you want (even to another computer, as long as the products are installed) and it will still work (Even if the data directory is installed to another location on that other computer). The only important thing here is to NOT move around the art files inside the data directory, they need to stay where CC3+ put them

When you manually insert files, like a bitmap for tracing, it is usually either inserted with an absolute path, meaning if you later move the bitmap anywhere, the map won't find it and you get a red X, or a map-relative path, which means you need to keep it in the same relative location as your map (usually the same directory) and move both when you move one.

If an example map shows red X's, it is because it use stuff from a product you haven't installed.

You can always figure out where things are supposed to be by using the Info -> List command on the entity with the red X, or if it is a symbol, open symbol manager, find it in the list, and hit the list button.

More about file paths.