CollisionProfileName property type not supporting multi-edit

Development Programming & Scripting
, ,
1

When making Variables of the CollisionProfileName type, they do not properly handle multi-selection, which can lead to data loss.

2

Steps to Reproduce

  • Make a new Actor Blueprint
  • Add a new CollisionProfileName variable
  • Compile and save the blueprint
  • Add two instances of the blueprint to a level
  • Change their CollisionProfileName properties to have different values
  • Select both Actors at once
  • Notice that the property does not properly handle the multi-selection
  • Select each actor individually and notice how one of their CollisionProfileName property got set to the value of the other
3

Looks like this is caused by FCollisionProfileNameCustomization not correctly handling actor multiselection. FCollisionProfileNameCustomization::SetPropertyWithName will reset all values to “None” when multiple actors are selected, dirtying the actor packages in the process.

4

Hi hsq_bhuguenin,

Thank you for reporting this issue. This is actually a known bug, you can find it on the following bug tracker links: UE-46242, UE-193151.

Unfortunately, from the “won’t fix” and “backlogged” statuses, it seems that this is considered low priority at the moment, and we cannot give estimates on when it might be addressed. If the fix is important for your team, please vote on the “backlogged” issue on the tickets above.

Let me know if there is anything else I can do to assist you.

Best regards,

Vitor