More effective documentation feedback

[KristofMorva]

Just for reference, here is project.gheist's pull request aiming to solve this problem: https://github.com/EpicGames/UnrealEngine/pull/5248

[KristofMorva]

In some part it's probably true, I guess there are some features which are not finished in time, re-prioritized, etc, so it's very likely they don't have...

[KristofMorva]

There are many things you can set, if all of them would be on the Timeline node itself, it'd be 10km long (and it's already too big), I guess that's why...

[KristofMorva]

Actually that sounds interesting, it would be great to know how internal Epic teams handle some projects, what guidelines do they stick to, what rules...

[KristofMorva]

I see, there isn't much more you can do in that case than the automatic crash reports, although you should check first if the crash is caused by any C++...

[KristofMorva]

There is the Crash Submission screen that opens automatically on an editor crash, where you can also explain the reproduction steps.
And what are...

[KristofMorva]

Generally I agree, sometimes it's really a pain to explain them what is wrong exactly (besides submitting steps, example project and everything), but...

[KristofMorva]

When I go through a page of the documentation, I usually find one or two typos, however, it'd be quite cumbersome to come to the forums each time, and...

[KristofMorva]

Well, I guess time will tell how it will turn out. It can happen that they privately instruct companies, especially if they plan to switch to Unreal and...

[KristofMorva]

It's great if they could publish materials, but it sounds unrealistic that Epic will start regular classroom courses around the world either by traveling...