When nativizing blueprints the packaged build of the project runs slower than a non-nativized version of the packaged project. Found in 4.22 CL#7053642 Reproduced in 4.21 CL#4753647, 4.24Main CL#7 ...
UObjectBaseUtility::GetInterfaceAddress() fails due to an incorrect serialized value of the 'bImplementedByK2' property within the non-nativized class's Interfaces array on save. See support thread ...
Since we implicitly create new function graphs for non-event functions when an interface is implemented, that code path marks the function as callable by default. In other words it's not required to ...
This occurs because the MakeStruct node will create a literal term for each input if nothing is connected. However, there is no explicit handling of some native 'noexport' struct types (e.g. FVector ...
This is a regression that was introduced by the fix for [Link Removed]. The fix makes an invalid assumption that instances of components whose archetypes are inherited by a non-nativized child Blue ...
When Blueprint Nativization Method is set to Exclusive, packaging will fail if a data only blueprint's child blueprint is set to to Nativize in class settings. Workaround:Adding a node to Parent so ...
Packaging with nativization enabled will fail when a struct and interface reference each other. Error Message: LogCompile:Error: Circular dependency detected for filename C:\Users\Sean's\Downloads ...
Implemented interfaces are not added to the list of assets to nativize when the blueprint class that implements them is flagged for nativization, saved, and compiled. This results in a package failu ...
Crash occurs when removing the native root component from code and then attempting to reopen a Blueprint Class asset that was based on the native parent class. Seems like maybe the 'AttachParent' f ...
The incorrect use of NewObject() to instance nested class-owned subobjects will force StaticAllocateObject() to reconstruct the instance that was already constructed by the outer class ctor in nativ ...