Source Control has broken, I cannot check out any previous changesets without it crashing. If I try and do so, I get hit with the bug splat screen, and in the dev ops source control client, it will say that the previous changeset is checked out, but when I go into Unity none of the files changed.
How do I recover my project?
I deleted and reinstalled the project locally, which stopped the version control from crashing, but now there are many random errors in the console and many of the values of the serialized fields of my game objects have been completely undone, some of them dozens of checkouts old. Why did version control not save those values? What in the world is going on here??
if anybody is reading this, I’m begging you to please don’t use Unity’s version control, find some other way to do source control. I don’t want anybody else to have to go through this.
After cleaning up this huge mess I deleted my project in Unity dev ops and now I strictly only use github for source control.
Hello @holycrapjohn I’m very sorry you are facing all those problems.
Could you be available for a short meeting to check what is going on? We don’t have any other reports matching what you explained and we are very interested in understanding the issue and fixing it. Unfortunately with the data provided there isn’t much we can do, that’s why I’m requesting a meeting.
sure, I would be available. I know I probably sound like some angry, grumpy boor in these forums because I’m always criticizing Unity in some way. However, if you would like me to provide more detail or information to help you guys out I certainly don’t mind trying to be helpful.
It also feels nice that someone actually wants to hear what I have to say as opposed to just getting angry in return and finding a reason to dismiss away whatever problem there is. This is what the overwhelming, vast majority of people do who have 1000+ comments on the forums. They appear to be expert game devs, which is often true, but they are also experts in denial, dismissal, brushing problems under the rug even more so than they are experts in Unity. The problem is so sever that I sometimes wonder if Unity just pays people to defend or praise Unity to make Unity look better than it actually is in these forums
With this said, I actually did delete the project on dev ops and move it over to github. However, I could probably just put it back on dev ops and maybe it would replicate. I already strongly suspect the issue was caused by a package in the asset store named “Tasty Grass Shader” which was caused a huge problem in my project (I left a one star review on that package with more information about the issue). TLDR, when added to a large terrain, it filled my project with an enormous amount of grass mesh and caused my computer to crash even just loading the project. Unfortunately, I think version control automagically added the extreme quantity of grass meshes to version control, which might have something to do with why version control stopped working also. As stated originally, when trying to checkout previous versions of the project, version control would crash, and I was essentially “locked out” of my project.
However, after deleting and creating a new project, regarding the issue of how serialized fields were not getting reloaded in the newly created project, I have no clue what could have caused that. But that was like a “last straw” moment for me and after cleaning things up I switched to git and github.
EDIT: Actually, in hindsight, I was encountering problems with version control crashing and getting the “bug splat” popup in checkouts even early in development when the Unity scene was simple and had no artwork or large assets. So I’m not sure what the root problem might be, it may not be caused by this Tastey Grass package
Well if you are able to repro the issues I would be more than happy to connect.
I’m based in EU so CET mornings are usually fine for me.