Cosmographer Traveller Sector Import
Flyteach
Traveler
I have created a new sector. One can view it here on Traveller Map: https://forum.profantasy.com/discussion/12144/cosmographer-traveller-sector-import#latest
However, the colors for the various political systems are not showing properly when I import into CC3+. They are all showing as grey and they all run together. Is that because I used different color names in the sector metadata file that aren't in the config file? If I know the numbers/names I can redo the config or add to it, but I'm not sure where to start.
Thanks for any help!
Jim/Flyteach
Comments
Whoops, for some reason the link above isn't correct when I copied it. Here's the link to the Travellermap reference where the sector can be found: https://travellermap.com/?p=-4032.839!819.326!7.3&options=58359&mains=1
I am unsure why it is happening, but it does seem like it is a problem with translating the colors from the website into CC3+ colors, so they all end up at the default. I couldn't get it to behave myself, so I've asked those that knows more about this than me to look at it.
But, I did notice that if you use the "generate script file" option from the import dialog, you get a script file you can run to make the drawing. And the advantage here is that this is a text file you can edit. The first part of it is all the polys for the borders, and you'll noticed they are all prefixed by a COLOR 15 statement. You can then simply edit these, changing them to other color numbers, and then run the script file from inside CC3+ (Tools -> Macros -> Script File). You'll be editing a little blind since it is difficult to envision the look of the polygon from these candidates, but at least you can just keep the script file, tweak it, and re-run it....
In the config file for the traveller sector importer, there should be a "color names" section that should look something like this:
(that's the default string above). The entries are separated by the vertical bar characters and are name:value pairs. The name field is the exact color name (case-sensitive) that gets searched for and the value field is the exact color value string that gets presented to CC3+. If you change the color names, then the names from the sector definition file must exactly match (including case) the names in the color names config entry and each value must be a valid CC3+ color number ("0" through "255"). Any color name that's not in the list will use the color value "15", which is white.
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:
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:
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.
Thanks Joe and Remy! You guys are awesome and as always right there with help and I very much appreciate it.
I will check out trying to edit them, although I have also sent a note the the TravellerMap author to see what's going on with the API. Sometimes these things creep in and cause other problems, so figured he should be aware also.
Traveller support from ProFantasy is FANTASTIC and again, thank you very much!
Jim/Flyteach
And, to wrap this up, it's my fault. Joshua (TravellerMap) emailed me back almost immediately. It's because I do not have the allegiances defined. He pushed a change on his end, but it doesn't seem to resolve it completely (although some colors are coming across). So, my next step is to change tactics on the sector building and name the allegiances (not a big deal, but wasn't as high on my list) and get that update to Joshua so he can upload it. That SHOULD (tm) resolve it. I'll post back again when resolved. And, again, thanks to Joe and Remy for looking at this and providing someplace for me to work from.
Jim/Flyteach