The latest Serialization (1.00 preview-5) and Properties (1.0.0 preview-5) packages are giving me buckets of errors with the latest Entities (0.7.0 preview-19 )and Platforms (0.2.1 preview-5 )packages.
Indeed, they are not compatible yet. The new version of these packages were released some hours ago and have not been integrated in the com.unity.platforms and com.unity.entities packages. This is our next step.
The com.unity.platforms and com.unity.entities packages will be updated shortly. For now, I would advise to stay at the previous version (0.10.4-preview) to avoid any errors.
Cool. Cheers. I can wait.
But what’s the point of the package manager and dependencies if it doesn’t warn me that things will break if I update? I guess that’s a question for the Package Manager team and not for you. Then again, I won’t bother asking them because they haven’t responded to my last several attempts at letting them know about the many basic things that are broken.
1 Like
@martinpa_unity So Platforms and Entities have now been updated but are still not compatible it appears (at least not Platforms). Can you check that both teams are aware of the other’s existence? There is another thread on this forum about the current mess with packages and dependencies and the absence of communications between teams.
Is this duplicate of this issue?: DOTS Dependency Hell (was: Entities 0.8.0 - missing class PropertyAttribute?)
@transat They are aware. I believe that Platforms has already shipped a version that is compatible and Entities should be the next one to be updated. The integration code is done, we are waiting for green tests and approvals from all parties involved.
1 Like
@diegodeddo The issues are related, but I don’t think so. The user in that thread seems to have pulled the latest versions manually. That will not work until Entities ships with 1.0.0-preview of Properties and Serialization.
1 Like
@martinpa_unity Thanks for the info. My build started failing with the same errors in that thread after updating my ECS+Hybrid packages from the package manager with the latest preview versions.
After struggling with a brute force approach to the update, I’ve successfully settled on this package version combo. If you are having problems with compilation errors due to serialization classes, use these versions for each package you share with the list below.
{
"dependencies": {
"com.unity.addressables": "1.6.2",
"com.unity.burst": "1.3.0-preview.7",
"com.unity.cinemachine": "2.5.0",
"com.unity.collab-proxy": "1.2.16",
"com.unity.ext.nunit": "1.0.0",
"com.unity.ide.rider": "1.1.4",
"com.unity.ide.vscode": "1.1.4",
"com.unity.postprocessing": "2.3.0",
"com.unity.progrids": "3.0.3-preview.5",
"com.unity.quicksearch": "1.5.2",
"com.unity.rendering.hybrid": "0.4.0-preview.8",
"com.unity.scriptablebuildpipeline": "1.6.5-preview",
"com.unity.settings-manager": "1.0.2",
"com.unity.test-framework": "1.1.11",
"com.unity.test-framework.performance": "2.0.8-preview",
"com.unity.textmeshpro": "2.0.1",
"com.unity.timeline": "1.2.13",
"com.unity.ugui": "1.0.0",
"nuget.mono-cecil": "0.1.6-preview",
"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"
}
}
1 Like
the error happen when i upgrade to Platforms 0.2.2 preview 5, I fixed it by delete the entry from manifest file, and delete the library folder, restart the client
1 Like
Deleting the library folder means waiting 8 hours for everything to reimport. And then waiting for another 8 hours for the editor to do its thing again after I switch my default platform back to iOS. Sure, I can reduce that time by doing this and that instead but what I really want is a package manager that works. Failing that, proper up-to-date changelogs and readmes wouldn’t hurt.
Besides, last time I tried Entities seemed to be the problem.
1 Like
Three weeks on. Another update to Platforms without an updated changelog. So I give it a shot anyway… I update. I then update Serialization and Properties as well as they are dependencies. Entities of course then starts throwing up errors. And so I downgrade all 3 of the above packages.
@martinpa_unity any “updates” for me on this?
@transat It should be in the next published version of entities.
Regarding the other packages, I would advise you to use the latest version of entities, as that should link to the proper version of the other packages. Packages that do not depend on entities (such as platforms, properties, serialization, etc.) may update and contain breaking changes that will need to be updated in entities. So the safest approach is to update entities only.
1 Like