Star Citizen: Death of a Space Thread?

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

«‹›6530 »

Lime Tonics: Nov 7, 2015; by FactsAreUseless

# ? Dec 29, 2016 19:58

Adbot: ADBOT LOVES YOU

# ? May 15, 2024 23:45

Inkel: Feb 19, 2004; College Slice

AbstractNapper posted:

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.

I doubt Parry will catch any public flak over this. CIG has a tried and true method for when an employee does/says/writes something they shouldn't have. Basically just tell them to shut up and then ignore the matter until the backers forget about it and/or write their own headcannon about what was said.

# ? Dec 29, 2016 19:59

Lime Tonics: Nov 7, 2015; by FactsAreUseless

There is no difference between any engines at all.

You can take unity code and tree branches and set aflame an office building and in that mess you can save some whales.

easy peasy.

# ? Dec 29, 2016 20:11

intardnation: Feb 18, 2016; I'm going to space!

Fat Shat Sings posted:

i know we tend to scrape the bottom of the comedy barrel here at the star citizen thread but this is legitimately funny.

"If your car starts as a blank blueprint and my car starts as a blank blueprint we can safely say that your Honda civic is just a modified Lamborghini with no extra work."

whoever said this guy was just a lighting peon with no idea what he is talking about was pretty much 100% correct.

"Calling my Honda a Lamborghini is easy, actually converting it into a Lamborghini conceptually is hard. "
"converting it into a Lamborghini after construction starts is extra hard"
"Whats been done is just calling my Honda a modified Lamborghini"
"So it wasn't hard"

well an nsx is pretty close but not quite. you could up the HP etc and get something theoretically that could be as good if not better for a cheaper price.
When the 1st launch it made Italians take notice and adapt and the world is better for it. (honda is acrua)

the old one that made waves

add a twin turbo to the sexy beast and you dont need a diablo really or the repair bills.

So in essence it is as good as a lambo - yup 100%. maybe you meant kia?

intardnation fucked around with this message at 20:27 on Dec 29, 2016

# ? Dec 29, 2016 20:22

Chalks: Sep 30, 2009

Beer4TheBeerGod posted:

Did Lumberyard even exist before 3.8?

No, it did not.

Amazon built a house on a hill. CIG built a house on a hill. CIG claims their house is based on Amazon's because at some point in the past, they were in the same state.

The fact that, at that point, neither CIG nor Amazon had done anything at all is apparently a minor detail.

It's stupid and no developer in their right mind would say that Cryengine 3.7 is "Lumberyard Legacy". You might as well say that Crysis 2 was built on Star Citizen legacy code. It's a loving retarded, meaningless thing to say.

# ? Dec 29, 2016 20:25

Tijuana Bibliophile: Dec 30, 2008; Scratchmo

Iglocska posted:

A better allegory would be that Cate took a picture of her face on 03/07 and sent it off to a surgeon to see what he could do with her based on the picture. The surgeon got to work on photoshop to make the adjustments that she should expect.

At the same time she took chainsaw and a sledge hammer to her face to "improve it".

The surgeon in the meanwhile died of a terrible case of lovely finances, but to Cate's surprise a second surgeon also took a copy of the picture she sent in and created a photoshopped image of what he could sculpt out of her. She was absolutely enthusiastic about the result and partially due to the massive brain damage caused by the sledge hammer, she exclaimed to the world that she switched surgeons and that she now looks like the picture the surgeon created.

# ? Dec 29, 2016 20:30

Lime Tonics: Nov 7, 2015; by FactsAreUseless

I'm ben, and i'm rubbing two sticks together to spin gold wire.

It has to be true, because it is true.

So sayeth the crobbers.

# ? Dec 29, 2016 20:30

intardnation: Feb 18, 2016; I'm going to space!

Chalks posted:

No, it did not.

Amazon built a house on a hill. CIG built a house on a hill. CIG claims their house is based on Amazon's because at some point in the past, they were in the same state.

The fact that, at that point, neither CIG nor Amazon had done anything at all is apparently a minor detail.

It's stupid and no developer in their right mind would say that Cryengine 3.7 is "Lumberyard Legacy". You might as well say that Crysis 2 was built on Star Citizen legacy code. It's a loving retarded, meaningless thing to say.

