I know there's an American flag beneath me... but I'm Canadian. We don't sue anyone, we ruin them with "Sorry, eh"Glad I didn't make any litigious comments
I know there's an American flag beneath me... but I'm Canadian. We don't sue anyone, we ruin them with "Sorry, eh"Glad I didn't make any litigious comments
In a nutshell, Crytek still has one or two claims they could pursue (like the Bugsmashers code) that probably have little chance of succeeding...BUT...will take more legal back and forth, cost time and effort, and "little chance of succeeding" does not mean 0%.This is normal procedural stuff. CIG agreeing to the extension is also normal.
There is a bit of a community misconception though, on potential copyright infringement. The 3 month window does not exist. I went back to 12 bugsmashers, and there is a lot of code displayed during 2016, and 2017. Yes, 2017. Switching to Lumberyard doesn't necessarily remove or limit risk - since Lumberyard is also based on code that Crytek claims is protected by their copyright. Displaying code though, doesn't mean there was a copyright violation.
Also, if it turns out CIG did make a few mistakes, this kind of thing happens all the time. It doesn't mean that CIG is bad. Just that they need to manage what gets published in videos a bit better. If they didn't breach any copyright, then no issue, and Crytek's Hail Mary fails - er - which also doesn't automagically remove their copyright protection.
The code we see on Bugsmashers is markup language, not Crytek source code from the engine.I went back to 12 bugsmashers, and there is a lot of code displayed during 2016, and 2017.
I'm predicting that both sides have more incentive now (for opposite reasons) to settle than they did before, and that in a couple weeks they will announce that they have reached some sort of settlement in which neither side will admit any wrong doing, and the amount will be confidential, etc. But I don't think Crytek can squeeze much more than $150k out of CIG. But nobody has to know how much/how little they got, and both sides can claim a moral victory. But more importantly, CIG can just put this behind them and move forward.
You see how meaningless it is to show source code like that. There were in fact, C++ classes that inherit from apparent Cryengine classes - and a lot of it. Everything I saw was an inherited class though, so not necessarily written by Crytek. And, yes there are potential issues with contractors working for CIG, especially FOIP, but we don't have any evidence from Crytek, just alligation in both source code and contractors actually. Fortunately that's not enough for a lawsuit.The code we see on Bugsmashers is markup language, not Crytek source code from the engine.
Correct me if Im wrong, but CIG sharing the actual Cryengine code with a 3rd party, that is issue being raised here, not some markup language from Marks bug hunting.
Correct.I think it's telling that Crytek hasn't pointed to a single incident of copyright violation yet.
Just means drink more beer as it will help you to understand... or not give a shit. Never did figure it out, which is why i say cheers.Stuff! Things! Happenings! What does it all mean?!
...but...but...but...DS clearly stated this is the final nail in the coffin for CIG!Spoiler:
CiG wins
Eventually he will be correct....but...but...but...DS clearly stated this is the final nail in the coffin for CIG!