Star Citizen: Death of a Space Thread?

The Something Awful Forums > Archives > Comedy Goldmine > The Goodmine > Star Citizen: Death of a Space Thread?

«‹›6530 »

Beer4TheBeerGod: Aug 23, 2004; Exciting Lemon

I wonder if Amazon is even remotely aware of what's happening with their engine.

# ? Dec 29, 2016 18:34

Adbot: ADBOT LOVES YOU

# ? Apr 25, 2024 10:43

Blue On Blue: Nov 14, 2012

XK posted:

That was me as well.

I'm totally baffled about these explanations he's given, even assuming he's just a lighting guy who's out of the loop. His statements seem to reveal specific things that CIG was trying to skim over and ignore.

Ben Parry is going to be told to shut up, and his posts at the Frontier forums will cease.

Just like those before him

# ? Dec 29, 2016 18:35

Colostomy Bag: Jan 11, 2016; C-Bangin' it

Beer4TheBeerGod posted:

I wonder if ~~Amazon~~ CIG is even remotely aware of what's happening with their engine.

# ? Dec 29, 2016 18:36

Tippis: Mar 21, 2008; It's yet another day in the wasteland.

Beer4TheBeerGod posted:

I wonder if Amazon is even remotely aware of what's happening with their engine.

It's probably just a clerical error that not even a mention has been made on the Lumberyard blog in the week since the news broke.

# ? Dec 29, 2016 18:38

Blue On Blue: Nov 14, 2012

Tippis posted:

It's probably just a clerical error that not even a mention has been made on the Lumberyard blog in the week since the news broke.

Hey guys who is this cig person ? Are we making any money off them ?

It's pretty funny because that's probably exactly what Chris said when someone brought up amazon

Blue On Blue fucked around with this message at 18:44 on Dec 29, 2016

# ? Dec 29, 2016 18:41

Scruffpuff: Dec 23, 2015; Fidelity. Wait, was I'm working on again?

Beer4TheBeerGod posted:

I wonder if Amazon is even remotely aware of what's happening with their engine.

They don't know and they don't care. I've worked with these guys before and rule #1 is their integration specialists are trained to say one, and only one, thing if you're a prospective client: "Absolutely."

"Listen, I have some very odd legacy code, can we scale this into your cloud solution?"
"Absolutely."

"OK but this is like Windows 95 poo poo with static IP and SSL 2.0 and it's very old, our old systems actually don't even use the internet, we have a direct connection between our office and the building holding the server."
"Yes, absolutely we can support that, we have a team of dedicated professionals to walk you through any migration challenges you may face."

"OK but actually most of the clients are old Commodore 64 machines hard-coded to attempt to connect to QuantumLink, we use old hacking tools written in 1983 to get them to even boot."
"Yes, absolutely, we've got middleware solutions in place to help you bridge your infrastructure to our cloud."

Chris is a grade-A idiot. He understands not only zero game development, but zero about life in general. And so the scammer becomes the scammed.

# ? Dec 29, 2016 18:42

Chalks: Sep 30, 2009

AbstractNapper posted:

Parry explained it more on the frontier forums, and then some other guy also offered his understanding of it and Parry seems to have agreed.
https://forums.frontier.co.uk/showthread.php/259596-The-Star-Citizen-Thread-v5?p=4943960&viewfull=1#post4943960

