Not signed in (Sign In)

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome Guest!
Want to take part in these discussions? If you have an account, sign in now.
If you don't have an account, apply for one now.
    • CommentAuthorovka
    • CommentTimeDec 8th 2017
     
    I upgraded my CC3 to CC3+ and have the latest patch (along with the latest CC3+ Cosmographer). I tried a Traveller sector import and have noticed something strange. Some of the underlying data formats might have changed (it's been a year or more since I last imported a Traveller sector) because I don't recall having this problem before. The Allegiance codes sheet and layer is pulling in the first two characters from the Ex field in the data, the travel zones are not being added, the gas giants are not being added, and the bases are not being added. There may be other oddities, but those are the ones that jump out at me.

    Cheers,

    Ovka
    • CommentAuthorovka
    • CommentTimeDec 29th 2017
     
    I finally got this figured out. I took the Example.cfg file provided in the System/Traveller directory and modified the first two lines at the top from

    msec source = http://www.travellermap.com/MSEC.aspx?sector
    sec source = http://www.travellermap.com/SEC.aspx?sector

    to

    msec source = https://travellermap.com/api/msec?type=MSEC§or=?sector
    sec source = https://travellermap.com/api/sec?type=SEC§or=?sector

    Now, as log as I select that configuration file when I import the data, it works as it should.

    Cheers,

    Baron Ovka
    •  
      CommentAuthorMonsen
    • CommentTimeDec 29th 2017
     
    Thanks. This will be usefull for later.
    • CommentAuthorovka
    • CommentTimeDec 29th 2017
     
    Well, I just checked with the owner of the TravellerMap site. He said his fresh install of cc3 doesn’t require any extra work. It’s just cc3+. I did notice that if the file I specified wasn’t available, cosmographer still found a file from the TravellerMap site (right sector, wrong file format). Perhaps the issue is error checking gone awry?

    Cheers,

    Baron Ovka