Transport 1.2.0 Incompatible with collections 2.x

When updating to the new Entities release (1.0.exp12), you get compilation errors due to the collections package required being a mismatch. I understand that this is just the way it goes with these package systems... However, could you provide a ballpark ETA regarding parity for this package with entities?

8548139--1142681--upload_2022-10-29_7-19-16.png

Another less impactful problem is that the DataStreamReader and DataStreamWriter types conflict with the ones in the Collections.

I really want to get the new collections, logging and the Blobs part of the entities package, but I have a rollback engine built on top of Unity Transport. While I can just get the package locally and fix the errors myself for now, I wanted to plan for the time when I'll need to update the Transport package to fix this. Here's my package manifest, just in case you need it.

manifest.json

[spoiler]

{
"dependencies": {
"com.playeveryware.eos": "git@github.com:PlayEveryWare/eos_plugin_for_unity_upm.git",
"com.unity.2d.sprite": "1.0.0",
"com.unity.addressables": "1.21.1",
"com.unity.ai.navigation": "1.1.0-pre.1",
"com.unity.burst": "1.8.0",
"com.unity.cinemachine": "2.9.2",
"com.unity.entities": "1.0.0-exp.12",
"com.unity.ide.rider": "3.0.16",
"com.unity.ide.visualstudio": "2.0.16",
"com.unity.ide.vscode": "1.2.5",
"com.unity.inputsystem": "1.4.3",
"com.unity.jobs": "0.70.0-preview.7",
"com.unity.logging": "1.0.0-exp.7",
"com.unity.memoryprofiler": "1.0.0",
"com.unity.playablegraph-visualizer": "0.2.1-preview.3",
"com.unity.render-pipelines.universal": "14.0.3",
"com.unity.sequences": "2.0.1",
"com.unity.test-framework": "1.1.33",
"com.unity.textmeshpro": "3.0.6",
"com.unity.timeline": "1.7.2",
"com.unity.transport": "1.2.0",
"com.unity.ugui": "1.0.0",
"com.unity.ui.builder": "2.0.0",
"com.unity.modules.ai": "1.0.0",
"com.unity.modules.androidjni": "1.0.0",
"com.unity.modules.animation": "1.0.0",
"com.unity.modules.assetbundle": "1.0.0",
"com.unity.modules.audio": "1.0.0",
"com.unity.modules.cloth": "1.0.0",
"com.unity.modules.director": "1.0.0",
"com.unity.modules.imageconversion": "1.0.0",
"com.unity.modules.imgui": "1.0.0",
"com.unity.modules.jsonserialize": "1.0.0",
"com.unity.modules.particlesystem": "1.0.0",
"com.unity.modules.physics": "1.0.0",
"com.unity.modules.physics2d": "1.0.0",
"com.unity.modules.screencapture": "1.0.0",
"com.unity.modules.terrain": "1.0.0",
"com.unity.modules.terrainphysics": "1.0.0",
"com.unity.modules.tilemap": "1.0.0",
"com.unity.modules.ui": "1.0.0",
"com.unity.modules.uielements": "1.0.0",
"com.unity.modules.umbra": "1.0.0",
"com.unity.modules.unityanalytics": "1.0.0",
"com.unity.modules.unitywebrequest": "1.0.0",
"com.unity.modules.unitywebrequestassetbundle": "1.0.0",
"com.unity.modules.unitywebrequestaudio": "1.0.0",
"com.unity.modules.unitywebrequesttexture": "1.0.0",
"com.unity.modules.unitywebrequestwww": "1.0.0",
"com.unity.modules.vehicles": "1.0.0",
"com.unity.modules.video": "1.0.0",
"com.unity.modules.vr": "1.0.0",
"com.unity.modules.wind": "1.0.0",
"com.unity.modules.xr": "1.0.0"
},
"registry": "https://packages.unity.com",
"testables": [
"com.unity.collections",
"com.unity.entities",
"com.unity.jobs"
]
}

[/spoiler]

Thanks

You should update to the latest experimental release of Unity Transport 2.0. At the time of writing this message that would be version 2.0.0-exp.8. It takes care of all incompatibilities you have identified, and is what we recommend installing if using it alongside Entities 1.0 (it's the version Netcode for Entities 1.0 depends on).

Here's a guide on how to update from transport 1.X to 2.0.

This is great! Thanks :smile: