Game Discussions Star Citizen Discussion Thread v12

No I get that, often times if you enjoy a game or not comes down to your internet connection, your rig or just picking a "good server". So some people saying "I ve never had this issue" and others saying "I m always crashing and gitching out" doesnt mean that one of them is lying. It could very well be different for both of them. But the example I gave quotes him with never having the issue himself while also acknowledging that elevators only kill rarely anymore which I would take as having inside information or a source that would allow me to make such a statement. I wonder what his source is and I was asking him to share. Is it just a select group of friends that he trust more then other random backers/users or is it some kind of statistic unknown to me or others?
I doubt Tyler Witless crashes often. He's too busy being excited for roadmap and playing Sq42 levels.
 
i
We all started around that time. Software distributions wasnt at its peak and the magazines were full of listings.
Had you looked up from your listing you might had noticed that the 'tool' is neither well-documented (Tyler Unwit is sill waiting excitedly for the new roadmap) nor 'solid'.
I think like you. If they make a game engine it will only be for them, like the Rockstar Advanced Game Engine is only used by Rockstar.

LOL. You certainly don't work in development, do you!
I work in development since 30 years (98% web) and make some little games for my pleasure (my first lines of code with C64 but really started to code with AmosBasic).
 
Last edited:
I work in development since 30 years (98% web) and make some little games for my pleasure (my first lines of code with C64 but really started to code with AmosBasic).
So why do you keep making up fantasies that were disproven long before that and reject standard knowledge that anyone with any measure of development knowledge will know? Is it because CI¬G are clueless in the field of development and toeing the party line is more important than sticking to what you've known for decades?

The Brooks law is about late project, not overdue projects that doesn't care about deadlines (talking for SC only).
Brook's law states that "adding manpower to a late software project makes it later". SC is a late project. Whether they care or not is immaterial — it only helps explain why they're doing something so idiotic as trying to solve their lateness by adding manpower. They, like you, believe that more teams working in parallel on same work with same tools = faster delivery of systems. The book explains very clearly why this does not actually happen, especially not once you've already a immensely over-bloated team. You should re-read it.
 
Last edited:
You don't get it CIG do what's never been done before in a way never been done before, so common everything (starting with sense) do not apply.
I don't know one game company that can push deadlines at will for several years. So they effectively manage the project in a way never been done before and they don't care about some common rules of managment.
 

Viajero

Volunteer Moderator
Given the SQ42 beta proposed timeline has come and gone, and it is the first Friday after said timeline I presume today it would be a good date to offer some news, double good for them to do it on a Friday if it is bad news.
 
Last edited:
Parallelization works when the tools are solid and the teams are competent. A simple example : the tool (minecraft) + the guideline (Game of Throne documentation) + hundred people and you get WesterosCraft.
That makes sense if all they have to do is make content. The problem is that the underlying engine (and, by extension, the tools) are constantly changing - resulting in existing content breaking, and in-progress content having to be constantly reworked to keep up... Not to mention the other parts of the engine that are dependent on the things being altered. Parallelisation works when the different parts are not dependent on each other (or at least, the co-dependent parts aren't changing) - that isn't really the case here...
 
I don't know one game company that can push deadlines at will for several years. So they effectively manage the project in a way never been done before and they don't care about some common rules of managment.
Blizzard. And CI¬G not caring about common rules of management is just what makes them profoundly incompetent and even outright stupid.
 
I work in development since 30 years

Your English teacher would be ragging you over this one!

Since is used with a specific date. For is used for durations. Also tense is wrong.

I have worked in development for 30 years
OR
I have worked in development since 1990

;)
 
So why do you keep making up fantasies that were disproven long before that and reject standard knowledge that anyone with any measure of development knowledge will know? Is it because CI¬G are clueless in the field of development and toeing the party line is more important than sticking to what you've known for decades?


Brook's law states that "adding manpower to a late software project makes it later". SC is a late project. Whether they care or not is immaterial — it only helps explain why they're doing something so idiotic as trying to solve their lateness by adding manpower. They, like you, believe that more teams working in parallel on same work with same tools = faster delivery of systems. The book explains very clearly why this does not actually happen, especially not once you've already a immensely over-bloated team. You should re-read it.

But... but... staggered development.

Also, perhaps i was hasty when i talked about young people learning bad development at the knee of the Code Whisperer. It appears even experienced people can suffer the brain worms that are induced by listening to too much Roberts.
 
I don't know one game company that can push deadlines at will for several years. So they effectively manage the project in a way never been done before and they don't care about some common rules of managment.
Well that doesn't guarantee a positive output unfortunately. "NASA has hard times reaching Mars by throwing things at the sky, maybe if we dig deep enough in the ground we can reach it, and even further, before them!"
 
Given the SQ42 beta proposed timeline has come and gone, and it is the first Friday after said timeline I presume today it would be a good date to offer some news, double good if bad news.

So, CIG haven't commented the passing of their own deadline?

MOST TRANSPARENT COMPANY EVER!
 
Backers are probably overqualified, what with them all being CTOs and whatnot.
There is no such thing as overqualified Chief Trolling Officer
Her signature's weird.
We sign with Sandi!

Dear friend, you teach me nothing about those laws (Brooks, Hofstadter, Peter's principle, etc). I started to code 35 years ago, hard to miss them when you are a coder. The Brooks law is about late project, not overdue projects that doesn't care about deadlines (talking for SC only). Re-read the law.

Parallelization works when the tools are solid and the teams are competent.
Dear sir, I'm surprised that you, having 35 years of coding experience, think that technology doesn't get obsolete.
I'm even more surprised that you put overdue and 'no deadlines' together - one can't be overdue if there is no due. SC is not overdue, it is late.
By the way, you are directly contradicting Saint Roberts himself, who said that game becomes stall if developed longer than 4 years. Even counting from "reboot" (surprised again that you believe in that cowpiss), we are already here.



But again, Christopher was in this business not as long as you, dear sir, even if we don't count all his downtimes, therefore you sound more plausible, and your own words show that Roberts is a liar.

That explains why tools aren't solid and teams are incompetent - predictable with leadership like that.
 
Back
Top Bottom