Brian- Thanks for taking your time man! It means a lot to me, especially as I plan to switch to Cryengine in about 7 months. Keep up the work!

Hi everyone - this is Brian Dilg, the CRYENGINE Learning Manager here at Crytek. First of all, I'd like to thank you both for taking the time to post your insightful comments and suggestions. Your feedback is both perceptive and invaluable to us.

While I can't address development issues directly, I can tell you that the CRYENGINE team has have read your comments and is already working on these kinds of issues. What I can directly address are the learning materials that we offer. I started at Crytek on October 2, 2017, and my mandate can be described pretty simply: I'm here to make CRYENGINE as easy to use and as well supported as it is rewarding to master. Undoubtedly, we have in the past poured more resources into developing the engine and using it ourselves to build games than into providing an adequate, up-to-date supply of tutorials, documentation, and other learning options. That is going to change profoundly.

I'm confident that you'll see an immediate and substantial improvement in the substance, clarity, and technical quality of our learning offerings in the coming months, as well as the announcement of some major initiatives to address some of the issues you've raised. (If you happen to be subscribers, you can see the first webinar I produced with CRYENGINE programmer Alex Klinger on programming custom entity components in C++, released November 23: https://forum.cryengine.com/viewtopic.php?f=67&t=4409 If you're not, you need only wait until late December, when it will become available publicly after one month of exclusive access, as always.)

Among many other things, you will be seeing a whole suite of C++ tutorials, addressing some of the most technically challenging and rewarding aspects of working with the engine. But we will be working just as hard to ease the learning curve for beginners, and provide comprehensive expert guidance on best practices that address the concerns of every job in game development, from level designers to animators to sound designers.

In the meantime, I strongly encourage you to post requests for new tutorials as well as feedback on learning materials we've already posted in the Tutorials section of our CRYENGINE Educational Forum, where other community members can chime in as well: https://forum.cryengine.com/viewforum.php?f=11 That is the single most direct way for our educational and support team to get a sense of what your needs are and how well we're meeting them. While we do try to comb other platforms like Slack and Discord, it is just too time-consuming to comb through the hundreds of daily posts and try to summarize what amounts to requests or feedback with regard to learning assets.

Thanks again for your comments, and keep it coming!

Best,
Brian Dilg
CRYENGINE Learning Manager
Crytek

Silver008-> You are spot on correct, but I would like to add something: Unity is way more barebones than Cryengine. It's not like Cryengine is designed for First/Third person, it just has way more tools than other engines to do those tasks. When you start with a FPS or TPS in mind in both Unity or Unreal, you have to literally do everything from scratch. In Cryengine, you have a comprehensive framework already available to you to prototype your FPS/TPS game instantly. BUT, since that is the only thing that we can do with ease in Cryengine, that is what most of us end up doing, due to lack of docs, tutorials or just bad impressions, that Cryengine can't do, say, an RTS, which it can. Cryengine is way ahead on features, like, it had 2017 features back in 2012, that far ahead. Lighting is amazing. Etc, etc. You can do much more with Cryengine than Unity and Unreal combined, and I say this as a programmer and as a level designer. Never have I seen such good level design tools. Navmesh is automatically generated based on height and is auto-updated based on what differed in the map. Try that stuff in Unity. You have to do a ton of programming, which I can do, because I learned it. But Cryengine does it out of the box, in just 10 seconds.

I really, really love this engine, but you have to step up the tutorial quality. This one needs a lot of work, the video and audio quality alone is a big issue. The clarity and pace are another one. Dependency on proprietary plugins is a major blow, and also dependency on photoshop for simple texture import. The whole system could be refined.
I see things like this: Unity is copper, pretending to be gold. It gets the job done, and is mostly reliable to do the job, although sometimes copper is not what you need.
Cryengine is like Diamond covered in mud. You can see some of the diamond, but you have to clean the mud first. Clean the mud please, give us a nice and intuitive workflow, deprecate flash, integrate easier PBR workflow, make Cryengine more compatible with blender, cryblend just wont do.
Scripting doesn't have to be impossible(it is, there is no way to learn it, no comperhensive tutorials). Stick with C# and Visual Scripting, because they are the future. Document them, and make proper tutorials.
I am 100% certain that once this mud above, like lack of an intuitive workflow and proper docs and tutorials, is what this engine needs. When they are solved, I, and propably nobody will ever choose copper(Unity) to do a diamonds job.
A joyful fan of yours, Endi Haxhi.