I have created a new project for Unity 6 (6000.0.23f) and try installl Cinemachine package (3.1.2). But have installation error:
How can I fix this?
[Package Manager Window] Error adding package: com.unity.cinemachine@3.1.2.
Unable to add package [com.unity.cinemachine@3.1.2]:
One or more dependencies could not be added to the local file system:
com.unity.settings-manager: EINVAL: invalid argument, futime
UnityEditor.EditorApplication:Internal_CallUpdateFunctions ()
The source of the problem is the Settings Manager package
This is the reason why some other packages are not installed. For some reason I can’t install the Settings Manager package either from Package Manager (it’s not there at all) or via the URL:
The dependency Splines package version 2.0 also has this same issue if you try to import the package in a project on an exfat formatted drive separately from cinemachine. @Unity will Unity 6 support exfat formatted drives in the future?
Curious that the file system would make a difference. Since the error message mentions “futime” it may be because of that tool which I assume may want to read or change the file create/access/modify timestamps but isn’t compatible with exFAT. However “invalid argument” seems to contradict that notion.
I also wouldn’t rule out that this may have been by chance, and the likelihood of issues on an exFAT drive may be higher simply because the drive may have been formatted by another OS and thus may not have the correct permissions set. Could either or both of you verify that the logged in user has full read-write access? Ideally create a new empty project, try to import. If it fails, give the user full permissions and try again.
Would also be interesting to see if the issue also occurs on a newly exFAT formatted drive.
If by chance you run the project off of a USB stick I would generally advice against that. I experimented with a super-super-fast USB3 stick out of curiosity 1-2 years ago but the performance just wasn’t there despite using the best possible configuration.
Both disks were formatted on the same computer and the same operating system. This was a test project created directly on an exFAT disk. After copying this project to an NTFS disk, there were no more problems with connecting packages.
This is a problem of Unity 6 and we have already written about it:
I have an internal SSD formatted with exfat, and I have been creating new projects on it with 2021, 2022 through multiple releases for years. I tried upgrading my project to Unity 6 and that issue arose when I tried to update cinemachine. I then tried to create a new empty project with Unity 6 on the same exfat drive. It threw the same error once I tried to import the cinemachine package into the empty project. When using the Unity 2022.3.50f1 and importing Cinemachine 2.10.1 it does not throw the error. In fact Using Unity 6 with cinemachine 2.10.1 still works, the error is thrown when I upgrade cinemachine to 3.1.2.
Moving the project to a drive with NTFS formatting allows Unity to update Cinemachine to version 3.1.2. So I guess, at least for now, Unity 6 no longer fully supports exFAT formatted drives.
I was getting the same results… my Unity 6 project resided on an external SSD drive using exFAT… and it would not allow me to install Cinemachine. I simply copied the project folder over to my NTFS system and it installed with no issue. Thanks for the help on this!