If you believe this content violates Code of conduct please provide details below. All reports are strictly confidential
CRYENGINE versions 5.0 - 5.6.7 have been removed from the CRYENGINE Launcher. CRYENGINE 5.7 LTS Hotfix inbound!
As previously communicated in our blog and via email to all registered users, we have now ended the distribution of legacy versions of CRYENGINE following the launch of the CRYENGINE 5.7 Long Term Support Update. CRYENGINE 5.7 LTS is the most advanced version of the engine that we will support from now on. It is designed for backward compatibility, but we recommend that you back up your projects before upgrading to it regardless.
New users will not be able to download legacy versions of CRYENGINE from the website and the CRYENGINE Launcher. Source code for CRYENGINE 5.0 through to CRYENGINE 5.6.7 will be removed from GitHub on Wednesday. If you are using a legacy version of CRYENGINE, please back up your projects as the ability to repair and update your builds for engine versions older than CRYENGINE 5.7 LTS will cease at the end of the month.
CRYENGINE 5.7 LTS will receive its first Hotfix on Wednesday [Update: The update has been pushed to CW20]. We'd like to thank you all for your feedback on the latest version of the engine so far, and please keep it coming. You can submit your feedback on our new private repository on GitHub, where you can also access CRYENGINE 5.7. LTS source code. Whether you need source code or not, please register for access, and register your projects with us. This will help us collate your feedback and bug fix requests and better support you as your progress with your projects.
You can follow step-by-step instructions on how to request access source code here.
Please note that we have disabled forking of the private repository. However, you can still clone the repository to your local development environments as normal. Existing forks of the public repository will continue. 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.
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 to 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, and we actively encourage people from all kinds of backgrounds and experience levels to apply to our open positions, so join us over at LinkedIn and check out our careers page.