Reply To: Star Citizen – Musings

Home Main Star Citizen – Musings Reply To: Star Citizen – Musings

#5914
Dsmart
dsmart
Keymaster

CHRIS ROBERTS HAS COMPLETELY LOST IT

These broadcasts are, among other things, about letting backers know the state of the project. They’ve been part of a long running ruse that backers who pay extra for a monthly subscription (yes, you get to pay a monthly sub fee that supposedly pays for these shows) are somehow paying to make them. That aside from the fact that backers have given this company $160M, but are still being asked to pay for what is basically ego stroking where backers only get to see and hear what it is Chris and Erin want them to see and hear. Yea, all under the guise of “open development”, which is a rather hilarious misnomer.

Ignore the fact that, given the backer count, and the view counts for these videos, over 97.4% of the backers don’t even watch them. At all.

There are so many examples of this bullshit, that I’ve basically lost count. However, the biggest one has to be from Dec 2016 when backers found out (through me of course, and before the newsletter even went out), that for the better part of that year, they were in the process of switching from one CryEngine derivative to another. The first time backers found out about this after it appeared in my Twitter feed, was when the 2.6 patch with the first implementation, was released. In all the shows throughout 2016; all the newsletters, all the publications, not once was this mentioned to backers. The reason, as we later came to find out, is because they didn’t want to cause panic, let alone admit that “Derek Smart was right” back in 2015 when I wrote that they couldn’t build the over-scoped game with the engine they chose. Of course nobody thought they would jump out of the frying pan, into a boiling pot. I wrote about that extensively back in Dec 2016.

Throughout his history, he has always blamed others for his disastrous failures, decisions etc. To the extent that, if you look back, EVERY SINGLE company and project he has ever spearheaded since Wing Commander the game – which was controlled by a publisher btw – has ended in COMPLETE DISASTER. Every. Single. One. And that’s not hyperbole, it’s FACT. And Star Citizen is no different.

Which brings me to this latest broadcast of Oct 12.

Yeah, because that totally looks like an inspired dev team

With the much awaited 3.0 patch out to Evocati testing, and which has been ruled to be an unmitigated disaster which I recently wrote about in a new blog, this latest broadcast, if nothing else, shows that not only is the project on it’s final legs, but that Chris has completely lost it. I don’t even know where to begin. Thankfully, our archivist Goon once again risks brain damage by transcribing the key parts of this broadcast. Note that the pressure, stress and strife seen in that broadcast, are a direct toll from the project being a complete disaster – and everyone in that broadcast knows this. And most are talking to friends and family about it.

The first gem comes @ 4:50

Wilmslow Studio – Dev
“Once we’ve figured out the last 10001 disconnect issue, we’ve got a build here from the UK, just deployed from… that was kicked off earlier this afternoon that should… the fixes for the disconnect seem like they’ve ‘taken’, we could get another code build done or a full build if we absolutely needed to, go through the process of putting that up to the Evocati so that we can get them… those fixes rolled out to them today, ah.. which is good… a couple of…”

Christ Roberts
Eh, ahhh I wanted… to mention it at project leadership meeting but it’s important that the… QUALITATIVE feedback, uh… is filtered through, ah… TARD… and we’ll make priority calls on it ‘cos… there’s some STUFF like you know, the 10001 error codes, yes with them we’re definitely… we’re definitely fixing, but then you know there’s some SUBJECTIVE feedback of like, “I don’t like THIS or I do like THIS” or whatever, now some of those issues they’re calling out we already know about we’re already working at addressing…

I always get a bit WORRIED because first of all we’re getting ah… kind of SUBJECTIVE feedback that’s sort of ANECDOTAL and so you know someone can have a strong OPINION but you know like, that could be THEIR opinion and maybe different to someone ELSE’S opinion as to whether it’s a bug or not… so it has to go through the FILTER of us on the very HIGH LEVEL of the kind of DESIGN SIDE to make sure that you know, it’s something that we wanna AGREE because a lot of the times people can’t see the BIG PICTURE when they’re making, ah… you know… FEEDBACK ‘cos they don’t know where the, you know, they’re like, “WELL THIS IS MISSING! I NEED THIS!” and we’re like ‘yeah, no shit we know it’s missing’, it’s kind of like on our TASK LIST, we’re working on it right now, and we understand that… you know… it hurts your ability to dogfight if you can’t see the status of your TARGET… or the status of your SHIP

Um, so… so I just wanna make sure we do that ‘cos we’re all worried that we automate it, some of these like subjective feedback get re-upped to JIRA, they get put in somebody’s BUCKET, maybe they get ASSIGNED and you know… we’ll spend some time working on stuff that needs to have… kind of… ahh… DIRECTION and… and… and… and… ORDER and PRIORITY called out.

SOMETIMES what people want to get FIXED, the solution is SOMEWHERE ELSE to fix the issue they’re complaining about… so on the subjective stuff I kinda wanna make sure that, um… we’re going through a FILTER on that.

By the time we get @ 6:07, it was already off the rails.

Christ Roberts
….a lot of times people can’t see the big picture when they’re making feedback…they’re like “well this is missing I need this!” and we’re like “yea no shit we know its missing! Its kind of like on our task list we’re working on it right now

By the time @ 7:20 rolls around….

Wilmslow – Director’s Meeting, Erin Roberts
“So it’ll be handy also if… if… when we get to the stage when we are, you know, looking at whether we’re gonna go… LAUNCH… ah, you know, do this every day as well… it would be nice to know what, you know, stuff was FIXED today, or, you know, GOING IN today as well, that kind of information would be great… that would be good… so… we know what we’re actually putting into the build and so forth, I know the information’s passed to… WILL and those guys because they need it to tell people but I have no idea.”

Ricky Jutley (Senior Producer)
Yep, I think it’s TUESDAYS basically, I think moving forward TUESDAYS will incorporate the live sync within the director’s sync, and the PU will have to go first, and people obviously listen to that kind of stuff, and um, that will be the way that TUESDAYS has to kind of run

Christ Roberts
I think what Erin… Erin was saying was actually what I was gonna kind of bring up, which was… you know… the way I look at it we’re in Evocati now, we’ve got 800 testers instead of 70 testers… and we should be looking to deliver a build every day if we can to them ‘cos we have the DELTA PATCHER… but… the key is not so much about, ‘oh we’ve got one blocker, there’s a crash here or a deadlock here’, which was sort of the approach we were taking in like getting it to Evocati… the KEY is like, ‘OK! What bits of the thing we’ve still left to do are vying for this coming MONDAY’, what about this coming TUESDAY cos… I don’t wanna have like only one blocker fixed, right? Cos we’ve got people finishing CONTENT, you know, doing LIGHTING, you know…

OK? And we… you know… these… these three areas have now being LIT, have they gone in? This SHIP has now been brought over to item two point zero has it gone in? That’s kind of it, cos what we actually want to do is have a steady stream of… ah… you know… things are getting like… FINISHED OFF or FIXED UP… putting in… and we want an… “Ok, here’s an Evocati, here’s the things that have gone in that we think we’ve fixed’, cos you’re basically… you’ve just got to sort of manage that over time so we’ve… we’ve got to get into that MODE as opposed to the… you know… what three bugs have we got to fix before we CAN go to Evocati

…we were completely off the rails by @ 9:20

Wilmslow – Dev/QA
So the next steps for us here in… CIG… is, we’re focusing on the SHOPPING ah, feature… SHOPPING and commodities as… as a FEATURE… em, to… PRESENT… to the Evocati and say, this is now… in a STATE were you guys can just… GO NUTS! Go ahead! Buy, sell… so, whatever you want

Jake Ross (Producer)
We’re fixing bugs left and right, we’ve got issues were certain CLOTHING items… CLOTHING and items aren’t showing up in the shops right, there’s issues were you can’t interact with an item through a glass case, ‘cos the glass is getting in the way with the interaction system so we’re trying to figure that out, uh… and we’re trying to work out some KINKS with the TRY ON MODE were when you look to inspect a… uh… uh… an ITEM like a ship component or something, the character will look around like he’s got… look… got GLOVES on and he’s looking at his GLOVES so like we’re just ironing out kinks getting everything working really well

Spencer Johson (Assoc Gameplay Engineer)
So right now I’m focusing on a suite of different SHOPPING related bugs and features that we’re pushing out to the Evocati soon… ah, today a couple of them are focused on the weapons being attached to the item ports on the shelves, so we got… trying out a weapon in the shop, drops it onto the floor for remote players, uh… weapon models disappear after inspecting them (he’s reading all this off his screen btw), these are the GREAT kind of bugs cos they’re not 100% repro, so they only happen sometimes… which are always the best to find and solve…

Wilmslow – Dev/QA
So what we’ve done is, eh.. we’ve taken… our… um… TOP ISSUES that we wanna get fixed, these are a collection of uh… BUGS and TASKS, ah, we’ve gathered those together, put them into the Evocati FIXED VERSION, and our internal JIRA tracking software and um… this is where we saw the burndown graph come from the last time, so when you see this report go out you’ll see the… the NEW LIST of numbers… oh, sorry, the new TOTAL number.