that is why they are saying it. because they can and the spergs eat it up and keep spending money while they delay the project longer and keep making $$. All the while the ship sinks. Mind you Ben, Hobo et all dont help
with the weight.

# ? Dec 29, 2016 20:32

The Titanic: Sep 15, 2016; Unsinkable

Sillybones posted:

I will poorly give my layperson explanation:
When we say 64-bit here we mean 64-bit positions of entities in the SC engine. A 64-bit engine, like Skyrim, is referring to move from 32-bit to 64-bit codebase so you can use more ram and such.

https://tomforsyth1000.github.io/blog.wiki.html#%5B%5BA%20matter%20of%20precision%5D%5D stuff. From Derreks blog it looks like he thinks they went with some sort of kinda-fixed-point solution which I think is only natural. It would definitely suck to try move an established engine to use 64-bit positions as it could touch from how you save/load data, to optimisation and packing problems, right down to the rendering side of things. Certainly not impossible and definitely something you would need in a large scale game world. If they did it for real I can't imagine merging with another engine fork is anything but a nightmare.

Seems the best explanation for everything. They have changed nothing. Maybe the AWS integration completely separate from the whole engine change was the thing that took a year?

Sounds good to me, friend.

I'm not a game engine writer so I assumed you couldn't just half do 64-bit architecture. But it still seems like a core change, since positioning is pretty important to everything, including rendering orders and such. But I'll leave that for the big kids in the know to hash out.

# ? Dec 29, 2016 20:34

Tijuana Bibliophile: Dec 30, 2008; Scratchmo

I think what happened is CIG got all sweaty knowing they couldn't show any progress with 2.6, and somebody figured out the genius solution would be upgrading the servers to reduce latency. Somebody got on the phone with Amazon and negotiated a deal where they got slightly better servers for the same cash, while whoever's in charge of Lumberyard can finally say one developer's using their lovely engine. Code is unchanged of course.

# ? Dec 29, 2016 20:34

ripptide: Jul 28, 2016

Beer4TheBeerGod posted:

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

I don't think there is a version history that specifically says "Lumberyard 3.6" etc, what he seems to be implying is that since LY was based off 3.8, it automagically becomes backwards compatible with all previous 3.x CE versions, and thus inherits all those versions. Pure bollocks, if I understand what he's babbling about correctly. It may be possible for core functions, but that kind of backwards compatibility is never a guarantee, and usually requires extensive testing. Especially when you consider that LY specifically did away with all the network layer in CE, which means anything written in a previous version of CE that makes a network call using the old function calls would most assuredly throw an error, and so would require additional error checking and redirecting to the "newer" network code.

# ? Dec 29, 2016 20:35

Tijuana Bibliophile: Dec 30, 2008; Scratchmo

Scruffpuff posted:

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.

Made me smile

I would have liked to see some IBM mainframes in there as well

# ? Dec 29, 2016 20:36

D_Smart: May 11, 2010; by FactsAreUseless; College Slice

XK posted:

quote:
https://forums.frontier.co.uk/showthread.php/259596-The-Star-Citizen-Thread-v5?p=4943682&viewfull=1#post4943682
Ben Parry posted:
I think I explained further up, but it's probably buried.
If your modifications are relative to 3.7, and their modifications start diverging at 3.8, then switching from "modded 3.7 CryEngine" to "modded 3.7 Lumberyard" is no changes, because you're at a point before theirs diverged.
===
https://forums.frontier.co.uk/showthread.php/259596-The-Star-Citizen-Thread-v5?p=4943734&viewfull=1#post4943734
Ah, I think I see your misunderstanding. You think SC has switched from StarEngine to Lumberyard. Actually StarEngine has switched from being a modification of CryEngine to being a modification of Lumberyard.
Can you see that because Lumberyard and CryEngine split away from one another at 3.8, if you rewound either of them to 3.7, they'd be the same as each other?
Right, so with StarEngine branching off at that shared 3.7 point, can you see that it doesn't matter which one it's a modification of?

Oh. He actually said this.

