Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client not properly changing scenes/spawning objects in Unity Editor #235

Closed
uweeby opened this issue Jun 28, 2020 · 4 comments · Fixed by #339
Closed

Client not properly changing scenes/spawning objects in Unity Editor #235

uweeby opened this issue Jun 28, 2020 · 4 comments · Fixed by #339
Labels

Comments

@uweeby
Copy link
Member

uweeby commented Jun 28, 2020

Client not properly changing scenes/spawning objects in Unity Editor

Repro project and To Reproduce

  1. Open the ChangeScenes Example.
  2. Add the 3 scenes in the example to a build.
  3. Run that build as a Server or Host.
  4. Run the Editor as a Client and connect.
  5. use the buttons on the SERVER SIDE to change the scene.

Expected behavior
The client should load a new player object and the scene object from the scene. Instead more than 50% of the time it gives a spawning error and the client disconnects itself.

If you run the Client in the standalone build and the Server in the editor it works fine. If you run both in standalone it works fine. If you use breakpoints on the Client while in editor it works fine.

Desktop:

  • OS: Windows
  • Build target: Standalone
  • Unity version: 2019.3.10
  • Mirror branch: Master
@uweeby
Copy link
Member Author

uweeby commented Jul 4, 2020

image

@uweeby
Copy link
Member Author

uweeby commented Jul 17, 2020

Breaks here:
image

@uweeby
Copy link
Member Author

uweeby commented Jul 17, 2020

When replicating the steps there are 2 possible outcomes. The errors above and this one:
image

Breakpoint stepping order:
OnObjectSpawnStarted
PrepareToSpawnSceneObjects
ConsiderForSpawning x2
OnObjectSpawnFinished
Cleanup
DestroyAllClientObjects

@github-actions
Copy link
Contributor

🎉 This issue has been resolved in version 43.4.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant