The Star Citizen Thread v5

Status
Thread Closed: Not open for further replies.

hahahahahaha this is real right? This is not someone making a parody skit right? This is actually something CIG produced and thought was a good idea to release to people. All this video did was give me the impression that CIG spends all of their time talking about what they want to make but not actually making it. And most of the video is explaining how bad they are at making a game and trying to come up with excuses.


And that is ignoring the fact they cut most of the main features of 3.0 in order to ship anything out.
 
Last edited:
My dear 1500 - it's much, much worse than that :D

It's basically people saying they have no idea how to schedule themselves, cannot manage a scheduler, are not surprised the schedule doesn't work, and what they are doing is so innovative that a scheduler won't work because what they innovate isn't bound to any schedule.

Sprint!

Waterfall!

Pipeline!

Agile or it's not worth doing!

What a load of absolute nonsense.

If they tried that in Mainframeland - I can't decide wether to laugh or cry bitterly.
 
I just love the first bit were Erin tries to explains how especially hard it is to develop SC, but all he does is talk about normal game development and problems any none indie game faces.
 
Last edited:
This is just also wonderful.

Network Bind/Unbind (STRETCH GOAL)
Eliminate network updates for entities far away from clients. Should greatly reduce the amount of work the netcode has to do, helping improve server performance. A greater proportion of client bandwidth will be spent on entities close to the client.
ETA is 26th June

What happened to thousand player instances? :D
 
I watched that video and thought "Yeah yeah, so fraking what? Every game development company has to plan for these things and work them out, why do CIG feel the need to make a video about it?"
With 3.0's release being 6 months later than CR's estimate, this video just feels like they're being defensive about that delay.
 
I watched that video and thought "Yeah yeah, so fraking what? Every game development company has to plan for these things and work them out, why do CIG feel the need to make a video about it?"
With 3.0's release being 6 months later than CR's estimate, this video just feels like they're being defensive about that delay.

ya look on the bright side, at least they are stripping everything from 3.0 in order to release it 6 months late.
 
Last edited:
That's a lovely schedule they obviously worked very hard on it, shame about the game.

Calling it now when they miss all those dates "busy updating the schedule" will become one of the go to excuses.
 
Someone on the SA forum noticed this...

Entity Update Component Scheduler

Will allow lower priority entities (i.e. those further away from players) to be updated less frequently, which should improve the overall framerate and allow us to add more content to the universe.

ETA is 31st May.

I guess this includes other players too. So much for thousands of players in one instance.

Get a refund.

Sorry ASP missed your post.
 
Last edited:
When they say a release date of 29/6 that's got to be for the Evocati right? Especially if the networking is only done a couple of days before.

That's not what the labels seem to say. As I read it, "gameplay" will be added half way through the Evocati testing and ships will be added just before Evocati ends, but Network and Backend will miss the Evocati testing window, and go straight to the live deployment (where "live" means "generally available Alpha-test").

Needless to say, this does not make sense. Target delivery of the product requires all the essential subcomponents to be ready first. It may be that the bars include internal testing, but with the given level of detail all we have is "we're choosing a date close enough not to dismay our backers, but far enough away to let us push it out further as we get closer to the release date".

The goal is always just over the horizon.
 
That's not what the labels seem to say. As I read it, "gameplay" will be added half way through the Evocati testing and ships will be added just before Evocati ends, but Network and Backend will miss the Evocati testing window, and go straight to the live deployment (where "live" means "generally available Alpha-test").

Needless to say, this does not make sense. Target delivery of the product requires all the essential subcomponents to be ready first. It may be that the bars include internal testing, but with the given level of detail all we have is "we're choosing a date close enough not to dismay our backers, but far enough away to let us push it out further as we get closer to the release date".

The goal is always just over the horizon.

And you're right. I posted that shortly after waking up and didn't even see the evocati bracketing at the top of the chart :eek::D
 
Did someone knock over Asp's lulzbuckets? He went to a lot of trouble to fill those.

No - the lulzbuckets are filled and burping squees contentedly :)

I'm still very amused with the latest content - or lack of it. I am sure many people here have actually worked with or on real systems that depend upon real results. I am also sure that they all share the same merriment as me and my lulzbuckets :D

Or sheer despair at the mere thought of trying to manage nested MS Projects :(
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom