Been trying to start a system colonization but it always stops after I deploy the beacon it says contacting megaship but no countdown is given and no ship ever shows up. When exiting out the game and relogging it wants me to deploy another beacon but again no ship ever shows up. On the system map it shows me as the system architect and all the places I can build stuff at and whatnot but no megaship. Submitted a ticket already just wondering if others are running into this issue. o7
Is the colonization system bugging out or something?
- Thread starter Kenpachi85
- Start date
At peak hours on the first saturday after the update, the servers will be getting absolutely hammered right now. I'm like three trips away from completing my outpost and I'm deliberately leaving it until the slow hours before I log on again and finish it.
I think the answer to the question "Is the colonization system bugging out or something?" is basically yes.
(You've perhaps seen people posting about having started to build a station and then the game decides they don't own the system any more?)
It's a new feature, it has some teething problems, but most of all: players are swarming all over it and the servers in general, so everything is slow and a tad flaky (including FC jumps).
For that reason, I have no intention of even trying it for a few more weeks, when perhaps the dust will have settled, the server load will have stabilised, and the most obvious emerging bugs will have been corrected.
(You've perhaps seen people posting about having started to build a station and then the game decides they don't own the system any more?)
It's a new feature, it has some teething problems, but most of all: players are swarming all over it and the servers in general, so everything is slow and a tad flaky (including FC jumps).
For that reason, I have no intention of even trying it for a few more weeks, when perhaps the dust will have settled, the server load will have stabilised, and the most obvious emerging bugs will have been corrected.
I already posted the same in another thread, but a bit of repetition won't hurt: The dreaded steam charts showed over 12.000 concurrent players 40 minutes ago, and that is just steam. That's crazy numbers for a dead game
. So yeah, the server hamsters probably have to do some overtime.Yeah I'm starting to think somebody else might be trying to make a claim on it too and the server doesn't know what to do or something. Things are probably just too busy atm like you say
Yeah I think your right I might just logoff for now and go play some 7d2d or KCD2 for a week or two and see if things calm down and it lets me do anything. Thanks for the replies cmdrs o7
Last edited:
Was bored and ending up giving it another go after abandoning the first system and was able to get everything to work right and the colonization ship spawned in. The second system is one I have a bit of history with too having used it for raw mat grinding in my early days so honestly happy things went down like this in the end. Have been in a mental funk not really wanting to play anything else so glad I have something to do in this game again dusting off my cargo cutter and getting to work on a t2 coriolis. o7 cmdrs
I've bumped into the same problem... I have a day off today, and planned to spend it hauling. Guess not :/
They are looking into the colonization system contacts and likely the whole system atm might be a good idea to put things off for a day or two. When I had this issue moving to a different system and trying again seemed to work though I couldn't cancel the first and had to wait for it to expire.
Been around this block for 7yrs this is a massive update as far as this game goes and things will undoubtedly need to be ironed out as we go. From what I can see from talking to frontier support they are working hard to get things up to speed. o7
Yeah, I get that... I'm not angry at frontier, this game is a complex beast. But I could resist the joy of trying out the new system, especially since a lot of star systems were being colonised so rapidly. Supposedly the today's update fixed it. Gonna find out soon.