This could explain some of the issues students are having installing since the switch to 0.50.0. Unfortunately, from what I’ve been able to glean from Unity, 0.50.0 is considered a “breaking” update, in that it renders certain features of 0.17.0 “broken”. As such, we can’t guarantee that you’ll be able to use the code as Nathan has presented it throughout the remainder of the course. I haven’t had a chance to work through the updated Dots to see what’s specifically broken and what’s not, and it’s too soon to record any new patches without more information on what has changed, what works, and what does not. Rest assured, though, that Nathan and the rest of the team are working on it. In the meantime, I have devised a workaround to install 0.17.0, which involves overwriting the manifest.json in the Packages folder of a project. It’s rather brute force, but it gets the project into a state to follow the lectures without error.
Simply replace the contents of manifest.json with:
{
"dependencies": {
"com.unity.collab-proxy": "1.13.5",
"com.unity.dots.editor": "0.12.0-preview.6",
"com.unity.entities": "0.17.0-preview.42",
"com.unity.ide.rider": "2.0.7",
"com.unity.ide.visualstudio": "2.0.11",
"com.unity.ide.vscode": "1.2.4",
"com.unity.physics": "0.6.0-preview.3",
"com.unity.platforms.windows": "0.10.0-preview.10",
"com.unity.render-pipelines.universal": "10.6.0",
"com.unity.rendering.hybrid": "0.11.0-preview.44",
"com.unity.test-framework": "1.1.29",
"com.unity.textmeshpro": "3.0.6",
"com.unity.timeline": "1.4.8",
"com.unity.ugui": "1.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"
}
}
If you do choose to follow along in 0.50.0, I would be interested in hearing about anything that is specifically broken in our code in the new version. Any data points we can get will help us in revising the course in the future to work with the new Entities version.