[BUG] 4.12.5 Convert Actor moves Actor to selected Level

When I have multiple levels in my world and convert an Actor to a different type using the “Convert Actor” functionality, the following seems to happen (I reproduced it several times):

  1. The Actor is deleted.
  2. A new Actor of the desired type is spawned in my currently selected Level which might not be the one where the original Actor was!

Update: Also happened in 4.14.1

Hi GigaGrunch,

When you are choosing Conver Actor, what option are you picking? InteractiveFoliage or have you added an additional subclass?

I was converting a bunch of BlockingVolumes to NavModifierVolumes, nothing custom. Also, I just reproduced it in 4.14 – I selected one NavModifierVolume in a streaming level while having the Persistent Level active and converted it back to a BlockingVolume. It ended up in the Persistent Level.

Hmm, I just attempted to reproduce this but the converted actor still stays in the correct level for me. Could you provide repro steps from a new Blank project?

We haven’t heard back from you in a few days, so we are marking this post as resolved for tracking purposes. If you’re still experiencing this issue, please feel free to post back here with additional information to reopen the post.

Cheers,

TJ

Finally I came back to reproduce this and found it very easy – now with the current version 4.14.2 from the launcher.

  • I created a blank C++ project without anything
  • added one more level to the World
  • added a BlockingVolume to the new level “Level2”
  • switched to the PersistentLevel (via double click)
  • converted the BlockingVolume to a NavModifierVolume
  • it ended up in the PersistentLevel (easy to spot, because the label telling me the level of the Volume is directly above the ConvertActor button)
  • switched back to “Level2”
  • converted the NavModifierVolume back to a BlockingVolume
  • it was in “Level2” again

I don’t know if this happens for all types of Actors, but with my example, I have a 100 % reproduction rate.

Thanks for sticking with this and getting a repro to us. I was able to reproduce this using the steps you provided. I’ve logged it as JIRA UE-40360 and our developers will be investigating further. Use that link to monitor the bugs status and vote on it’s priority.

Thanks again,

TJ