Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Star Citizen and Squadron 42 are using Amazon’s Lumberyard game engine

venturebeat.com

Post reply on HN
Print view View original

11–20 of 120 posts

Re: Star Citizen and Squadron 42 are using Amazon’s Lumberyard game engine

#12

Post by quantumpotato_ »

caseysoftware wrote: post #8
gulaschadasical wrote: post #7

Apparently "The most open game development in history" involves briefly mentioning an engine / platform switch at 5pm on a Friday before christmas

Did you see their EULA change a while back? If you upgraded to the latest beta, you absolved them of all liability if they never deliver the actual product. This is a sinking ship, they just won't (publicly) admit it yet.. though a bunch of their staff jumped ship, so they realize it.

So if you don't update, then you can still hold them accountable? Do you know of people who are watching (maybe you didn't update?)

Re: Star Citizen and Squadron 42 are using Amazon’s Lumberyard game engine

#13

Post by tjalex »

caseysoftware wrote: post #8
gulaschadasical wrote: post #7

Apparently "The most open game development in history" involves briefly mentioning an engine / platform switch at 5pm on a Friday before christmas

Did you see their EULA change a while back? If you upgraded to the latest beta, you absolved them of all liability if they never deliver the actual product. This is a sinking ship, they just won't (publicly) admit it yet.. though a bunch of their staff jumped ship, so they realize it.

Are you serious? Have you actually even tried the game?

Re: Star Citizen and Squadron 42 are using Amazon’s Lumberyard game engine

#14

Post by scrollaway »

mikhailt wrote: post #6
scrollaway wrote: post #2

I didn't expect this, but it makes a lot of sense in retrospect. CIG had already hired a bunch of the crytek devs and invested a ton into their engine. They're also already pretty tightly coupled with AWS. I suspect this is the nail in CryEngine's coffin. I massively disagree with the decision, though. I think CIG could have taken CryEngine under their wing and continued developing it, releasing StarEngine (their for…

I don't see how fragmenting CryEngine benefits that much considering they're all on the same licensed CryEngine. Amazon paid $50m for the CryEngine and Amazon said Lumberyard is free to use with their AWS services. I think it makes sense for CIG to use Lumberyard's engine with AWS integration, especially it saves them a lot of money not licensing their own CryEngine fork and they're using AWS anyway.

CIG probably has more crytek talent than crytek themselves. It wouldn't be fragmenting, at this point.

Re: Star Citizen and Squadron 42 are using Amazon’s Lumberyard game engine

#15

Post by acemarke »

Given their comments about having rewritten over half of the original CryEngine codebase (including things like 64-bit map sizes, local physics grids, physically based rendering, and more), my guess is that this engine switch is primarily about licensing, networking, and use of AWS. They'd also stopped taking updates from CryEngine a while back, so at most they've swapped out some of their networking code.

Re: Star Citizen and Squadron 42 are using Amazon’s Lumberyard game engine

#16

Post by ComputerGuru »

Bombthecat wrote: post #5

When do they start with the "bottom line" and try to finish the game? A month more here, another month more there another switch of engine, concept,plan etc there.

They did the math and found out that they would have the least expenses if they didn't actually release.
Post reply on HN