Unity Transport Update Blocking Thread

[aondw]

Description

Hi, I was looking through the profiler and noticed UnityTransport always showing up with like 0.3ms.
In the code I saw that in UnityTransport.Update() the m_Driver.ScheduleUpdate() is immediately completed, blocking the main thread.

Because don't know about all the timing implications and reasons behind it, I wanted to ask here: can we e.g. move the .Complete() to LateUpdate or use Jobs (but that's probably a bit more involved).

Unity 2022.3.51, Netcode 1.14.0

[EmandM]

Thanks for reporting this issue! This is actually an area that has had a number of improvements in the latest versions of Netcode for GameObjects and Unity Transport that are available in Unity 6. We highly recommend upgrading to these versions if that is possible for your project.

[aondw]

thanks for the response!
do you have a commit I could look at for those changes? The UnityTransport on the develop 2.0 branch seems to have the same logic, but maybe I'm looking in the wrong place.

[EmandM]

Is there any chance you can link to the specific code you're looking at?

The UnityTransport code we have in this code base relies upon the underlying UnityTransport package. That code does not live in this codebase and has had improvements in Unity 6.

[aondw]

I'm looking here: 2.x, 1.14

edit: also which UnityTransport version is Unity 6 exclusive? the highest I can see on the package site is 2.5.3, which is 2022.3+. https://docs.unity3d.com/Packages/com.unity.transport@2.5/changelog/CHANGELOG.html
or does it handle things different in unity6?