Unreal Engine Issues

FSubobjectData::SetupAttachment() receives SocketName as a parameter but ignores it.

When using the Subobject Data Subsystem in C++, method FSubobjectData::SetupAttachment() can be used to help attaching a component to a parent at a given socket. This function receives SocketName as ...

WindDirectionalSourceComponent.h has a meta edit condition that, by referencing an undefined property (bSimulatePhysics), throws an error

WindDirectionalSourceComponent.h has a meta edit condition that, by referencing an undefined class property (bSimulatePhysics), throws an error in the logs: LogEditCondition: Error: EditCondition pa ...

Investigate PythonScriptPlugin module load order for preload module

Bug when loading an external project that also exists in the uprojectdirs

When launching the editor for the "external\foreign" project, the code in GetEngineAndProjectAbsoluteDirsFromExecutable ends up superseding the path returned from {{FPlatformMisc::ProjectDir() }} wi ...

Niagara - "Make Static" nodes do not seem to be working correctly.

When a "Make Static" node is used in a Niagara Function Script or Niagara Module Script to supply the input value for a Static Switch Selector or, a Function Parameter, or a Function Parameter Defau ...

On the Details Panel of Niagara Function Inputs, the Type selector does not show "Static" types.

Consider a Niagara Function or Module Script containing a Static Switch node. If the "Expose as Pin" option is enabled for its selector variable, an input pin with type "static bool" appears. In one ...

Niagara - When a Static Switch is used inside a Niagara Function Script with "expose as pin" disabled, its Selector variable is exposed as an input on function call nodes. However, this input incorrectly loses its "static" type.

Consider a Niagara Function Script containing a Static Switch node with the "Expose as Pin" option disabled for its selector variable. When the function is called by another Niagara Function or Niag ...

Niagara - When editing a Niagara Function or Module Script, the "Apply" button on the toolbar never gets disabled if "expose as pin" is checked on any static switch node.

Consider a Niagara Function or Module Script containing a Static Switch node. If the "Expose as Pin" option is enabled for its selector variable, the "Apply" button on the graph editor's toolbar wil ...

Niagara - The "Apply" button on the toolbar does not get enabled when changing the checked state of an entry in "Propagated Static Switch Values" for a function call node.

Consider a Niagara Function Script containing a Static Switch node with the "Expose as Pin" option disabled for its selector variable. Now consider another Niagara Function Script or Module Script ...

Blueprint asset tabs move around weirdly when you navigate between them with too many open

The "parent class type" text changing size causes the tabs to shift around a lot when you have a lot of them. We need to figure out a better place for this text to avoid the issue ...