South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Any chance of a public release of 3.0 before the end of the year?
We can hope but there seems to be quite a lot of work left. They will probably extend the PTU release to a lot more people though.
What is the PTU release?
Crytek sues Star Citizen studios over use of CryEngine (update)
As we explained in October, the Star Citizen project is actually an effort to create two unique AAA-quality games: an online multiplayer game referred to as the Persistent Universe and a single-player game called Squadron 42. Crytek said in its lawsuit that in continuing to use the CryEngine 3 for both products, CIG and RSI are in breach of contract.
In December 2016, CIG and RSI said they were moving off of CryEngine 3 in favor of Amazon’s Lumberyard product. But the complaint filed by Crytek says that’s not the case. Looking carefully at CIG and RSI’s own marketing materials, show lines of code on the screen that seem to indicate the games are running, at least partially, on CryEngine 3.
Making matters even more complicated is the fact that Amazon’s Lumberyard is, in fact, a fork of the CryEngine itself purchased by Amazon.
The lawsuit goes on to say that CIG and RSI improperly removed the CryEngine logo when the game boots up, and that the teams failed to properly disclose modifications to CryEngine 3 as part of their licensing agreement.
But the lawsuit doesn’t stop there. As we reported in 2016, CIG and RSI began selling two distinct games — Squadron 42 and the Star Citizen Persistent Universe. Crytek says that since both use the same code, that constitutes using the engine twice and represents a further breach of contract.
Not good. RSI is going to loose that fight
I read this this morning and it looks mostly like a quick cashgrab from Crytek than anything else. Erin Roberts confirmed on the forums they bought the engine (3.7), not just rights to use it, so that they can change things and implement different features. When Amazon bought the engine (3.8) from Crytek, Crytek lost prtty much all rights to argue anything around star citizen.
Not good. RSI is going to loose that fight
Not that easy - when RSI switched to CryEngine initially they signed some pretty intense contracts, including clauses preventing them from using a different engine (like Amazon's). Seems like that's just one of many contractual breaches - see 4 highlights below. They're going to get the sht kicked out of them in court if even half of the allegations are true.I read this this morning and it looks mostly like a quick cashgrab from Crytek than anything else. Erin Roberts confirmed on the forums they bought the engine (3.7), not just rights to use it, so that they can change things and implement different features. When Amazon bought the engine (3.8) from Crytek, Crytek lost prtty much all rights to argue anything around star citizen.
I think Crytek are having solvency issues which is why they are looking for a payday. Lawsuit seems pretty dodgy since they have moved to Amazon, however the main problem If foresee is Star Citizen pledged to not change engines and also topromote their use of CryEngine. Crytek claimed they invested significant resources of their own in assisting Star Citizen and them dropping the engine means that there will be no payback in terms of exposure for CryEngine.
I think Crytek are having solvency issues which is why they are looking for a payday. Lawsuit seems pretty dodgy since they have moved to Amazon, however the main problem If foresee is Star Citizen pledged to not change engines and also topromote their use of CryEngine. Crytek claimed they invested significant resources of their own in assisting Star Citizen and them dropping the engine means that there will be no payback in terms of exposure for CryEngine.
Erin Roberts
Addis
Posted: June 2014
S1GN3T | S1GN3T said:
Hi guys,
my question is about CryEngine 3 and the whole StarCitizen project. This week our German geming magazine 'Gamestar' reported that CryTek, developer of CryEngine 3, has been close to insolvency in April (due to bad sales of the last AAA games). Some ominous investor, probably Wargaming.net, will provide financial support. Just in case CryTek goes bankrupt and the support of the CryEngine ends, what would you do? Did you already evaluate this kind of risk? Would you support the engine by yourself, since a new netcode was written for the DFM?
I am concerned that this could have a bad effect on the project, if this case happens in a few years.
Regards,
Pascal
Hi S1GN3T,
We did an outright buyout of the engine last year and have the source code, so while we hope all the noise about Crytek blows over, as they are great partners and friends to the project, if the worse happened we would be ok, as we’ve already branched the engine and have a large team that is adding features and supporting it every day here at CIG. So even in the worst case scenario we should be fine, but obviously we hope it does not come to that.
Cheers,
Erin
When asked to comment by Kotaku, CIG sent over a statement: “We are aware of the Crytek complaint having been filed in the US District Court. CIG hasn’t used the CryEngine for quite some time since we switched to Amazon’s Lumberyard. This is a meritless lawsuit that we will defend vigorously against, including recovering from Crytek any costs incurred in this matter.”
CIG declined to answer follow-up questions about specific complaints in the suit.
Lawsuit in link
Features
Although CIG is very open about their development process, not all details on internal processes and work on the engine are released to the public. The following list contains features that are described in interviews, Monthly Reports or dev comments. The names can differ from the actual name internally used and the feature funtionality should always be considered as not fully accurate. Additionally, some are already integrated CryEngine 3.8 and/or Lumberyard features
Amazon’s releasing their very own game engine. Lumberyard, as they call it, is based on Crytek’s famous CryEngine, and can be used to develop games for both PC and consoles. It’s also free to download, and comes with “no seat fees, subscription fees, or requirements to share revenue.”
Fees come in only, as Lumberyard’s official page notes, if the game takes advantage of the engine’s integration with Amazon Web Services for multiplayer.
While the engine is based on Crytek’s CryEngine, which Amazon licensed last year, Lumberyard will, as general manager Eric Schenk put it (via Gamasutra), “go in [its] own direction.” He added that at launch, the engine already has components that are not based on CryEngine, including low-latency networking code and “an entirely new asset pipeline and processor.”
It may be the case that Crytek are having solvency issues, but this is what was stated by Erin Roberts,
https://forums.robertsspaceindustries.com/discussion/comment/2895381/#Comment_2895381
Kotaku,
https://kotaku.com/crytek-sues-star-citizen-makers-for-breaching-contract-1821269577
More on CIG's Star Engine,
https://starcitizen.tools/Star_Engine
On a side note, Crytek is licensed to Amazon, and according to Kotaku,
https://kotaku.com/amazon-releases-its-own-game-engine-for-free-1757995787
Generally, though Crytek may seek a payday, it seems to be due to negligence on CIG's part.
Bought and licensed, not quite the same thing when it comes to use. I think Erin Roberts, like the previous debacle, talked too much when she said they did an 'outright buyout'.
Interesting post thanks, puts things into perspective. I'm also starting to think Erin might have talked too much. But we will see when more info floats to the surface
As long as my money put into the game spews out a complete product, one day, I’m happy.
Is anyone playing 3.1?
I tried it and it was a lot better than before but still lags every now and then, but I dont really have a beast of a machine at the moment. I think people with 16GB RAM or more will have a better time