Description

Currently, properties marked DuplicateTransient will be reset to default when their actor is moved to a different level. This happens because we use the clipboard to virtually cut the actor out of one level and paste it into another, so it's still a duplication under the hood. However, it's more intuitive to think a "move" transaction would relocate the existing instance and not duplicate it and delete the original. Therefore, we'd expect the DuplicateTransient property to still be set after a move.

Steps to Reproduce
  1. Create an actor with a property marked DuplicateTransient
  2. Add your actor to the level and set your property
  3. Copy and paste it. See that the new actor's property resets to default (expected)
  4. Select a different sublevel in the levels window and move your actor to that level
  5. Property will reset to 0, despite you "moving" the actor and not duplicating it

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-52678 in the post.

0
Login to Vote

Won't Fix
ComponentTools
Affects Versions4.19
CreatedNov 22, 2017
ResolvedAug 18, 2021
UpdatedAug 18, 2021
View Jira Issue