Purpose of this PR

If, upon starting a host or server using the default client synchronization mode of LoadSceneMode.Single, a new scene is loaded additively, preserving the original scene already loaded, and then sets the newly loaded scene as the active scene, any client attempting to connect will get a soft synchronization error due to the serialization order of the scenes.

Jira ticket

MTT-15431

Changelog

• Fixed: Issue where the active scene was not being serialized as the 1st scene which could result in various errors including a soft synchronization error if, on the client-side, other synchronized scenes had already been loaded prior to the active scene, which is always loaded as LoadSceneMode.SingleMode when client synchronization is set to LoadSceneMode.SingleMode, resulting in the previously loaded scene(s) to be unloaded.

Documentation

• No documentation changes or additions were necessary.

Testing & QA (How your changes can be verified during release Playtest)

Functional Testing

Manual testing :

• Manual testing done
  • The jira ticket contains a link to the project used to replicate and validate this issue.

Automated tests:

• Covered by existing automated tests
• Not covered by new or existing automated tests
  • This requires clients to be able to load scenes in LoadSceneMode.Single which cannot be done when running integration tests and sharing the same scene hierarchy (thus the manual test).

Does the change require QA team to:

• Review automated tests?
• Execute manual tests?
• Provide feedback about the PR?

If any boxes above are checked the QA team will be automatically added as a PR reviewer.

Backports

No back port is required.