BP Doc review
jetXS opened this issue · 5 comments
The only thing I can recommend for this is to add the new "Send Mode" feature under the Cook Mode paragraph - there are 2 send modes, Every Frame and On Access.
Every Frame sets and gets outputs every frame, while on access only sends them when the variable types are accessed via the blueprint nodes
(If you have a better idea for the name other than "Send Mode" that would be appreciated)
Did you look at that long doc with all the examples detailed @ddthejj ?
I need to update the blueprint bits I think, as they were updated considerably in the last couple weeks with the changes on CHOPs and DATs.. etc.
I'd need however to make sure I'm not too off with the "Unreal slang" but also not missing important steps in the way you built BPs and data + events flow.
It looks like the blueprint CHOP stuff in the screenshots is already up to date (specifically looking at example 06, which has CHOP values)
The DAT stuff is only used in example 10 at the moment, and does need to be updated.
The "Unreal slang" is pretty on point, though there's not anything specific that isn't apparent when doing something like hovering over an object to see what it's called in unreal.
One thing that I think could be added to help with the workflow is that to add the events you see in the blueprints (example below) you need to click on the TE component, scroll to the bottom of the details panel, and click on the event.
@ddthejj Can you please give your input and update line 107 A word about texture type, depth and limitations - thanks!
One thing that I think could be added to help with the workflow is that to add the events you see in the blueprints (example below) you need to click on the TE component, scroll to the bottom of the details panel, and click on the event.
Added to Plugin readme doc