Star Citizen Leaves Cryengine for Amazon Lumberyard
Events
Subscribe:  iCal  |  Google Calendar
Vancouver CA   12, Aug — 17, Aug
London XE   17, Aug — 20, Aug
Cologne DE   19, Aug — 21, Aug
Cologne DE   22, Aug — 26, Aug
Seattle US   28, Aug — 30, Aug
Latest comments
by chemo3000@hotmail.com
25 min ago

Great interview! I appreciate you make this kind of material that inspire and helps people in the same path :) Thanks 80 level and Mats! Ancelmo Toledo ;)

by earn to die
12 hours ago

Thanks for sharing.I found a lot of interesting information here. A really good post, very thankful and hopeful that you will write many more posts like this one. - earn to die

by Clinton Crumpler
21 hours ago

very nice!

Star Citizen Leaves Cryengine for Amazon Lumberyard
25 December, 2016
News
One of the biggest crowdfunding projects of our time, Star Citizen, is going through a massive technological change. A number of sources, including the official blog of Chris Roberts, report that from now on the game will be powered by Amazon’s Lumberyard. See UPD!

“We’ve been working with Amazon for more than a year, as we have been looking for a technology leader to partner with for the long term future of Star Citizen and Squadron 42. Lumberyard provides groundbreaking technology features for online games. Because we share a common technical vision, it has been a very smooth and easy transition to Lumberyard.”

Chris Roberts, Cloud Imperium Games

It is a big change, but we sort of expected something like that. There are a number of reasons to change the engine for Star Citizen. First of all, Crytek is going through a lot of changes right now. The company closed a number of studios, Crytek’s developers complain about horrible delays with salary payments. This doesn’t make it sound very reliable, and for a game, as massive as Star Citizen you do want to have a reliable partner. Secondly, Lumberyard’s render is actually Cryengine, because the company bought this technology a while back. It’s only natural to make the switch to this tech. And last but not least, Lumberyard comes packed with a ton of great cloud-based services from Amazon. This is an essential for Star Citizen, which promises access to a wide variety of virtual worlds for thousands of players online.

Star Citizen is a one of the biggest and most ambitious projects in game industry today. 350 people are working on it and we were fortunate to feature some of the great minds, which are creating the content for this massive beast. We really hope, that this game will make it and will be release sometime in the future.

UPD:

Looks like there was a mixup. The game runs on a modified engine of Cryengine, Lumberyard is there to make networking stuff work. Thx Thomas Ray.

We stopped taking new builds from Crytek towards the end of 2015. So did Amazon. Because of this the core of the engine that we use is the same one that Amazon use and the switch was painless (I think it took us a day or so of two engineers on the engine team). What runs Star Citizen and Squadron 42 is our heavily modified version of the engine which we have dubbed StarEngine, just now our foundation is Lumberyard not CryEngine. None of our work was thrown away or modified. We switched the like for like parts of the engine from CryEngine to Lumberyard. All of our bespoke work from 64 bit precision, new rendering and planet tech, Item / Entity 2.0, Local Physics Grids, Zone System, Object Containers and so on were unaffected and remain unique to Star Citizen.
Comments

Leave a Reply

3 Comments on "Star Citizen Leaves Cryengine for Amazon Lumberyard"

avatar
Richard Wulf
Guest
Richard Wulf

Switching engines 4 years into the project? Sounds like it’s fubar at this point. Looks like that Derek Smart guy was right.

ShikukuWabe
Guest
ShikukuWabe

Its far less substantial than it sounds, SC has been using its own engine for over a year now (nicknamed StarEngine) which is pretty much a reworked cryengine, all they did is partner with amazon to get the networking modules of their cryengine fork and the capabilities and advantages that comes with it due to AWS

wpDiscuz