I’m unsure if this report is similar but I tried the steps outlined in that thread without any success.
- new/empty project
- drives formatted NTFS
- Unity install and project folders excluded from antivirus scans
- deleted the package cache
Which version of Cinemachine are you installing, and which exact version of Unity6?
- Unity 6 preview (6000.05f1)
- Cinemachine 3.1.2 · October 04, 2024
Thanks!
When I create a new project using Unity 6000.25f1 (the latest LTS release), and install Cinemachine 3.1.2 from the package manager, I get no errors.
Can you try upgrading your Unity? You are using a preview version.
Upgraded to the latest LTS and Cinemachine 3.1.2 installed without error. Thanks for the support Gregory!
1 Like
That is the version I have as well, and I can’t seem to get it to load or update at all. which is aggrivating because the Lock on system is very crucial with Cinemachine, any reason for this bug?
Can you be more specific? What exactly is the problem you are having? If it’s the same as the one described above, then the solution I gave will also work for you.
It just refuses to Install, and the current version of that was part of the project was causing issues and crashing everything. causing me to have to do a fresh start on unity 6 but I still can’t seem to install it.
If this worked this iss the issue I keep seeing.
There was a new version of Unity 6 dropped, Installed it and I’m still having that issue.
Okay I figured it out on my end.
It seems that Unity 6 doesn’t like to update certain packages if the Project wasn’t installed to C Drive or at the Very least an internal Drive. I work primarily off an External and it seems to have been fine with earlier versions but Unity 6 was flashing errors. I was able to figure this out by Using my Laptop for remote project work to see if I could update things on it and send it back via Version control.
Which I was but other errors flashed. Redownloading the Repo to C on the Desktop fixed the issue. Not entirely idle because if C Drive Dies, I’m SOL thank god for Version control.
But yeah, seems like a bit of a Bug, might want to look into it.
2 Likes
I regret that I upgrade my unity version to unity 6 LTS. I wish I waited a couple of months before upgrading.
Anyway, not only in the Cinemachine package I encountered this problem. I got a few packages that needs to update and re-install. Instead of moving my project to the C: drive, I just unchecked the Read-Only properties of my project folder and I am able to install and update my packages.
Hope this will help for the others who encountered the same issue.