I thought the reasonable assumption was that they were using new Lumberyard stuff for Star Marine, and their existing code for the rest. But this, wow. I would feel like a completely immoral sociopath by telling my $140m backers that I switched engines, without detailing that the change is currently only licensing related, and almost no functionality or implementation (code) has changed.

I'm still hesitant to believe that's what actually happened.

Yes, that's what the furor has been about. Which is precisely why I wrote the blog, and highlighted this in it.

Beer4TheBeerGod posted:

Okay, let me see if I understand this.

Lumberyard is based off of CryEngine 3.8, which is based off of CryEngine 3.7.

StarEngine is based on CryEngine 3.7.

Therefore StarEngine is Lumberyard.

Yes. And technically Star Marine is same as SQ42.

Scruffpuff posted:

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 20:36

Tijuana Bibliophile: Dec 30, 2008; Scratchmo

Sappo569 posted:

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

Please state whether it's 5000 degrees Celsius or 5000 Kelvin

this is important

# ? Dec 29, 2016 20:37

Lime Tonics: Nov 7, 2015; by FactsAreUseless

Close up shop till the 3rd of january, oh and have a developer/insane man explain code.

ship sale in 2 weeks.

it's fine.

# ? Dec 29, 2016 20:42

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

D_Smart posted:

Yes, that's what the furor has been about. Which is precisely why I wrote the blog, and highlighted this in it.

I read your blog, and it wasn't as clear as it should've been. In your blog you stated something about Ben Parry backdating the engine switch, but his claims didn't become clear to me until I actually read his posts of the Frontier forums.

That dumb mspaint of branches was nowhere near as clear as his posts. That mspaint thing only baffled me.

You need to screenshot all those posts and include them in your blog.

# ? Dec 29, 2016 20:50

Drunk Theory: Aug 20, 2016; Oven Wrangler

XK posted:

I read your blog, and it wasn't as clear as it should've been. In your blog you stated something about Ben Parry backdating the engine switch, but his claims didn't become clear to me until I actually read his posts of the Frontier forums.

That dumb mspaint of branches was nowhere near as clear as his posts. That mspaint thing only baffled me.

Well, from the standpoint of clear arguements, ya he'd want to do that. But I got some respect for Dsmart for creating that baffling MSpaint thing. It's great low effort trolling which I appreciate more than blogs.

# ? Dec 29, 2016 20:52

Chalks: Sep 30, 2009

D_Smart posted:

Yes. And technically Star Marine is same as SQ42.

Star Citizen is based on legacy code from failed Korean MMO Aion Online

# ? Dec 29, 2016 20:53

Cao Ni Ma: May 25, 2010

Chalks posted:

Star Citizen is based on legacy code from failed Korean MMO Aion Online

I'll have you know failed korean MMO Aion makes more money than just about every western MMO that isnt WoW.

# ? Dec 29, 2016 21:01

Tarquinn: Jul 3, 2007; I know I’ve made some very poor decisions recently, but I can give you
my complete assurance that my work will be back to normal.; Hell Gem

Who the gently caress is Ben Parry?

# ? Dec 29, 2016 21:11

Rad Russian: Aug 15, 2007; Soviet Power Supreme!

CIG should just post this on their site: Happy Holidays Citizens! Would you like more in depth information on our recently announced engine switch? Head down to the Frontier forums! Our expert developer Ben Parry is there 24/7 waiting to answer any of your questions.

# ? Dec 29, 2016 21:11

Drunk Theory: Aug 20, 2016; Oven Wrangler

Tarquinn posted:

Who the gently caress is Ben Parry?

CIG employee who posts over on the Frontier forums. I haven't really focused what his specialty is, but I think it's lighting? Either way, he's commenting on this "engine change", and providing clarification that nothing actually changed.

# ? Dec 29, 2016 21:12

Chalks: Sep 30, 2009

Cao Ni Ma posted:

I'll have you know failed korean MMO Aion makes more money than just about every western MMO that isnt WoW.

Lets just say failed in the west at least

It was an Aion goon who bought me my account on this site many years ago. I can't remember what his name was though, sadly.

# ? Dec 29, 2016 21:19

D_Smart: May 11, 2010; by FactsAreUseless; College Slice

