izzy/UnrealEngineUWP
0
0
Fork 0
mirror of https://github.com/izzy2lost/UnrealEngineUWP.git synced 2026-03-26 18:15:20 -07:00
Code Issues Packages Projects Releases Wiki Activity
Files
c245cdc36281eb0cd31c8265a263aaaed00a4580
UnrealEngineUWP/Engine/Plugins/Experimental/DataInterfaceGraph/DataInterfaceGraph.uplugin

46 lines
918 B
Plaintext
Raw Normal View History

Initial prototype of data interfaces and data interface graphs Data interfaces are designed to be the basis for a functional, compositional framework, allowing loose bindings (a typed return value) between functional units (data interfaces). They incorporate the following main features: - Simple call to 'get a value' from a data interface. - Most communication is done via the UE::DataInterface::FContext, which handles data management. - Type-erased values (UE::DataInterface::FParam) for results, parameters and state. These can be promoted to typed values (UE::DataInterface::TParam<T>) with runtime validation. - 'Hidden state', allocated on-demand via a context, to support functional units that require statefulness. State is allocated according to the calling context, currently a hash of the 'callstack' and call site, so subsequent calls to the same data interface can reuse state. - Batch processing of multiple state representations at once (e.g. processing multiple characters at one), via a chunked allocation strategy. Also includes data interface graphs - a proof-of-concept implementation using RigVM to construct scripted data interface logic. This is still very early! Still lots to do: - Removal of typed interfaces (e.g. IDataInterface_Float) - Validation of hidden state approach on a wider scale - Validation of kernel processing approach - Chunked branching (probably via a masking strategy) so branches can be handled within chunks - Reworked type system incorporating type promotion/conversion - UI work to allow for mixing instanced sub-objects and asset references with using TScriptInterface<IDataInterface> - Expansion or RigVM usage and a ton of UI/UX work to get graph editing up to scratch - Many many more things #preflight 625e86873e0f6f80ada98290 [CL 19806109 by Thomas Sarkanen in ue5-main branch]
2022-04-19 06:28:48 -04:00
{
"FileVersion" : 3,
"Version" : 1,
"VersionName" : "0.1",
"FriendlyName" : "Data Interface Graph",
"Description" : "Framework for defining functional data flow for animation systems",
"Category" : "Animation",
"CreatedBy" : "Epic Games, Inc.",
Update vendor links for built-in plugins to use secure protocol. #jira UE-166823 #rb lauren.barnes #preflight 6352b20b7261e565c476ec3b [CL 22690089 by Robb Surridge in ue5-main branch]
2022-10-21 11:04:07 -04:00
"CreatedByURL" : "https://epicgames.com",
Initial prototype of data interfaces and data interface graphs Data interfaces are designed to be the basis for a functional, compositional framework, allowing loose bindings (a typed return value) between functional units (data interfaces). They incorporate the following main features: - Simple call to 'get a value' from a data interface. - Most communication is done via the UE::DataInterface::FContext, which handles data management. - Type-erased values (UE::DataInterface::FParam) for results, parameters and state. These can be promoted to typed values (UE::DataInterface::TParam<T>) with runtime validation. - 'Hidden state', allocated on-demand via a context, to support functional units that require statefulness. State is allocated according to the calling context, currently a hash of the 'callstack' and call site, so subsequent calls to the same data interface can reuse state. - Batch processing of multiple state representations at once (e.g. processing multiple characters at one), via a chunked allocation strategy. Also includes data interface graphs - a proof-of-concept implementation using RigVM to construct scripted data interface logic. This is still very early! Still lots to do: - Removal of typed interfaces (e.g. IDataInterface_Float) - Validation of hidden state approach on a wider scale - Validation of kernel processing approach - Chunked branching (probably via a masking strategy) so branches can be handled within chunks - Reworked type system incorporating type promotion/conversion - UI work to allow for mixing instanced sub-objects and asset references with using TScriptInterface<IDataInterface> - Expansion or RigVM usage and a ton of UI/UX work to get graph editing up to scratch - Many many more things #preflight 625e86873e0f6f80ada98290 [CL 19806109 by Thomas Sarkanen in ue5-main branch]
2022-04-19 06:28:48 -04:00
"DocsURL" : "",
"MarketplaceURL" : "",
"SupportURL" : "",
"EnabledByDefault" : false,
"CanContainContent" : false,
"IsBetaVersion" : true,
"Installed" : false,
"Plugins": [
{
"Name": "DataInterface",
"Enabled": true
},
{
"Name": "ControlRig",
"Enabled": true
}
],
"Modules" :
[
{
"Name" : "DataInterfaceGraph",
"Type" : "Runtime",
"LoadingPhase" : "Default"
},
{
"Name" : "DataInterfaceGraphEditor",
"Type" : "Editor",
"LoadingPhase" : "Default"
},
{
"Name" : "DataInterfaceGraphUncookedOnly",
"Type" : "UncookedOnly",
"LoadingPhase" : "Default"
}
]
}
Reference in New Issue Copy Permalink