This isn’t the right topic for it,
But generally speaking…
Keep your sentences short.
The shorter the better.
Less chance for confusion.
You can also include a version in your original language.
Re: getting help, which is also NOT the point of the topic.
If a request is a rambling of 20 run on sentences that can be barely read, and most definitely not understood - no one will touch it.
The subjects are often very technical and complex.
Writing topics like “x doesn’t work” means you’ll probably get a response of “wtf are you talking about”? Or “sure it does”.
If instead you include details about what doesn’t work and how to replicate it, when people read it, they would actually be more inclined to help, as they would have at least some information to make assumptions with.
RE: the rest.
If your “feedback” to epic is that you can’t find answers when you ask something.
Sure. No one can. That’s the point.
Ask @BrUnO_XaVIeR for instance.
Did anyone tell you why the community ocean project water needed transparency sort priority per pixel to avoid artifacts?
The more specific a problem is, the less of a chance you’ll get an answer without actually going around trying to find an answer yourself…
IF we had a community wiki instead, huge important things like that, or like the character movement component, or think even new nuisances like Tessellation alternatives, best/good practices?
maybe you would be able to just find answers without having to really search…
BUT NO… epic took our wiki away instead.