Rad Russian posted:

CIG should just post this on their site: Happy Holidays Citizens! Would you like more in depth information on our recently announced engine switch? Head down to the Frontier forums! Our expert developer Ben Parry is there 24/7 waiting to answer any of your questions.

Man, that's just mean :grin:

# ? Dec 29, 2016 21:25

D_Smart: May 11, 2010; by FactsAreUseless; College Slice

Drunk Theory posted:

CIG employee who posts over on the Frontier forums. I haven't really focused what his specialty is, but I think it's lighting? Either way, he's commenting on this "engine change", and providing clarification that nothing actually changed.

He's a low level effects programmer. And basically clueless.

# ? Dec 29, 2016 21:26

Dongicus: Jun 12, 2015

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 progarmming 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.

did you just seriously loving say that? are you stupid AND retarded? gently caress off. I can't believe this line of reasoning is considered valid. I mean how cognitively dissonant and occamz razorly can you be?

"nized 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 proga"

seriously, fucko? seriously :allears:

Man I bet you're the kind of guy who's like

"riginal 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"

jesus what a fruitcake! you actually said that! how about you peep the goddamned numbered graph in the OP next time you ordain spewing this unrepentant squalid mess.

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).

Are you retarded?

# ? Dec 29, 2016 21:26

Crazy_BlackParrot: Feb 1, 2016; Christ Roberts is way better than toilet lord...

Is it possible CIG found out that they completely screwed up their engine and just used lumberyard as an excuse to start from scratch?
Basically throwing out 4years of development?

# ? Dec 29, 2016 21:27

D_Smart: May 11, 2010; by FactsAreUseless; College Slice

Crazy_BlackParrot posted:

Is it possible CIG found out that they completely screwed up their engine and just used lumberyard as an excuse to start from scratch?
Basically throwing out 4years of development?

Yes, it's quite possible. Which means that they get to dump 4 years and million dollars worth of custom code, to use Lumberyard and a merge of their 64-Bit positioning hack.

# ? Dec 29, 2016 21:33

Tarquinn: Jul 3, 2007; I know I’ve made some very poor decisions recently, but I can give you
my complete assurance that my work will be back to normal.; Hell Gem

Drunk Theory posted:

CIG employee who posts over on the Frontier forums. I haven't really focused what his specialty is, but I think it's lighting? Either way, he's commenting on this "engine change", and providing clarification that nothing actually changed.

Exciting.

Thanks.

# ? Dec 29, 2016 21:37

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

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

You mean this thing?

# ? Dec 29, 2016 21:48

sorla78: Oct 11, 2012; EAT THE PAIN AWAY!

# ? Dec 29, 2016 21:53

Beer4TheBeerGod: Aug 23, 2004; Exciting Lemon

Drunk Theory posted:

CIG employee who posts over on the Frontier forums. I haven't really focused what his specialty is, but I think it's lighting? Either way, he's commenting on this "engine change", and providing clarification that nothing actually changed.

He's also undercutting everything Chris Roberts has said, and providing a level of honesty that is clearly not in CIG's interests.

I give him until January 4th.

# ? Dec 29, 2016 21:54

Crazy_BlackParrot: Feb 1, 2016; Christ Roberts is way better than toilet lord...

D_Smart posted:

Yes, it's quite possible. Which means that they get to dump 4 years and million dollars worth of custom code, to use Lumberyard and a merge of their 64-Bit positioning hack.

I think it was Melkor who said that it might also be a budget related move.
Because basically now they get the same engine for free instead of directly via Crytek who asks muchos dollaz for it.

So I adjusted my personal theory.

1) they hosed up the engine, beyond repair discovered 64bit isn't working.
2) started from scratch, hence why SM is semifunctional
3) Since, they restarted from scratch, they are using lumberyard now because its free. instead of paying license fees to crytek.

I love game development.

# ? Dec 29, 2016 21:56

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

Drunk Theory posted:

Well, from the standpoint of clear arguements, ya he'd want to do that. But I got some respect for Dsmart for creating that baffling MSpaint thing. It's great low effort trolling which I appreciate more than blogs.

Ben Parry created that picture.