Basically, second image shows the trunk red (but it's the same trunk as the first image) because it is now let's say labeled as LumberYard code, even though it is identical to the CryEngine "trunk" up to the point that LY forks off (3.8.x). (Ben or some other guy call it "LumberYard legacy code" up to the point of the fork off CE 3.8, where LumberYard proper begins). SC remains forked off the previous point (3.7) as it was originally.

No actual merge has occurred.

But they are now in "LumberYard" because Amazon has a license that gives them access to the CryEngine source code "history versions" before 3.8 (3.8 being the point where they forked off from and did their own thing); so basically SC can now say its a fork off LumberYard "legacy code" (ie Cryengine 3.7 as it always were) or has switched to LumberYard (marketing speak mainly).

So literally nothing has changed what so ever? How is anyone even talking about this?

# ? Dec 29, 2016 18:48

Scruffpuff: Dec 23, 2015; Fidelity. Wait, was I'm working on again?

Chalks posted:

So literally nothing has changed what so ever? How is anyone even talking about this?

Bingo.

# ? Dec 29, 2016 18:50

Blue On Blue: Nov 14, 2012

Chalks posted:

So literally nothing has changed what so ever? How is anyone even talking about this?

It's me , I'm the news about Lumberyard furiously waving it's arms and making funny noises trying to distract you

While in the background 2.6 burns at 5000 degrees and small children are being suffocated due to the fumes

# ? Dec 29, 2016 18:50

Chalks: Sep 30, 2009

Scruffpuff posted:

Bingo.

So Windows XP Media Center edition is branched from Windows XP. This move is basically the same as Microsoft announcing that they've migrated it to "Windows 10 legacy" without changing a single line of code.

How the hell is everyone involved in this so dumb.

Do they have to pay additional licensing fees to Amazon now? lol

# ? Dec 29, 2016 18:53

AbstractNapper: Jun 5, 2011; I can help

Chalks posted:

So literally nothing has changed what so ever? How is anyone even talking about this?

Yes. And they do like to parp, so there is your answer.

# ? Dec 29, 2016 18:54

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

We're having problems with development because of Amazon cloud service issues.

Give us more money.

# ? Dec 29, 2016 18:55

Dementropy: Aug 23, 2010

Chalks posted:

So literally nothing has changed what so ever? How is anyone even talking about this?

It's a great announcement! I know you might have been writing posts about why 2.6 may have broken things that were present in 2.5. Some of you may even have been wondering where 3.0 is, or even SQ42. Others may have been pondering why nothing we showed at Gamescom or CitizenCon, outside of the bland and broken Star Marine, made it to our end of year update, and the reasons for this are...HOLY poo poo LOOKATTHAT! CIG is "partnered" with Amazon and using their engine to do...what exactly?

In conclusion, CIG is a land of contrasts. Thank you for your time, and see you sometime in 2017.

# ? Dec 29, 2016 18:55

Scruffpuff: Dec 23, 2015; Fidelity. Wait, was I'm working on again?

Chalks posted:

So Windows XP Media Center edition is branched from Windows XP. This move is basically the same as Microsoft announcing that they've migrated it to "Windows 10 legacy" without changing a single line of code.

How the hell is everyone involved in this so dumb.

Do they have to pay additional licensing fees to Amazon now? lol

It's true that as of right now, nothing has really changed. But this also represents a Hail Mary pass from Chris that Amazon can help them slog through their years of failures where the Crytek engineers couldn't. Now with Amazon's experience and success implementing (a different version of) ~~CryEngine~~ LumberYard with their AWS platform, Star Citizen backers can now experience NETWORK and MESH like never before.

You have to think like a visionary if you're going to be able to see things that aren't there.

# ? Dec 29, 2016 18:58

Fat Shat Sings: Jan 24, 2016

Chalks posted:

So literally nothing has changed what so ever? How is anyone even talking about this?

Surprisingly we gave CIG the benefit of the doubt and assumed they had made a deal or taken steps toward upgrading their engine.

The best part of all of this is now Ben Parry and Chris Roberts have to crawl out and scream "WE AREN'T UPGRADING AT ALL! WE DIDN'T EVEN DO ANYTHING!"

# ? Dec 29, 2016 19:02

Strawman: Feb 9, 2008; Tortuga means turtle, and that's me. I take my time but I always win.

Dementropy posted:

It's a great announcement! I know you might have been writing posts about why 2.6 may have broken things that were present in 2.5. Some of you may even have been wondering where 3.0 is, or even SQ42. Others may have been pondering why nothing we showed at Gamescom or CitizenCon, outside of the bland and broken Star Marine, made it to our end of year update, and the reasons for this are...HOLY poo poo LOOKATTHAT! CIG is "partnered" with Amazon and using their engine to do...what exactly?

In conclusion, CIG is a land of contrasts. Thank you for your time, and see you sometime in 2017.

It's also an attempted spoiler of the much bigger news of Derek Smart's 'Line Of Defence Tactics - Tactical advantage' going on sale.

http://store.steampowered.com/app/267220/

# ? Dec 29, 2016 19:02

Chalks: Sep 30, 2009

Scruffpuff posted:

It's true that as of right now, nothing has really changed. But this also represents a Hail Mary pass from Chris that Amazon can help them slog through their years of failures where the Crytek engineers couldn't. Now with Amazon's experience and success implementing (a different version of) ~~CryEngine~~ LumberYard with their AWS platform, Star Citizen backers can now experience NETWORK and MESH like never before.

You have to think like a visionary if you're going to be able to see things that aren't there.

I have a vision of two futures, one involving nothing changing and another involving massive additional delays, rewrites and extremely expensive consultancy bills.

Visionary indeed.

# ? Dec 29, 2016 19:03

Mr.PayDay: Jan 2, 2004; life is short - play hard

Nothing really matters, the days-since-CIG-hosed up-again-counter can be reset even weekly and the Cult will still spend 25-30 Million Dollars in 2017 after CIG just releases parts of 2.7-2.9 or even 3.0 and SQ42 Ep1, no matter how cut and broken this stuff is.
The PTU modules - no matter how limited they come - will be enough to satisfy the Cult, again.

Every part of alpha stuff released means keeping the dream alive and proving the Goons and Derek wrong.
Citizens will continue paying money for this. "2017 will decide their fate!" lol, no. The funding won't stop, the chairman will feeding Gamestar.de and Pcgames.de with exclusive jpegs and avis.

The entertainment will not stop, not in 2017

# ? Dec 29, 2016 19:03

The Titanic: Sep 15, 2016; Unsinkable

ewe2 posted:

Sorry in advance for this rant, I just wanted to make it clear as clear why there are problems with CIGs/Parrys "explanation". Please point out mistakes or confusions/omissions.

Just managing the pieces of a website in git can teach you a lot about how VCS actually works and not how Ben Parry wants you to believe, like just skipping main development line history. Good VCS patterns are about minimising merge conflict and small, manageable deltas, regardless of the size of the project.

Let me break it down into a hypothetical, the kind of hypothetical that the Reddit crowd hates because they'd have to apply braincells to it, and let's pretend we're using git because its an excellent distributed VCS that lets you decide how to manage your workflow:

You've got engine code, it's made up of different bits that different groups of developers can work on, and like a good game company you want to make modifications to make the greatest game ever and you want builds to work so you can demonstrate how things are going (you know, not like SC). There will be a bunch of stuff that doesn't use the engine at all, ignore that in this discussion, it would be added at the build branch stage to make a build work and then get added to the main branch. Here we're only concerned with bits that need the engine code.

Ideally we'll have a development branch, a build branch and a main branch. You're the guy coordinating this because your developers are all working on their bits of the engine and when they put in changes, you make sure all the different bits agree and you take a snapshot of the current development branch and call that the build branch (and add those bits I mentioned above), and if it builds, those changes make it into the main branch. Clear so far? You can give these snapshots whatever name/version you like as long as it makes sense to everyone.

Ok, so down the track your builds are going fine but meanwhile the engine developer has released a new version of the engine and you want to take advantage. So you grab the new engine code, and to be safe, you clone a new copy of the original engine code and you do a merge to see what the changes are and make a diff from that. You now literally have what changed between engine versions. Well, like you would expect with a new engine version, they've changed the API you use to access its code and they've restructured its different bits quite a bit, there are new bits, older bits have gone. You do the same technique as before, comparing your current main branch (NOT the development branch, guess why) to the code and oh dear there'll be merge conflicts everywhere, the engine is quite different. What to do?

At this point we are up to BEFORE the LY fork, at 3.8 whatever version. We can break the task down: some bits can be easily discarded, some bits will be added, but there'll be a chunk that will have to be integrated piece by piece preferably along structural lines and meanwhile you have to educate the developers who can't continue along the lines of continuous development/builds until these changes are made. You have to educate the developers on the changes to the API, you have to reassign developers to the bits that are changed/new, and you may have to take a deep breath and throw a lot of good code away simply because you don't have the time or resources to rebase everything. "Rebase" sounds simple but only works if your modifications are only in the parts of the new code that didn't change, and in the case of an engine only some of that will be true.

Ideally, you can give some developers the freedom to rebase their own development work on the new engine code, but in some cases you'll have to do the work yourself and get them to clone from that. And THEN it's back to making the builds work, having "rebased" on the new code and then you've got a main branch which is a fork off the engine code.

And THEN you have the LY fork. Take the above scenario and repeat, unless you're prepared to simply throw away all the previous work. Unless the LY fork is amazingly compatible which I do not believe for a second.

I want to point out that as far as I understand, game development is rarely this organized or as careful. An object hierarchy is fine for business software development but usually only gets as far as the UI and maybe file operations but everything else is written pedal to the metal good old functional programming and that is a dog to manage even with the help of a VCS. The whole point of object orientation was to make large projects even feasible but that breaks down with the way games work which do multiple things at the same time like a mini-OS, it's that complex.

So when Ben Parry tries to tell me that it was easy I'm just dumbfounded. Because he should know better. And this discussion is only applicable to if they did it as he claims, ripptide might be closer to the truth.

This is a good post. And only hints at how this is a perfect world scenario. Most branching seems to explode into hideous messes, and merging different branches becomes terrible.

I also totally fail to see how they could merge anything outside of even basic AWS support in when their whole system uses 64-bit position data. This is a huge core change. Unless Amazon is also magically 64-bit in the exact same way, seems like they'll either be lying, or starting over and dumping their major engine changes. Not to mention all changes built after the 64-bit change.

But really who knows. I'm of the mindset at this point that CIG did very little actual code changes and basically did modding. Very good modding, but modding none the less. We may never know the truth. :shrug:

# ? Dec 29, 2016 19:05

The Titanic: Sep 15, 2016; Unsinkable

AbstractNapper posted:

What Parry says, or what his latest iteration said (when I last read the Frontier forum thread, a few hours ago) is this:

They changed nothing with the switch. Their custom code remained intact.

How? They did not switch to LY proper. The LY fork is something still foreign to them and way off if they ever decide to merge with it.

What they did was "switch" to the 3.7 "history point" of LY, which is identical to CryEngine's 3.7 snapshot and is the point where StarEngine was forked out off. And they say "switch", but this amounts to a whole lot of nothing at this stage. Because it's pointless on its own (you literally do nothing --maybe a copy of a license and readme files-- and voila you've switched) and not an actual transition to anything different.

They had gained nothing out of the LY features, but maybe the license and the "right" to say they are on "LY" now... (which I don't think they can technically say that --but they can "sell" it as such apparently).

And they could do that sort of "switch" because, according to Ben, Amazon's license of the CryEngine is for source code that goes further back into the past of CryEngine than the 3.8.x point, where Amazon forked off and made their adjustments/ customizations. So it does include the 3.7 where they "switched".

What Parry's rough paint drawing shows is Star Engine remaining still forked off at the same point (no merging back with LY proper) and *essentially* in its own former branch, completely unaffected from the "switch". The only thing changing in the two drawings is the color of the "base" line which in the "before" is the CryEngine code, and in the after it is still the exact same CryEngine code (until LY's fork) now labeled "LumberYard legacy code or something".

Of course, It's unclear whether this circlejeck (possible but pointless) switch is what actually happened or what Barry thinks (or explained in his own mind to keep it sane) has happened. I sort of tend to believe him, because it matches the whole image of CIG being incompetent and selling this zero-sum switch as a new cooperation with Amazon that was "like for like" (no it wasn't).

This is a distinct possibility too. I mean if you go back far enough eventually every program in the same language is probably going to start with a hello world app. But by that token, Star Engine may as well be Windows 10, or whatever the hell else they want. Marketing gonna market. :homebrew:

# ? Dec 29, 2016 19:10

Beet Wagon: Oct 19, 2015

Lack of Gravitas posted:

In the neon-stained streets of 2190. the only value placed on a human life is a number in a spreadsheet

A squad of Stimperial Commandos relax until a new mission comes in

They go to the general vicinity to seek out their target

Hacking into the local datanet, they find a person of interest

Closer investigation shows a probable match

Enhance 78 to 105

Go left 45 and zoom

Enhance 11 to 66

Pan up 12 and zoom

Enhance and give me a hard copy

Target confirmed, they trail him to a nearby massage parlour

The target is acting erratically, never stopping in one place for more than a few seconds

The commandos have a discussion about how best to fulfill the clients request of "sending a message"

They come to an agreement that high explosive is relatively unambiguous

Landign sucsessfl commando o9

This post didn't get the love it so clearly deserves lmao

# ? Dec 29, 2016 19:11

Quavers: Feb 26, 2016; You clearly don't understand game development

Scruffpuff posted:

You have to think like a visionary if you're going to be able to see things that aren't there.

Star Citizen: You have to think like a visionary if you're going to be able to see things that aren't there

# ? Dec 29, 2016 19:11

The Titanic: Sep 15, 2016; Unsinkable

Second Sun posted:

Our galaxy is only 100,000 ly across. What the hell are they trying to say?

I think they are saying:

"We don't know what we're doing. Uh, buy ships!!!"

:homebrew:

# ? Dec 29, 2016 19:14

Quavers: Feb 26, 2016; You clearly don't understand game development

Mr.PayDay posted:

Nothing really matters, the days-since-CIG-hosed up-again-counter can be reset even weekly and the Cult will still spend 25-30 Million Dollars in 2017 after CIG just releases parts of 2.7-2.9 or even 3.0 and SQ42 Ep1, no matter how cut and broken this stuff is.
The PTU modules - no matter how limited they come - will be enough to satisfy the Cult, again.

Every part of alpha stuff released means keeping the dream alive and proving the Goons and Derek wrong.
Citizens will continue paying money for this. "2017 will decide their fate!" lol, no. The funding won't stop, the chairman will feeding Gamestar.de and Pcgames.de with exclusive jpegs and avis.

The entertainment will not stop, not in 2017

# ? Dec 29, 2016 19:14

Libluini: May 18, 2012; I gravitated towards the Greens, eventually even joining the party itself.

The Linke is a party I grudgingly accept exists, but I've learned enough about DDR-history I can't bring myself to trust a party that was once the SED, a party leading the corrupt state apparatus ...; Grimey Drawer

Mu77ley posted:

Hutton Orbital is 0.22Ly (6,784,404 ls) from the primary star in Alpha Centauri. That's a good 45 minute trek in supercruise.

Or longer if you let your ship sail past it

To be honest, if I were in the bubble and if you could get a Hutton Mug vanity item for placement in my cockpit, I would be tempted to make the journey. But as long as "Hutton Mugs" are just a rare item to sell for money, that's one time-wasting treck I won't do.

# ? Dec 29, 2016 19:14

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

Ben Parry posted:

1500 posted:
So you are saying that Starengine didn't diverge from Cryengine.

No. Good god, man, no.

StarEngine diverged from CryEngine at 3.7
LY and CE diverged from one another at 3.8
So, because 3.7 is less that 3.8, StarEngine's changes are as compatible with CryEngine as they are with Lumberyard.

If they'd diverged at 3.7, and StarEngine was based on 3.8, then StarEngine would be based on code that wasn't the same, and there'd be problems.

If you stay with CE, or you switch to LY, taking later updates takes work because of StarEngine's differences. Which is why my quote from yesteryear about not just doing big merges.

Stop blowing up crobblers story!

Ben Parry posted:

Any codebase can be expressed as a set of differences from another one. It's what gets put in patches, it's what gets stored in version control systems.
All of CIGs changes relative to CE 3.7 can be wrapped up like that, even though there's a lot of them.
You can apply those changes to anything else that has identical code to CE 3.7.
Since LY did not make any changes until 3.8, you can apply the changes to pre-3.8 Lumberyard. Note that I don't know what Amazon will actually do with the version numbers, but there'll be a point in their versioning system that lines up with CE 3.8.

Ben Parry posted:

Ok, I think your fundamental problem is that you don't know about version histories. Here's a thing that might help. Lumberyard isn't just a thing that got made at 3.8, it's a full history of every edit that's been made going back to... some point. Not sure how far, but well back. So no, it's not "an upgrade", it's a complete history which looks progressively more different from CryEngine after 3.8.

XK fucked around with this message at 19:24 on Dec 29, 2016

# ? Dec 29, 2016 19:21

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

Ben Parry posted:

bliss posted:
So CIG just went "ctrl C" from Cryengine 3.7 and then "ctrl V" into Lumberyard 3.7 (legacy support in Lumberyard 3.8) bringing over all the Starengine features. If CIG want any of the Lumberyard 3.8 features that will be extra work.

Am I understanding that right?

Basically yes, except you can just go "diff CryEngine 3.7 and Lumberyard 3.7" and paste that into StarEngine.
Taking actual features requires work, I don't know if that's included in the 2 days it took. Depends what features really.

Shaking my head.

Ben Parry posted:

Remus posted:
Nice picture ! And thx for the link, I'll sleep less ignorant tonight !

But there is something wrong in your picture, there is NO LY pre 3.8.1. Before that, it is still CE.

Amazon took the engine at its 3.8.1 version, and developed form there, before that there is no LY, just CE.

The first histogram shows accurately with green color that LY forked from CE at 3.8.1, that is true. the second though tries to tell me that LY = CE UNTIL 3.8.1, which is false.

LY is just a "fork", from CE, a modification. Before that point, there is no LY.

This is where you're mistaken, they have a license for that code, so their version history includes all those old bits.

XK fucked around with this message at 19:29 on Dec 29, 2016

# ? Dec 29, 2016 19:27

Beer4TheBeerGod: Aug 23, 2004; Exciting Lemon

Did Lumberyard even exist before 3.8?

# ? Dec 29, 2016 19:27

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

Beer4TheBeerGod posted:

Did Lumberyard even exist before 3.8?

"their version history includes all those old bits."

# ? Dec 29, 2016 19:30

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

Ben Parry posted:

sleutelbos posted:
Right. And the CIG changes are not influenced by the sugar. But now they have the sugar, they can start using it. The basic idea is that Amazon had better sugar on top of 3.7 than CT, so CIG decided they want to make future dishes using Amazon's sugar. I am sure Ben will confirm that if CIG plans to use a lot of the new sugar that will take a lot of time, depending on what they are taking. But making SC compatible with the new sugar isnt that much work, and thats what they have done.

No, making it compatible with the new sugar could take work, so we went back in time to when there was no sugar, and switched the dishes there.

Just all of this stuff deserves quoting. My mind is blown.

# ? Dec 29, 2016 19:32

Beer4TheBeerGod: Aug 23, 2004; Exciting Lemon

XK posted:

"their version history includes all those old bits."

So there's a version history that says Lumberyard 3.6, 3.7, etc?

# ? Dec 29, 2016 19:33

AbstractNapper: Jun 5, 2011; I can help

Beer4TheBeerGod posted:

So there's a version history that says Lumberyard 3.6, 3.7, etc?

Parry calls it that. But he admits it's essentially the CryEngine code. Because Amazon forked LumberYard and started adding and changing stuff at Cryengine 3.8.1.

# ? Dec 29, 2016 19:39

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

Beer4TheBeerGod posted:

So there's a version history that says Lumberyard 3.6, 3.7, etc?

According to Ben Parry, Lumberyard has rights to previous versions of CryEngine. Backdating to previous versions of CryEngine is completely identical to previous versions of Lumberyard.

# ? Dec 29, 2016 19:39

Young Freud: Nov 26, 2006

Combat Pretzel posted:

A cheap and easy trick would be to stretch the hitbox across the motion vector, according to the speed of the object.

True, but I also think that would get people crying about their "fidelity" and their "verisimilitude" if they got struck with a missile from 5-10 meters forward or behind the impact.

I was going to put in my post about that speed is probably perfectly fine for missiles striking another ship, but then we've seen screenshots of missiles going straight through the cockpit of a Constellation, so it looks like a common issue.

# ? Dec 29, 2016 19:43

XK: Jul 9, 2001; Star Citizen is everywhere. It is all around us. Even now, in this very room. You can see it's fidelity when you look out your window or when you watch youtube

Somebody is going to be yelling at Ben Parry in the near future.

# ? Dec 29, 2016 19:46

bird with big dick: Oct 21, 2015

spacetoaster posted:

Welp. I'm still a "backer". Should I play this?

You'd think CIG would realize that, especially after NMS, this is a really dumb thing to tout. You can have a bazillion gajillion googolplexillion kilometers of space (and did they really want to use linear distance? Kinda dumb) and since space is mostly empty it's completely meaningless. Filling it with PG garbage doesn't make it fun or meaningful if the PG garbage is, well, garbage.

What matters is how much unique content you have and how well that content is done. So far for CIG the answers to that are "very little" and "badly."

# ? Dec 29, 2016 19:48

bird with big dick: Oct 21, 2015

I don't know why you spergs are talking about the engine change like it could possible matter. All you have to do is take the Cryengine and layer the Lumberyard on top of it.

# ? Dec 29, 2016 19:50

Drunk Theory: Aug 20, 2016; Oven Wrangler

XK posted:

Somebody is going to be yelling at Ben Parry in the near future.

Not sure why. This is the most openly developed game in history. Which is why we needed to find this out from an non-engine team employee on a subforum for a competitors product.

Basically, what I'm saying is that no one will care except people who are already critical of CIG.

Drunk Theory fucked around with this message at 19:55 on Dec 29, 2016

# ? Dec 29, 2016 19:50

Lime Tonics: Nov 7, 2015; by FactsAreUseless

Ben Parry, trapped by his own hubris, digs a well to australia, turning the earth, inside out.

# ? Dec 29, 2016 19:54

Adbot: ADBOT LOVES YOU

# ? Apr 25, 2024 10:43

AbstractNapper: Jun 5, 2011; I can help

Drunk Theory posted:

Not sure why. This is the most openly developed game in history. Which is why we needed to find this out from an non-engine team employee on a subforum for a competitors product.

Basically, what I'm saying is that no one will care except people who already critical of CIG.

Yeah, I kinda agree with XK here. Parry is blabbing too much for his own good, and him being a member of the development team his quotes could be used in the press/ articles about Star Citizen (like that Kotaku one) which could potentially hurt the company.

I do hope that he'll keep his job and no one will care though, because so far he has provided gold.

# ? Dec 29, 2016 19:55

The Something Awful Forums > Archives > Comedy Goldmine > The Goodmine > Star Citizen: Death of a Space Thread?

«‹›6530 »