[Bug] Reparenting != New Blueprint

Development Programming & Scripting Blueprint
, , , ,
1

If you re-parent a blueprint from Object to BlueprintActorBase, the result is not the same as having selected BlueprintActorBase as the parent when you created the blueprint.

Build info
Version: 1578757
Install Path: C:/Program Files/Rocket

Specs
OS: Windows 8
RAM: 8 GB
Graphics Card: GT 540M w/ 2 GB
Driver: 310.70
UAC: Off

Repro Steps

  1. Create a new blueprint
  2. Select Object as the parent
  3. Note: Objects can’t have components.
  4. Reparent blueprint to BlueprintActorBase
  5. Note: Still can’t have components.
  6. Close and reopen the blueprint, still no component capability.
  7. Create a new blueprint.
  8. Select BlueprintActorBase
  9. Note: You can now set components.

Expected
I expected after re-parenting any blueprint from one parent to another that I would have the same capability as if I had selected that new parent to begin with.

2

I had one of our programmers re-look this over and step 5 is actually a bug. This is a known issue which most likely will be fixed in a later iteration.

3

This is expected. When changing the parent the blueprints options will be based on that new parent.