[=vblanco;62617]
Interesting, the “Cryengine” thread in unity forum got like 3 pages, and its now burrowed, people there dont even take it seriously. Meanwhile, the Ue4 thread there got to almost 90 pages and they had to close it.
I expected little from them, and i was right. Its basically the exact same freesdk you had before, but now paying.
[/]
The licensing agreement is a no go for anyone that is honestly trying to release a product with the engine. Comparing the EULA for UE4 and CryEngine shows just how one sided the license you are agreeing to is:
UE4
“Epic owns all title, ownership rights, and intellectual property rights in the Engine Code and Assets. You own all rights in the Products you develop under the License, other than the Engine Code and Assets, Third Party Software, and any Submissions.”
Clear, simple and to the point - your IP is your IP - Epic’s IP is Epic’s IP - Third Party IP is Third Party IP.
does not exist in the CryEngine EULA. You are afforded zero protections for what you are bringing to the table i.e. your code and assets.
I do not even want to get into how difficult it is to do anything other than a very basic FPS with what they provide you as it remains a giant black box, (no source code where it actually matters exactly the same as the FreeSDK) which is horrendously documented, but suffice it to say nothing has changed other than PBS.
If I were a betting man I would say wait and see what happens when there is an influx or horribly designed output that comes from their EaaS and Crytek steps in and says: “No, forget it you’re not releasing and have no rights to do so!”