This seems to be because of recent changes made for [Link Removed]. Now that UNetDriver::bInTick is being properly tracked for derived classes, AOnlineBeacon::CleanupNetDriver is now deferring destruction of the NetDriver rather than immediately calling DestroyNamedNetDriver. When AOnlineBeaconClient::DestroyNetworkActorHandled is then called when attempting to destroy the beacon, the connection is still considered open, and so destruction of the connection/beacon is also deferred by setting bPendingDestroy on the BeaconConnection. However, the BeaconConnection isn't destroyed, since the NetDriver is shutdown at the end of the tick without ticking the connection again.
While destroying a NetDriver from a RPC is not considered a supported operation, this did work previously for beacons. If this is something that shouldn't be supported, it should likely be made more clear what is going wrong, such as with log errors or warnings.
Within a client beacon's RPC, call DestroyBeacon. Previously, this would result in the beacon being destroyed as expected. As of 5.2, the beacon will no longer be destroyed.
i have this problem UE4CC-Windows-58DC12AF4B97F057BD108FBFF569B2E9_0000
I am not able to find world outliner how to enable it?
Delay nodes occasionally don't fire the "Completed" output in a nativized build
How can i modify the param name in EQS node
Undefined sysmbol: typeinfo for AActor when cross-compile linux dedicated server on windows
How to achieve HLSL Multiple Render Target in Material blueprints?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-186023 in the post.
0 |
Component | UE - Networking |
---|---|
Affects Versions | 5.2 |
Target Fix | 5.4 |
Fix Commit | 30355891 |
---|---|
Main Commit | 30355970 |
Created | May 16, 2023 |
---|---|
Resolved | Dec 18, 2023 |
Updated | May 1, 2024 |