The general demeanor of most everyone in that conference call, screams of resentment, resignation, frustration, and stress. Aside from the obvious clues that most in there don’t even respect Chris enough to pay any attention to his drivel, the fact remains, this project is FUBAR and Chris has completely lost it.

The arrogance of it all is that, toward the end of the broadcast @ 41:08, he says this:

….it’s been just over five years since we first announced Star Citizen at GDC in Austin on Oct 10th, which was two days ago. And it’s incredible to think how far we’ve come in such a short amount of time, and only been possible because you’ve supported us along the way

Yeah, for a project that was said to be coming in Nov 2014, then over-scoped, has been coming out every year since then; and now is almost three years late this coming November.

3.0 EVOCATI TURNMOIL

You see, here’s what backers don’t know. The 3.0 build, having been rushed out to Evocati in order to start drumming up the concept that it was almost ready, is a complete disaster. Let’s ignore the connection problems of the past 48hrs, or the fact that the build is still a performance nightmare, flat out broken, missing a slew of features they claimed was already completed etc – all the things I have previously written about. Let’s focus on the fact that, as of this minute, while largely unplayable, CIG is not only now saying – on the record – that backer input is inconsequential and meaningless, but that they’re not even going to listen to feedback anyway. Which explains the 3000+ bugs currently in 2.6.3, and the dozens that have so far been found and logged since 3.0 went to Evocati on Oct 5th. And all the bugs they decided to shove under the carpet weeks ago, are now rearing their ugly heads in all aspects of the 3.0x build. To the extent that even when Evocati do encounter and report them, they are told not to report anything that’s not part of the “focus testing” for the specific build.

So, last night, following this AtV and aside from the ire over the Gladius cockpit and MFDs, the bullshit helmet HUD that’s coming back etc, there were quite a few very upset Evocati testers. The hardcore ones at that. Basically, all of what has gone on in the past regarding the seventeen months long Evocati program, just unraveled in a single broadcast in which Chris and his cohorts basically confirmed that it’s all a sham and publicity stunt. Imagine this. There are about 800+ Evocati testers now. Last we checked, not even 100 of them have even touched the build. Those who came in during the initial wave, saw the mess, and never game back. I know this because, guess what, leaks aside, everyone is talking.

And the worst part of it is that streamers like AstroPub who are in Evocati and who do know what’s going on, spend most of the time sweeping it under the carpet, helping CIG mislead and lie to backers, while pretending that everything is OK. And that’s got nothing to do with the NDA btw because, right there in the chat, instead of holding CIG’s feet to the fire, they’re basically playing the submissive game, while making asinine passive aggressive comments. Because, you know, nobody wants to get kicked out of the exclusive club for speaking up. Which is how we get leaks like this. Unfortunately for them, with the number of Evocati now ready to fall on their swords as a result of 3.0 not being what it was hyped up to be, ALL of it going to come out at some point – screen grabs and all. And I’m going to publish it. All of it. My attorney is on speed dial. Bring it.

THE REFUND CASCADE

A few months back, sources had told me that CIG was 1) going to stop doing refunds 2) release a new ToS, possibly to go with the 3.0 patch release. However, less than hours after my latest blog went live, and I sent out the tweet below, a slew of posts appeared on the refund Reddit, indicating that CIG was now refusing refunds. There is even a thread now with tips on how to take legal action.

You can still get a refund. Do it before the window closes cuz they ARE going to stop giving them. $3K refunded” – Tweet

I reached out to my sources and but nobody knows what is going on. My one credible source was the one who told me that he has to check around because they (devs) have no clue wtf management is even doing from one minute to the next. They he came back later and basically said that’s the policy going forward. He did say that the person who notified him, said that she was told that it was always the policy, but that they were issuing refunds on a case by case basis all this time and not something they were required to do.

Right. Where have we heard that before? Oh I remember.

It seems to me that this “delay” to issue refunds, financial ability aside, is probably a ploy to hold off on spending any money, until they get to see the reaction of the 3.0 release or non-release. You see, that’s precisely how a Ponzi scheme collapses. Once new money isn’t enough to pay off old money, or if you need to conserve cash, the whole thing collapses. CIG has basically been using new backer money, to refund old backers who want out. And we already knew that it simply wasn’t sustainable in the long term; especially with the project in turmoil, and over three years late. There is no plausible reason to “delay” refunds to people who were already in the refund process, under the guise of “hey we’re busy with 3.0; fuck off”. Which begs the question: what the hell does CS staff have to do with development – for a project that currently employs over 300 people worldwide?

