Reporting Issues for Documentation

AlwysAnrchy · September 29, 2015, 6:54pm

Howdy master_rigel,

I have just checked this option in 4.9.1 and in the latest main branch. Both versions have this feature listed as ‘Placement’.

This fix has been made and will show live after the next publishing.

master_rigel;388765:

Perhaps move “Blueprints Visual Scripting” above “Engine Features”

I am placing this feedback inside the issues topic because it is a serious issue for me. It is slowing down my learning of UE4 substantially.

I understand this change could be a bit drastic, but Blueprint is so pervasive across the engine (in materials, in umg, in “Gamplay Guide”, and almost all other scripting), that perhaps it should be introduced much earlier than it is presently. At the very least consider it an “engine feature”, and move to the top of that section because it has so many hooks into the way the engine works. Without it, someone who does not know C++ practically has their hands tied.

A) Following the documentation in linear form and cross-referencing the blueprints docs as I go, I am having to learn much by trial and error that is spelt out plain and simple in the blueprint docs.
B) It appears as though I can follow the blueprint docs relatively easily without having to reference other engine features so long as I’ve finished “Get Started with UE4” and “Unreal Editor ManuaL”

Regards,

I will bring up this topic during our next meeting and see what everyone’s response for this change is.

Thanks again!

Howdy ,

Thank you for your feedback. I have fixed the Documentation to include Interface in the Table. I have also entered UEDOC-2497 into our Database so that we can address the issue.

Howdy Drout,

I have just entered ticket UEDOC-2500 into our database so that this page can be fixed. I am unsure as to when this will be fixed but I will be sure to keep you posted when I see an activity on this ticket.

Thanks!