Latest stable DOTS package list, for fixing broken project!

[Lapsapnow]

Hello,

My team and I have been working on a DOTS game, and some sort of foul up has damaged our Burst Package.

However. For the life of me, I am unable to find the repository for the latest stable Burst version.

I would seriously - massively - appreciate a list of DOTS package links so I can update our project and get things moving again. The entire DOTS packages space is hard to navigate - understandable as it’s still in preview - but still there should be a reasonably obvious central repository of links.

Unless I’m just blind, which I’d be happy to know.

Thanks
Luke

[Shinyclef]

Are you looking for this?

DOTS Releases - Latest Release: DOTS 0.17

Dear devs, Going forward, this thread will be updated each time a new release of DOTS package sets becomes available. Please use the DOTS forums for discussions and feedback and start new threads where necessary. We are pleased to announce the release of DOTS 0.17. Please see below for the list of packages contained within the release as well as their versions and links to documentation. These packages target Unity 2020.1.9f1. com.havok.physics@0.6.0-preview.3 - (Documentation) (Change Log)…

I don’t see burst listed though… hmm, but it should just be listed in the package manager…

[system]

@Lapsapnow

some sort of foul up has damaged our Burst Package

Version control rollback to working version? Please don’t tell me that you guys are working on something without version control.

Also, all dependencies are listed in the package manager in the description when you turn on the appropriate setting.

[Krajca]

Try removing library folder, probably package cache will be enough. This is assuming you still has your manifest file intact.

[Razmot]

here is my list of working packages, and if you are still stuck, the “reset packages to default” menu works really well.

I tried to install the new unity network transport, it did update com.unity.collections to a newer version that broke com.unity.entities and I had a hard time to resolve that.

[Lapsapnow]

@Razmot

here is my list of working packages…

Thanks Razmot, much appreciated!

LurkingNinja, we have version control. But there’s nothing to revert to, as I have no idea what the real problem is. The burst version was never touched, or anything. I believe - now - that it was a version mismatch.

Thanks Krajca.

[system]

@Lapsapnow

Thanks Razmot, much appreciated!

LurkingNinja, we have version control. But there’s nothing to revert to, as I have no idea what the real problem is. The burst version was never touched, or anything. I believe - now - that it was a version mismatch.

Thanks Krajca.

Among other things version control could help you to figure out what is the problem. You revert one back, test, if the problem persists, then go back one more… you can test what you did without compromising your code.
This is of course if you version control your manifest file and you treat every update as you should: separate, serious events and commit them to version control.