The Star Citizen Thread v5

Status
Thread Closed: Not open for further replies.
Just in time for the upcoming holiday sale, the chairman sent out another newsletter (this is the anniversary sale one) ahead of the upcoming holiday sale. It's not live on RSI yet, but start laughing. He actually wrote this:

"For those keeping track, we got Alpha 2.6 made the release window forecast from the Production Schedule Report"

Remember when I said they pushed 2.6 out on 11-30 in order to claim that it was "released"?

Proof or link to source newsletter?
 
Just in time for the upcoming holiday sale, the chairman sent out another newsletter (this is the anniversary sale one) ahead of the upcoming holiday sale. It's not live on RSI yet, but start laughing. He actually wrote this:

"For those keeping track, we got Alpha 2.6 made the release window forecast from the Production Schedule Report"

Indeed. If you count changing it twice after the previous window had run out as being according to the forecast. :D
Also, 3.0 before new-years, right? I believe that was forecast too…
 

dsmart

Banned
Hey Mods, I am curious as to why this post was removed. Maybe it was a mistake during the last edit pass that Brett mentioned?

That looks like the "star marine only" build they pushed 2 days ago.

As you can see, it looks completely different from the fake crap they've been trying to shove through. SM was not active for play in the 1st 2.6 build they pushed. Like, at all. Which is what I was saying all last week that they are silent because they wanted to sneak it out at some point under the guise of plausible deniability.

I haven't seen it yet btw, as I haven't fire up the game since the last "minor" update they pushed the day after 2.6 went live on 11-30.

ps: given the person who is sharing this, I would still treat this with suspicion. On 12-16, we'll see if it goes live to the PU or not.
 
I don't think anyone knows any more. I think CIG's version numbering may be a live case of a repriversexclusion — it can be anything other than itself. So it's most likely not an alpha, and even more likely not version 2.6. ;)

2.6 is in the pre-alpha stage for snowflake testing in order to release a alpha module for a pre-alpha stage game.
 
This can be interesting...

Star Citizen - 2.6.0 - Personal Player Pulse (NON-EVOCATI-OFFLINE-MODE)
[video=youtube;wr5eCI-jLqs]https://www.youtube.com/watch?v=wr5eCI-jLqs[/video]
 
"Let's gather coolness seen elsewhere, append functionnality later"

I troll, sorry. A nice thing would be a "class" of player could have this kind of pulse detector tool to feed his comrades' radars. Would be better than a constant wallhack. They could add a counterpart tool which would jam radars.
 
Last edited:
"Let's gather coolness seen elsewhere, append functionnality later"

I troll, sorry. A nice thing would be a "class" of player could have this kind of pulse detector tool to feed his comrades' radars. Would be better than a constant wallhack. They could add a counterpart tool which would jam radars.
EMP grenades and maybe even the Herald(Amongst other possible stuff).
 
It's actually looks nice, although I predict CIG forums will have a meltdown about not being "deep enough" (and it is similar to radar thingy they showed off and triggered avalanche).
 
It's actually looks nice, although I predict CIG forums will have a meltdown about not being "deep enough" (and it is similar to radar thingy they showed off and triggered avalanche).
Now I gotta go look - that'd be a different kinda bonkers.

I mean effect first -> reason later is pretty weird, but as perhaps a pre-cursor to a period of wall-hack as a skill/bonus/thing.... there's precedent and could be a place for it
 

dsmart

Banned
Yeah, this is part where they lose me. I understand reason for Evocati and alpha testing bug fixing, etc. but this manipulation is where I am just off.

edit: also isn't it 2.6 pre-alpha-alpha? :)

As I said earlier:

That looks like the "star marine only" build they pushed 2 days ago.

As you can see, it looks completely different from the fake crap they've been trying to shove through. SM was not active for play in the 1st 2.6 build they pushed. Like, at all. Which is what I was saying all last week that they are silent because they wanted to sneak it out at some point under the guise of plausible deniability.

I haven't seen it yet btw, as I haven't fire up the game since the last "minor" update they pushed the day after 2.6 went live on 11-30.

ps: given the person who is sharing this, I would still treat this with suspicion. On 12-16, we'll see if it goes live to the PU or not.

There is only ONE Evocati build. All other builds are standard builds.

DEV (pushed by devs for testing) -> QA (internal QA) -> EVOCATI (usually the same build as QA) -> WIDE PU TEST (out of Evocati to larger group, usually subscribers) -> LIVE (public release)

Anyone with access to Star Marine when 2.6 was first released on 11-30, did NOT have access to SM other than via hacking the files and ending up in solo play

Think about this for a moment and you will see what's going on.

  • on 11-30, 2.6 was only pushed to Evocati (800+ people). It contained the SM files, though it wasn't playable
  • The 2.5.x patch will NOT download the 2.6 Evocati build
  • Anyone (not in DEV or QA - as above) with access to 2.6 had to have downloaded it as part of the Evocati release
  • If they had access to it - as per of #3 - why then did they have to hack it in order to access Star Marine if it was an official build they could just play?

Simple. The files where. But it wasn't an official release of Star Marine. They enabled it later via a "Star Marine only" patch update due to all the noise that's been going on about it. Which is precisely what I said they would do. They did that about 48hrs later.

I can't even believe that people are arguing about this still. This is what I stated back then, and I was 100% right.
 
Last edited:
As I said earlier:



There is only ONE Evocati build. All other builds are standard builds.

DEV (pushed by devs for testing) -> QA (internal QA) -> EVOCATI (usually the same build as QA) -> WIDE PU TEST (out of Evocati to larger group, usually subscribers) -> LIVE (public release)

Anyone with access to Star Marine when 2.6 was first released on 11-30, did NOT have access to SM other than via hacking the files and ending up in solo play

Think about this for a moment and you will see what's going on.

  • on 11-30, 2.6 was only pushed to Evocati (800+ people). It contained the SM files, though it wasn't playable
  • The 2.5.x patch will NOT download the 2.6 Evocati build
  • Anyone (not in DEV or QA - as above) with access to 2.6 had to have downloaded it as part of the Evocati release
  • If they had access to it - as per of #3 - why then did they have to hack it in order to access Star Marine if it was an official build they could just play?

Simple. The files where. But it wasn't an official release of Star Marine. They enabled it later via a "Star Marine only" patch update due to all the noise that's been going on about it. Which is precisely what I said they would do. They did that about 48hrs later.

I can't even believe that people are arguing about this still. This is what I stated back then, and I was 100% right.

It has already been proved that the evocati build indeed had Star Marine playable.

Video from evocati build, uploaded to youtube on 11-30: https://vid.me/1Fys

Proof of it having been uploaded on 11-30:

lf8N8wL.png


Someone please quote this post. Derek has me on ignore list, so i suspect he isn't yet aware of this.
 

Even if it was not active(talking about if the first build had SM enabled or not) it was probably because it had a blocker... not because some evil plan of not releasing SM in 2.6

I don't see the point of continuing this boring debate of wether the first build had it or not. I understand that there is not much to debate these couple of days/maybe more than a couple... but guys... really? Again with this?

But as always just my opinion.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom