fix(1.0.0-pre.3): Photon Transport connect event id assignment #118
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Connect event ids on the client now contain the hosts peer id instead of the clients own id.
LukeStampfli
force-pushed
the
fix/photon-clientidassigment
branch
from
8cafd3f to
19a3b91
Compare
andrews-unity
approved these changes
Nov 2, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Connect event ids on the client now contain the hosts peer id instead of the clients own id. This results in the Photon Realtime transport behaving similar to the UNet and UnityTransport and allows it to work with #1368
Tested on Boss Room
fix/ngo-pre.3branch (#483194dd749e062fcedd58d3fac43caeb0d7587b) with 1 host + 2 clients on same machine able to connect to the lobby select a character and walk around in the game using Photon Realtime Transport