Game Discussions Star Citizen Discussion Thread v12

Just listening to Boredgamer (no, I don't know why either) on twitch and he's waxing lyrical about how he's looking forward to "taking over an unexplored system" and then fighting other orgs who come and try and take it off his org.

I'm sure this will happen. Yes indeed.

LOL, the guy is off his head.

However, he could i suppose fill a server with 50 of his org mates, then nobody would be able to fight them for it (not that there will be a mechanic allowing this).
 
Overall, the PTU feedback threads have had barely any contributions with how poor the 3.17 builds are

unknown.png
This is peak citizens.

No interest in anything apart from ships and food/drink.
 
I have a sneaking suspicion that the 3.17 builds are actually built on the 3.16 code they couldn't get to work back in December...the whole current 3.16 group of live patches is based on the ultra stable 3.15 code (the current live patch, 3.16.1 is actually 3.15.3), they only added some of 3.16's content onto the build. I think Ci¬G are still trying to get the 3.16 base code to work but once again, added certain content from the 3.17 branch to squeeze it in for the 3.17 dev cycle...Unfortunately, it's still broken...call it a hunch :whistle:
 
Last edited:
This is peak citizens.

No interest in anything apart from ships and food/drink.
There's no new gameplay...unless you'd add Ci¬G's attempt at a refuelling mechanic using a 5 year old ship model with a gaffer taped on metal...err...semi-phallic protuberance... that nobody ever liked flying in the first place into that mix. There's nothing else to talk about... since eating, drinking and barely functional ships is all Ci¬G seem to add these days 🤷‍♂️
 
Last edited:
I have a sneaking suspicion that the 3.17 builds are actually built on the 3.16 code they couldn't get to work back in December...the whole current 3.16 group of live patches is based on the ultra stable 3.15 code (3.16.1 is actually 3.15.3), they only added some of 3.16's content onto the build. I think Ci¬G are still trying to get the 3.16 base code to work but added certain content from the 3.17 branch to squeeze it in for the 3.17 dev cycle...Unfortunately, it's still broken...call it a hunch :whistle:
Some of the wording in the many PTU patches, and chatter among Spectrums, Reddits and Discords, indicates that 3.17 is the first stage (of many) of CIG implementing the Replication layer on the long road to static server meshing, with the huge amount of instability and bugs being a result of those refactors.

This could likely be a long 2022 of increasingly-broken SC updates, with playability getting worse before it eventually gets better - a few patches after static server meshing is fully enabled (whenever that is).

2022: The Year Of Server Refactoring.
 
Some of the wording in the many PTU patches, and chatter among Spectrums, Reddits and Discords, indicates that 3.17 is the first stage (of many) of CIG implementing the Replication layer on the long road to static server meshing, with the huge amount of instability and bugs being a result of those refactors.

This could likely be a long 2022 of increasingly-broken SC updates, with playability getting worse before it eventually gets better - a few patches after static server meshing is fully enabled (whenever that is).

2022: The Year Of Server Refactoring.
A few of us who have been here before with Ci¬G...several times :rolleyes:... expected exactly that and have written this year off for anything at all by way of substantial gameplay or additions (Like Pyro)...or player facing content wise...but the general noisy miasma obviously still doesn't get it... there'll be a lot of shouting :D
 
Last edited:
I have a sneaking suspicion that the 3.17 builds are actually built on the 3.16 code they couldn't get to work back in December...the whole current 3.16 group of live patches is based on the ultra stable 3.15 code (the current live patch, 3.16.1 is actually 3.15.3), they only added some of 3.16's content onto the build. I think Ci¬G are still trying to get the 3.16 base code to work but once again, added certain content from the 3.17 branch to squeeze it in for the 3.17 dev cycle...Unfortunately, it's still broken...call it a hunch :whistle:

One has to wonder what the 700+ employees at CIG are actually doing all these months. As the faithful have often stated, they aren't all just making spaceships.
 
One has to wonder what the 700+ employees at CIG are actually doing all these months. As the faithful have often stated, they aren't all just making spaceships.
We don't have to wonder at all...Sqn 404 ;)

I've noticed of late that in all the ISC vids, Turbulent's small-ish Montreal studio are supplying the cast with only Disco Hobo holding the reins for the rest of Ci¬G....it's not like any of them are allowed to discuss what the idiot Roberts may or may not be up to...
 
Last edited:
Some of the wording in the many PTU patches, and chatter among Spectrums, Reddits and Discords, indicates that 3.17 is the first stage (of many) of CIG implementing the Replication layer on the long road to static server meshing, with the huge amount of instability and bugs being a result of those refactors.
Smells a lot like wishful thinking to me. Also, yeah right, "replication layer". Translating from sales person speak to actual words, that would be AWS's Elasticache. Takes all of a few button clicks to turn that on. No, it won't magically "enable server meshing" or whatever else CIG like to claim for every Jesus tech they invent. It's a cache, not magic.
 
Back
Top Bottom