com.unity.services.samples.game-lobby

文件历史

nathaniel.buck@unity3d.com 3045dabc Modifying UpdateSlow to accommodate differing periods, including acting as a regular Update for subscribers that aren't necessarily MonoBehaviours. I'm also stripping the staggering behavior, since it was unclear and not particularly necessary.		3 年前
..
RelayAPIInterface.cs	Adding comments and doing minor renames for clarity.	3 年前
RelayAPIInterface.cs.meta	Latest Dev and Readme without Vivox	3 年前
RelayUtpClient.cs	Modifying UpdateSlow to accommodate differing periods, including acting as a regular Update for subscribers that aren't necessarily MonoBehaviours. I'm also stripping the staggering behavior, since it was unclear and not particularly necessary.	3 年前
RelayUtpClient.cs.meta	Still partial progress. I have a little handoff going where the client identifies itself to the server and the server responds with an ID to use in further communication. However, I don't think that will actually work since all clients would also need those IDs? I can just send the user ID, which takes up more bandwidth but not dramatically so. Also, this pinpoints the heartbeat for keeping the Relay allocation up. I'm trying to pull out all the job system things, since that both seems like an extra layer of complexity that devs would have to learn and it also isn't, like, actually used correctly in the sample?	3 年前
RelayUtpHost.cs	Adding comments and doing minor renames for clarity.	3 年前
RelayUtpHost.cs.meta	Still partial progress. I have a little handoff going where the client identifies itself to the server and the server responds with an ID to use in further communication. However, I don't think that will actually work since all clients would also need those IDs? I can just send the user ID, which takes up more bandwidth but not dramatically so. Also, this pinpoints the heartbeat for keeping the Relay allocation up. I'm trying to pull out all the job system things, since that both seems like an extra layer of complexity that devs would have to learn and it also isn't, like, actually used correctly in the sample?	3 年前
RelayUtpSetup.cs	Looks like the "A Native Collection hasn't been disposed" error at this point is only present due to use not disposing of the NetworkDriver when we're done with Relay.	3 年前
RelayUtpSetup.cs.meta	Partial progress: Following a trio of Relay+UTP samples, I seem to have something that will bind a transport to Relay and keep the connection open (as evident from the fact that a client can join after what would be the 10s timeout on Relay and successfully get the JoinAllocation, when they wouldn't without keeping the connection open even when binding was correct). However, this current code is very slapdash and sloppy; I'm just committing now as a very rough draft.	3 年前