As described in the linked UDN, non-replicated components aren't being hooked up properly after an actor goes out & back into relevancy. The proposed fix sounds correct, calling MoveMapedObjectToUnmapped for the actor's non-replicated components as well.
This would be a great candidate for a regression test in EngineTest.
TBD, we could create a case in EngineTest to test this.
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-76357 in the post.
| 0 |
| Component | UE - Networking |
|---|---|
| Affects Versions | 4.20 |
| Created | Jun 17, 2019 |
|---|---|
| Resolved | Aug 27, 2021 |
| Updated | Aug 27, 2021 |