lavizh wrote:No point in publishing documentation for offline use since they cant be updated when there is a chance. People will end up with outdated docs quickly.

If you look at the roadmap the restructure isn't done yet (Under Prototyping).
https://www.cryengine.com/roadmap

The Rework is still in green light for 5.6

Thank you for answers, yes , I check roadmap every week , you are right , but I see a few news about cryengine, news is few , I love , I want more news of cryengine 5.5 and c# syntax.

Is possible , we see add component c# at an entity? Just like unity component ? I checked lumberyard 1.11 , also lumberyard is like unity with add component panel with lua component , we can control every entity independent of a number of lua scripts to added.

please here , If a person/persons of ce team know , please tell us more details of c# component/components at one entity , also please tell us more details about new docs in future , I understood here is a few shots of 2 news (last news) with WIP docs/pictures.

Thank you so much

Wait a sec... does it means CryEngine is going to be documented *for real* now?!

Could some CryTek engineer make a blog post about the internals of the engine?!
Explaining a bit on how the engine handles entities, properties and values...

Like this extremely helpful blog post example from Unreal 4 developer:
https://www.unrealengine.com/en-US/blog ... reflection

@This topic

Cry-Chris wrote:A good place to start would be the CRYENGINE videos that you can find here:
https://www.cryengine.com/tutorials/getting-started
They are very easy to follow and very user friendly.

No, it's not easy to follow nor user friendly.
For example:
Jack is a new guy and just download CryEngine, he like to know something about sound. He goes for this first tutorial from the Audio tutorial

So he sees that he needs to download Sample Assets (v8 396.78MB)
After downloading, he spends some time trying to find PIT_BLANK.cry, eventually he finds it at: ".\SAMPLE_v8\CONTENT_EXAMPLES\GameSDK\assets\levels\contentExample\PIT_BLANK\PIT_BLANK.cry", but then doesn't know what to do with it. So he can't process to follow the video and gives up.

Maybe these tutorial is more user friendly than the past, I appreciate that you made an improvement, but you still need to push forward, imagine you as a newbie, not a familiar user when designing these beginner's tutorial.

So I really hope that the tutorial can be like this Unity's tutorial for beginner: They give a project for the tutorial series (and update the project when it's outdated), they give the slide, they give the transcript for non-English speaker, they give related tutorials.


Instead of giving one big package for all the tutorials, make small projects for each tutorial/tutorial series. What's the newbie want is "one-click-setup". There are a few disadvantages of one big package for all tutorials that I guess you already know:
1. User take long download time.
2. Confuse user.
3. hard to setup.
4. Require user download the whole package when there is an update for 1 outdated asset (If there's an update for asset)
If you don't have time to break the big package now, at least give description (what is this, how to set up) for the content in the big package, but I still prefer small projects for each tutorial series.

I see that the tutorials just starts out with the pre-setup scene (for example: https://youtu.be/GJDs5YxhgPU), how the user know what's that come from, so it should be a good idea to tell user in the video's description where user can download the tutorial project (I said project, not asset, project contains asset and project can be clicked and played).

If you can't provide transcript for now, link the video from Youtube instead of Vimeo (don't get me wrong, I also love Vimeo, but I don't see Vimeo has auto-generated subtitle), so at least user has auto-generated subtitle. I see you've already uploaded your tutorial to Youtube.

@HDN Thank you for taking your time to give us feedback.
We do try to improve where we can so feedback is important to us.
However there is something we would like to point out in regards to your comment.

HDN wrote:@This topic
Jack is a new guy and just download CryEngine, he like to know something about sound. He goes for this first tutorial from the Audio tutorial

So he sees that he needs to download Sample Assets (v8 396.78MB)
After downloading, he spends some time trying to find PIT_BLANK.cry, eventually he finds it at: ".\SAMPLE_v8\CONTENT_EXAMPLES\GameSDK\assets\levels\contentExample\PIT_BLANK\PIT_BLANK.cry", but then doesn't know what to do with it. So he can't process to follow the video and gives up.

The content example setup is explained in the getting started section of our video tutorials:
https://www.cryengine.com/tutorials/get ... ng-project

HDN wrote:@This topic
Instead of giving one big package for all the tutorials, make small projects for each tutorial/tutorial series. What's the newbie want is "one-click-setup". There are a few disadvantages of one big package for all tutorials that I guess you already know:
1. User take long download time.
2. Confuse user.
3. hard to setup.
4. Require user download the whole package when there is an update for 1 outdated asset (If there's an update for asset)
If you don't have time to break the big package now, at least give description (what is this, how to set up) for the content in the big package, but I still prefer small projects for each tutorial series.

It is a fair point that the asset download is rather large and some things are not obvious, a single drag and drop into the GameSDK folder is the way to go right now which includes all the content examples.
As for the rest we will forward it to the relevant departments.

Thank you for your feedback

Cry-Chris wrote:The content example setup is explained in the getting started section of our video tutorials:
https://www.cryengine.com/tutorials/get ... ng-project

Thanks, Jack should have seen this video before he gives up
But I think most lazy people (like myself and Jack) work like this:
Step 1. Download the CryEngine.
Step 2. Start exploring CryEngine on his own (browse the CryEngine UI and start clicking and seeing)
Step 3. Check the tutorial videos for interesting features.
So when Jack sees the Getting Started videos, he tends to skip these videos, he likes: "Nah, I've already known how to do this in step 2! So skippy skip!".
Therefore I think CryTek needs to design a small game for beginner tutorial like Survival Shooter, through this tutorial, you can teach the Getting Started tutorial, I hope you soon have information for the tutorial like this.