You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On State Entry/Exit/Transitions bindings could be done in c++ using corresponding AddNativeXBinding() and avoid going through the BP VM.
Would a PR moving thoses function to C++ be accepted?
Lot of nodes or transition result could also be done in the AnimInstanceProxy to avoid blueprint usage.
I'm pretty sure the entire Layering Anim Graph Layer could be done inside a c++ node in a proxy and avoid much BP overhead.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello!
Since the project is aiming for performance:
On State Entry/Exit/Transitions bindings could be done in c++ using corresponding AddNativeXBinding() and avoid going through the BP VM.
Would a PR moving thoses function to C++ be accepted?
Lot of nodes or transition result could also be done in the AnimInstanceProxy to avoid blueprint usage.
I'm pretty sure the entire Layering Anim Graph Layer could be done inside a c++ node in a proxy and avoid much BP overhead.
Is it not used for AnimGraph Readability purpose?
Beta Was this translation helpful? Give feedback.
All reactions