5 次代码提交 (123815cb-d8a9-4988-990c-6dec6827032e)

作者 SHA1 备注 提交日期
nathaniel.buck@unity3d.com 123815cb Minor logging change, and upgrade package. I've tested in 2021.2.0b11 that this works with DTLS active, although it might need a little more rigor since I had intermittent issues with one editor (but not so much the other?) failing to fully connect to Relay for some reason (i.e. getting stuck in the "Connecting..." state). 3 年前
nathaniel.buck@unity3d.com 8344a95b Changing the Relay message parsing to allow for validation of the message length, which was interfering with diagnosing the issue with DTLS. (Turns out it's on their end, and there's a fix coming today. But, this is still an improvement.) 3 年前
nathaniel.buck@unity3d.com a204c67d Oops, missed a UI change in clients that I added for hosts. 3 年前
nathaniel.buck@unity3d.com 20496d52 Adding in a test for DTLS and cleaning up a couple minor points with the DTLS changes. These do not currently work on 2020.3 (since DTLS support has not been ported back yet but will be) but I've tested them on 2021.2.0b11; the test executes just fine, but for some reason in practice there's an issue where we no longer know the correct packet length when reading Relay data. I'm told there should not be any change to this needed on the developer's end when DTLS is active, but investigation is ongoing. 3 年前
nathaniel.buck@unity3d.com a0ba1fdd DTLS integration, probably? It's not in this Editor version, but this should work in 2021. Added a test to say "hey, this is the wrong version" and everything still works the same as before adding DTLS. 3 年前