Thing is this:

  • If they release 3.0 before or during CitizenCon (Oct 27th) in this condition, they’re screwed.
  • If they release 3.0 it before year end in this condition – like they did with 2.6 which released in mid Dec 2016 – they’re screwed.
  • If they don’t release 3.0 before year end, at either CitizenCon, during the anniversary stream, or before year end, they’re screwed.

Now, speaking as a game dev, this wouldn’t be an issue if your development wasn’t tied to on going funding. But because CIG clearly needs the money – via the goodwill of ignorant backers stuck in sunk cost fallacy, and Q4 being their biggest fundraising period, the decision to hold onto 3.0 for another six months while they get it in a better condition, is a disaster. It’s almost as if they don’t really have money in reserves as Chris has claimed, and that they do need the on-going funding in order to survive. If the perception of 3.0 wasn’t tied to financials, they wouldn’t be hiding it behind Evocati, taking steps to out and ban those who are leaking info about it, issuing (there is no credible evidence yet that CIG is behind this, despite statements made in 2014 to the contrary) DMCA takedowns of YouTube video leaks etc. Even the delta patcher, which works for the most part, is enough to allow them to release the 3.0 build to all backers as-is, because that whole notion of keeping AWS costs down by not making early builds accessible to all backers, goes out the window. Not that it ever made sense, because why else would they need to hide it behind an NDA if Evocati selection was necessary in order to save on costs?

As I’ve said before, CIG are well within their right to refuse and/or delay refunds as they see fit. Whether or not it’s legal, is left up to the courts and the government officials. You mad enough yet? Well how about this guy who was given a $10K+ refund check he can’t cash?

Get a refund, fool. The game is never – ever – coming out.

SQUADRON 42 DELAYED (INDEFINITELY)

Shockingly, in the latest newsletter Chris has declared that the December anniversary stream will showcase Squadron 42. Which means it’s not releasing in 2017. I called this one back in May. Now that it has no release date showing on the website, safe to say that it will either be canceled, or will be part of the early access change that Star Citizen is about to enter. Which means they don’t have to deliver it or Star Citizen. Ever.

SQUADRON 42 DELAYED TO 2018

As I reported on Twitter earlier today, several sources, as they have done twice before in 2015 and 2016, have once again informed me that SQ42 is now a 2018 game. In fact, the current internal schedule shows it stretching all the way to mid-2018, and possibly beyond. The past two times that I had reported this, some people didn’t believe it. And CIG kept denying it. This Sept 2016 denial was my favorite. Both 2015 and 2016 came and went. Right up to the blatant lies that CIG told during the events (GamesCom and CitizenCon) of Q4/2016. I wrote extensively about that in my Shattered Dreams blog from Oct 2016.

Sources also tell me that they’re frantically trying to either get a preview or trailer out before the end of the year. So yeah, probably a repeat of Q4/2016 all over again.

Oh, and they have definitely chopped up the SQ42 game. I reported on this back in 2016 as well, but they have apparently stuck to the goal of releasing the once full game, into bits and pieces in order to “keep things going and raising money”. It makes perfect sense if you ask me. They know that the minute they release any “final” version of any portion of this train-wreck project, that’s it’s all over. So why not maintain the bait and switch Status Quo by splitting a full game into parts, then sell them separately? If you recall, they did that back in 2016 when they split SQ42 from Star Citizen, in order to sell it separately. Except this time, they’re going to split SQ42 even further. Which, now that I think about it, explains why you can buy that game for $15 (instead of $45) if you buy it as a bundle ($45 + $15) with Star Citizen. My God man! We’re doing it all wrong.

The last time this happened, it was Star Marine. It was delayed for years, continuously hyped to the hilt, then rushed out in the 2.6 update released in Dec 2016 as the only tangible release that whole year. It was immediately forgettable, and died shortly after.

Meanwhile over on /r/games, as of this writing, this post had almost 500 upvotes.

As I’ve pointed out before, back in January 2015, Roberts delivered a presentation in which he claimed that not only would the first episode of Squadron 42 be released by Fall 2015, but the full commercial release – meaning SQ42 and the persistent universe / MMO – would happen by the end of 2016. He made this claim at 1:32:06 in this video.

At the time of this presentation, the PU wasn’t yet in the alpha stage. He seemed to think that his team could get through all of alpha, get through all of beta, and optimize enough for a decent MMO launch in 2 years, all while concurrently working on a single-player game. By saying this, he demonstrated that he either didn’t know what he was talking about, or he was being dishonest. It was probably a combination of the two.

Now, almost 3 years after that presentation, backers still haven’t seen a mission demo of SQ42, and the MMO is in alpha with, I’m guessing, another 1-2 years of alpha ahead of them. At this rate, I would be impressed if the first episode of SQ42 gets released by 2020, and the MMO gets released by 2023.