https://forums.frontier.co.uk/showthread.php/259596-The-Star-Citizen-Thread-v5?p=4943894&viewfull=1#post4943894

Ben Parry posted:

Ok, I made a picture...

# ? Dec 29, 2016 21:57

The Saddest Robot: Apr 17, 2007

TBH getting the engine free from Amazon/Lumberyard instead of having to pay future royalty + licensing fees to Crytek sounds like a good business reason for doing a fake switchover.

# ? Dec 29, 2016 22:07

D_Smart: May 11, 2010; by FactsAreUseless; College Slice

Crazy_BlackParrot posted:

I think it was Melkor who said that it might also be a budget related move.
Because basically now they get the same engine for free instead of directly via Crytek who asks muchos dollaz for it.

So I adjusted my personal theory.

1) they hosed up the engine, beyond repair discovered 64bit isn't working.
2) started from scratch, hence why SM is semifunctional
3) Since, they restarted from scratch, they are using lumberyard now because its free. instead of paying license fees to crytek.

I love game development.

It's none of that. Their CryEngine license was royalty free.

https://twitter.com/dsmart/status/814579023586140162

They can

1) completely dump their Star Engine abomination

2) merge their game elements which are obviously created on top of CryEngine

3) merge in their 64-Bit position hack

4) win

Then, with AMZ doing all the heavy lifting in terms of maintaining the LY engine, they get all the things* I listed in my blog. Then they can down size drastically.

*
- On-going updates to CE 3.x kernel
- XBox One and PS4 support
- VR support
- DX12 support
- Vulcan support
- End user game modding support
- End user private server support
- Robust client patching support
- I am hesitant to add EC2 here because Compute is comparatively priced; though Google traditionally keeps losing cloud business to Amazon due to infrastructure, robust implementation of cloud tech, and because well, for the most part, given the choice between Google and Amazon, my guess is Amazon will run out of tents to house defectors
- Amazon devs doing most of the heavy lifting in on-going support for the engine; seeing as Chris Roberts has burned the bridge with CryTek

# ? Dec 29, 2016 22:19

Beer4TheBeerGod: Aug 23, 2004; Exciting Lemon

The Saddest Robot posted:

TBH getting the engine free from Amazon/Lumberyard instead of having to pay future royalty + licensing fees to Crytek sounds like a good business reason for doing a fake switchover.

Especially if CryTek doesn't have the lawyers to dispute it.

# ? Dec 29, 2016 22:19

DrBall_MD: Oct 11, 2016

moveable shape posted:

this is what understanding game development looks like

This is what a crumpled piece of paper found jammed underneath a piss-stained mattress in Broadmoor looks like.

# ? Dec 29, 2016 22:20

D_Smart: May 11, 2010; by FactsAreUseless; College Slice

https://twitter.com/dsmart/status/814585558777335809

# ? Dec 29, 2016 22:37

Adbot: ADBOT LOVES YOU

# ? May 15, 2024 23:45

Viscous Soda: Apr 24, 2004

Sabreseven posted:

I had to check, it's not actually a photoshop, it's on the site clear as day.

I wonder how they worked that figure out, it's in linear kilometres and not 'squared' or even 'cubed', yet how do they make such a claim when they know full well 99.9 of those 100 are full of empty space and nothing to find?

I'm leaning towards thinking "false advertising".

1 x sextillion km = 1,000,000,000,000,000,000,000km = no way they made an in game map 100x larger than that.

Wait... that's actually not too good. Assuming that they meant cubic km, that'd make a cube 46,418,888 km per side (cube root of 100 sextillion). Now let's halve that distance to get to the center, and you end up in the center of the cube with 23,207,944 km in every direction (assuming you traveled along a axis of course). That's just 0.155 au, that's not even enough to fit the orbit of Mercury in; It's not even enough to fit the Kerbol system in (Duna's apoapsis is 21,783,189 km, so it would just barely fit in).

Unless I made a mistake in my math.

Edit: First cat picture from my pictures directory tax:

Viscous Soda fucked around with this message at 23:17 on Dec 29, 2016

# ? Dec 29, 2016 23:15

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

«‹›6530 »