Search Issue Tracker
Fixed in 5.4.3
Votes
9
Found in
5.5.0b2
Issue ID
827884
Regression
Yes
When close Client in Standalone - Host still has client's player and disconnect error appears
Regression: this started to happen since 5.5.0a3 (not happening in 5.5.0p4 and 5.5.0a2)
- please see attached video
How we can reproduce it using the example you attached
1 Open attached project
2 Build Standalone
3 Run Host in Editor and Client in Standalone
4 When Client will be connected - just close Standalone window
Actual results: after Standalone has been closed - it's player is still shown on the Host and errors appears about Disconnect error 6 appers (errors probably correct !!!)
Expected results: When there is only Host left - only one player should be present on the scene
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment