Plus another 2-3 hours to create the cache, during which time there will be errors and everything will crash ...Wouldn't be surprised if the maintenance window extends an hour past that. Whatever FD is planning to do, it sounds really major.
Plus another 2-3 hours to create the cache, during which time there will be errors and everything will crash ...Wouldn't be surprised if the maintenance window extends an hour past that. Whatever FD is planning to do, it sounds really major.
You're optimistic. Most of the gamebreaking bugs have been here for over a year at this point, but Frontier would evidently rather push cosmetics, pre-built ships and more completely broken features (PP 2.0 was and still is a buggy mess - try giving us PP missions that are actually possible to complete instead of asking us to hack holograms in systems without stations with holograms) and ignore the playerbase when every single update they post they got roasted by the masses for leaving parts of their game completely unusable and broken while fixing the odd decal and asking us about ship and module transfer times as if anyone cares when you consider the bigger issues that need fixing. Quick list of the bigger ones that actually need attention:Don't forget today's update is based around the story arc and next Tuesday (10th) there's a bigger update which brings amongst other things including fixes the Cobra Mk V.
So if the bartender bug isn't fixed today, it could be next Tuesday when bartenders and other issues get fixed.
Plus another 2-3 hours to create the cache, during which time there will be errors and everything will crash ...
By the way yes, the destruction of Earth was not required in the future, when it becomes possible to land on planets, recreate real cities.i wander if there will be a cinematic...
Frontier: "How about another broken decal instead?"Any fixes for the myriad bugs we've raised? Even if just the one, please make carrier bartenders and Ody mats transfer work again. I beg you.
Honestly you should just expect them to ignore us asking for bug fixes at this point. "How dare they, the customer, ask for a functioning product. The nerve!" xDStill no progession blocking bug fixes? Really?!
No sorry, we need Frontier to see them, not be in a place where they can be conveniently ignored for the rest of the game's existence. The bug situation is dire and their lack of communcation or focus on fixing them is starting to feel like they are deliberately mocking their veteran players in favour of shoving microtransactions down the neck of every new player - who will by the way ineviatable end up complaining about the same game breaking / immersion shattering bugs we are.Seriously, the constant whining about bugfixes is getting really tiresome. Can we concentrate on discussing about the game events? If you want to whine about lack of bugfixes, create a separate thread or something.
Here will do, thanks anywayThen create a thread about it. It's that simple.
Well, that's the thing, isn't it. Despite all these "gamebreaking" bugs, many of which have been there for months, there are more people active at the moment than there have been for a very long time. That server load isn't coming from the people who can't play the game right now because it's unplayable due to the bugs, or quit in disgust at the sight of the Mandalay's reversed thrust vectoring, or whatever.
- Long witchspace times due to increased server load since Update 19 that Frontier refuse to talk about or resolve.
To fix the technical debt they need to be ahead of the curve there and have the game in a point where everyone will quit if there's no new features for a few months.Frontier could have spent the last twelve months working on bugfixes rather than on Powerplay, engineering, SCO, Thargoids, new ships with graphics issues, etc.
And sure, there would have been a more polished game at the end of that, but still one which relatively few people were playing.
If waiting in witchspace for 3 minutes every jump is your thing, good for you buddy. Doesn't mean everyone else has to like it.'Long Witchspace jumps' aren't a bug - they're a feature. Previously when the servers were highly loaded it would just time out the jump and drop you out of the game with an error. Now it seems they added retries so that most often the jump succeeds, but juts take a bit longer. Which to me is far better.
Including 2 of mine, which are fully fuelled but left just over 10ly from Sol...If it works like previous Titan arrival rules anybody within a 20 light year radius of the Titan might find themselves kicked to the nearest rescue megaship (whichever one that may end up being). Because then, 15 light year distance was an immediate capture, and 20 was auto-invasions for any populated system within that range. I got my alt in a station at 29(.9)ly... in part because I slacked about actually moving my Thargoid-related things on it over there until 30 minutes before the maintenance window.
Supposedly there is one moving to Luyten's Star so the capture and invasion radius may be changed for this particular encounter, but we will have to see... there could also be an attacked or wrecked rescue megaship waiting for us instead.
If you would prefer to be dropped out of the game every time instead then make that case to fdev. Can't see you being the most popular for it though - certainly won't get my vote.If waiting in witchspace for 3 minutes every jump is your thing, good for you buddy. Doesn't mean everyone else has to like it.
That is actually still a bug. If an API or service is called and not responding before the request times out, it's a bug. For example because the code can't handle some data or load.'Long Witchspace jumps' aren't a bug - they're a feature. Previously when the servers were highly loaded it would just time out the jump and drop you out of the game with an error. Now it seems they added retries so that most often the jump succeeds, but juts take a bit longer. Which to me is far better.