Star Citizen Discussions v7

Perhaps - but with all the doubt and uncertainty that comes with such action, I wish the devs and their families all the best - especially at this time of year.

On the plus side, this case will probably take so long most of them will be in new jobs by the time anything happens...
But yeah, sucks for them. :(
 
Tell you this much - CryTek are going to be portrated as the reason for literally everything that goes wrong for SC from now on.

No S42 release date (which would be brave of them when it's the subject of a court case alleging that it's built on an unlicenced engine lol) - BLAME CRYTEK!

Core gameplay featured promised for 3.0 rolled back to 2019? BLAME CRYTEK!

CIG disolves into a puddle of acrimony and lulz with thousands of unfortunate gamers being left out of pocket? BLAME CRYTEK!

Lasting impact on the crowd-funding market causing fewer indie devs to be able to get their games to market? BLAME CRYTEK!

The eventual decline of western civilisation until we're all living in caves and making tools out of granny's leg bone? BLAME CRYTEK!



CIG response by the way:

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.
 
If CIG would have switched to let's say COBRA, I suspect CryTek wouldn't be able to touch them.

That would be a violation of the no-engine-change clause.

By the way, if they “[haven't] used the CryEngine for quite some time”, I rather wonder why there's a Crytek logo in what appears to be a dynamic list of partners page template… and why the Crytek partner logo links to a supposedly completely different engine.
 
Last edited:
Still - once they squash this "meritless" legal action - and get the bus fare to and from court back - they can carry on squashing all the bugs - meshing all the servers - writing all the netcode and generally saving all the PC gamers.

What's not to like?
 
That would be a violation of the no-engine-change clause.

By the way, if they “[haven't] used the CryEngine for quite some time”, I rather wonder why there's a Crytek logo in what appears to be a dynamic list of partners page template… and why the Crytek partner logo links to a supposedly completely different engine.

There's enough evidence that they still using CryEngine, just removing trademarks - this will be damning in court.

They shared code with third parties without permission. They failed to provide patches and improvements.

Yeah, they are truly screwed.
 
What's your take on this?

Erin Roberts said in June 2014: "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."

https://forums.robertsspaceindustries.com/discussion/comment/2895381/#Comment_2895381

They bought a source code licence. That's standard practice and applies when companies partner up with all kinds of vendors where the product is offering something that essentially provides a high amount of risk should the product fail (CMS, Web platforms, API, engines etc.)

Quite often there will be a standard set of licences that may include compiled core libraries. If the vendor goes out of business (very common) the clients using their platform for essential business are suddenly unable to upgrade essential parts of their platform. This makes it impossible to deal with larger organisations. The solution is to offer the complete source code under licence, this way if the vendor goes down the customer can continue to fork the original product as their own.

In the meantime, while the vendor is still active they are still under all of the terms & conditions agreed with the vendor. If it's a perpetual licence you still have to pay for it annually or whatever. If the agreement involved displaying the vendors product logo that still needs to be continued. Buying a source code licence doesn't mean you own the IP. You can't just fork it and sell it as your own super new engine just because you own a source licence.

I've worked on some pretty big web platforms using CMS products and the clients will typically buy the full source code licence.
 
Last edited:
Still - once they squash this "meritless" legal action - and get the bus fare to and from court back - they can carry on squashing all the bugs - meshing all the servers - writing all the netcode and generally saving all the PC gamers.

What's not to like?

It's the gift that keeps on giving.
 
In the meantime, while the vendor is still active they are still under all of the terms & conditions agreed with the vendor. If it's a perpetual licence you still have to pay for it annually or whatever. If the agreement involved displaying the vendors product logo that still needs to be continued. Buying a source code licence doesn't mean you own the IP.

This. Basically they bought source code. Yes, but that doesn't move copyright, doesn't invalidate CryTek IP, does not give permission to share it with third parties, and so on and so forth.

It is quite surprising CIG has so weak grasp about contracts and intellectual property.

Overall why lot of things can be weighted in court, CryTek have at least half of merits.
 
That would be a violation of the no-engine-change clause.

By the way, if they “[haven't] used the CryEngine for quite some time”, I rather wonder why there's a Crytek logo in what appears to be a dynamic list of partners page template… and why the Crytek partner logo links to a supposedly completely different engine.

I just pm'd a mate that link courtesy of Derek's Twitter, totally hilarious in the context of the complaint. 'OK we do display the Crytek logo on our website but only to link to Lumberyard' :D

As for your first line, that's what I meant earlier. If the defence against the content of the agreement is that it doesn't apply because they stopped using CryEngine, I can't wait to hear the defence against the clause that says they can't stop using CryEngine.

Got you covered. :D

Christ I can't rep you again either :D
 
Last edited:
https://kotaku.com/crytek-sues-star-citizen-makers-for-breaching-contract-1821269577?IR=T

Edit: Kotaku has the official response:

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.

Lumberyard is based on CryEngine though it has a different name.

I think it's about how much of the license agreement was violated before CIG switched to Lumberyard.
 
Last edited:
Still - once they squash this "meritless" legal action - and get the bus fare to and from court back - they can carry on squashing all the bugs - meshing all the servers - writing all the netcode and generally saving all the PC gamers.

What's not to like?

talking of which, the new Bugsmashers is up:
https://www.youtube.com/watch?v=Ru3zwjVMP3A&ab_channel=StarCitizen
jump to 51 seconds, and...

G5ccgDG.png


Well that's unfortunate.
 
Inb4 the "this is actually good news for Star Citizen" posts.

Holy moly, what a mess.

Pff. That one is easy.

Everyone knows that SC really needs a bespoke engine to work as advertised. With CryEngine out of the question, and Amazon likely to follow suit and bar CIG from using LY because of the mess they've caused, CIG will finally be forced free to design that proprietary engine that they needed all along, thereby making SC better than it could ever have hoped to be using those ancient outdated ugly publisher-associated hack engines.

Ergo ipso facto habemus papem romanes eunt domus this is good for Star Citizen, quod erat delendam.
 
Last edited:
Back
Top Bottom