Closed GrimLothar closed 3 weeks ago
com.unity.transport version 2.3.0 has released today that I think should have a fix for this issue. A new release for the 1.x line of com.unity.transport should be out soon as well, I'll post again when that is out in case you can't or don't want to update to 2.3.0.
Can you retest and confirm for us?
@ShadauxCat @michalChrobot thank you for your replies.
It looks like com.unity.transport
on my project is only being used by Netcode for GameObjects 1.8.1 (this repo). But I don't see any updates there since February.
So is it safe for this package to update transport?
I can see that Netcode for GameObjects uses a com.unity.transport@1.4.0
dependency. I would upgrade it then to 1.5.0 and this shouldn't break the project in any way (since there is no major package version change)
Let me know if it worked
Alright, I changed it to 1.5.0.
Any idea when netcode for gameobjects will be updated to use the 2.x.x branch of transport? Would be nice to be on the latest
Regarding my issue itself, I have no way or replicating the error, since I got it from a user in production... so not sure if you want to just close this and I'll create a new one if I get a new error after I push this build out?
Hmm, I'm not sure which editor version are you using but the correct way would be to consider switching to Unity 6. I can see that the newest version of com.unity.netcode.gameobjects
(2.X) is available from this editor version and it references the newest Transport package (2.X). (all netcode for gameobject, packages of version 1.X are referencing Transport package of version 1.X)
Of course it depends on your project size/current situation etc. but you could see if that would be an option for you or not really.
Regarding this Github issue I would close it in maybe a week, and then if you would encounter the same issue again I believe you will be able to reopen it
Got an error that just said to open a bug report here and paste this info