5.2 Actor Tag Bug?

Anyone having any issues with Actor Tags and the 5.2 Update? The update broke one of my systems that was working really well because it deleted half of my actor tags.

I replaced all tags and my system was back working as usual. I thought okay, minimal damage, let’s move on… Well, after opening the project again those previously deleted actor tags are gone once again. The difference this time, is that it still shows the actor tags in the details panel, where when I first converted the project it did not. I have tested this several times and the actor tags are consistently being deleted after closing program. This seems like a major bug. It looks like I might just code around this with a different identifier because 5.2 seems more stable all around… geez…

Hey there @FrankMink! This definitely seems like a bug, possibly one that is caused from the migration. Could you try to set some tags in a fresh project on a fresh BP? I couldn’t replicate the tags disappearing on my side.

Hey, thanks for responding. Yeah, I will do that tomorrow and get back to you. Thank you.

Fresh project, with fresh Blueprint actor and 3 tags. Exited project, reopened project and all tags are there, so this seems to be okay.

I’m going to create a test project in 5.1 with same actor tags and migrate it and see if they get deleted or cause any issues.

I did the same test migrating the 5.1 project to 5.2. I used 1 actor and 3 tags. I did not experience any issues as the tags were not deleted.

The only difference with my initial problem was that after migration it only deleted some of the actors tags. So I guess the next test is to migrate a project using multiple actors with tags. I’ll try that next.

Migrated 5.1 to 5.2 with multiple actors and multiple tags. No problems. On the project I am having issues with the tags in question are connected to child classes. This might be the only other area where the problem could be.

Excellent work narrowing it down! Are the child classes tags saving on maps that aren’t part of the default set? This is an odd one! I can’t even replicate child classes tags disappearing.

I haven’t been able to check them on other maps yet, but it seems that the migration striped the Child Actor Template section out of the child class components and with them went the connection to the Actor Tags.

All the child actors that had the missing actor tags all had a missing Child Actor Template Section from the Details Panel.

Clearing the Blueprint class from the Child Actor Component Details Panel and selecting it again brings back the Child Actor Template Section and proper function of the actor tags, but on exit and reopen of the project the Child Actor Template Section is stripped again.

The Solution to this was to just create new Child Actor Components and reconnect everything. These fresh Child Actors did not have any issues upon closing and reopening the project. Minimal damage… Other than this and some water issues 5.2 seems to being running pretty good!

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.