CRYENGINE 5 Legacy Deprecation Update

#1
Image
CRYENGINE versions 5.0 - 5.6.7 will be removed from GitHub and the CRYENGINE Launcher at the end of April. Find out more.


Following the launch of the CRYENGINE 5.7 Long Term Support Update, the most advanced version of the engine which will be supported going forward, we will be ending the distribution of legacy versions of CRYENGINE. CRYENGINE versions 5.0 to 5.6.7 will be removed from GitHub and the CRYENGINE Launcher at the end of April. We recommend upgrading to CRYENGINE 5.7 LTS, but whether you are upgrading or need to use older versions of the engine, please back up your projects now.

We have contacted representatives of all registered game projects via email about this change and to offer any assistance that may be required. If you are using an older version of the engine, please check your email. If you need to continue using a legacy version of CRYENGINE, want support, and are not registered already, please register now. Only games registered with us by April 30 will be considered for legacy support going forwards, and we will address requests on a case-by-case basis. Get in touch via the contact form.

We recommend upgrading as CRYENGINE 5.7 LTS will be the only publicly supported engine version. It has been designed for backward compatibility, so you shouldn’t have too much trouble migrating your projects.

We are now distributing source code and receiving bug reports via our new private repository on GitHub. As part of this process, we have disabled forking of the private repository, however, you can still clone the repository to your local development environments as usual. Existing forks of the public repository will continue to exist. One of the earlier forks will be selected as the new root parent from which all forks are derived – this is how GitHub works and we do not have control over this process. Whether you need source code or not, we kindly request that you register for access to CRYENGINE 5.7 LTS on GitHub as it is the prime spot to gather all bug reports and feedback. You can follow step-by-step instructions on how to request access here.

If you have any questions or queries about the update, tune in to our live Q&A with Jeremy Wade, SDK Product Owner, on our official Discord channel on April 25th, 5 pm CEST. There's still time to submit your questions on the dedicated AMA Discord Channel. If you can't make it to the Q&A session next Monday, we will publish it later on our YouTube channel. Take your chance to ask us anything about the update!

If you have questions or feedback about CRYENGINE, let us know in the comments, on the forum, or via Facebook and Twitter. You can pick up tips and tricks about our game development, ask questions, and more by joining our community and the CRYENGINE development team over on our official CRYENGINE Discord channel.

If you find a bug in the engine, please report it directly on GitHub, which helps us process the issue quickly and efficiently. Don't forget to subscribe to our YouTube channel, where we host a range of content, including tutorials covering all aspects of the engine and game design. Want to show your love for CRYENGINE? Pick up merch over on the official online Crytek Store.

Are you looking for your next career move? At Crytek, we value diversity. We actively encourage people from all backgrounds and experience levels to apply to our open positions, so join us over at LinkedIn and check out our careers page.

Who is online

Users browsing this forum: No registered users and 3 guests