Backcompat: ConstructObjectFromClass node no longer accepts "Outer" input types that are not also derived from self

The ConstructObjectFromClass node no longer allows connections to the "Outer" input pin that are not of a type that's derived from the current Blueprint class (self).

Previously, users could connect any UObject type to the "Outer" pin.

1. Create a new Actor-based Blueprint class asset (NewBlueprint).
2. Create a new variable of type "Object Reference."
3. Drag the variable into the Event Graph and create a "Get" node.
4. Right-click in the Event Graph, then choose "ConstructObjectFromClass"
5. Attempt to drag the "Get" node's output to the "Outer" input pin. Note that it's not allowed because the pin type is not compatible.
6. Create a new variable of type "NewBlueprint."
7. Drag the variable into the Event Graph and create another "Get" node.
8. Attempt to drag the "Get" node's output to the "Outer" input pin. Note that now it is allowed.
   Expected result: Both types should be allowed to be connected to the "Outer" input pin, as this is how it was working previously.

N/A

Request a info about UE-127172 bug tracker

How does TextureRenderTarget2D get TArray<uint8> type data?

Why does the REMOVE method of map container remove elements have memory leaks?

How do I set a material as a post-processing material?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

How to delete some elements correctly when deleting an array loop?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

UMG RichText not appear image when packaged

What is the difference between Camera and CineCamera?