nv_cache error on cloud build, local build is fine

I keep getting this error in a standard win 64 cloud build :

"Player export failed. Reason: IOException: Failed to Copy File / Directory from ‘Library/nv_cache.asset’ "

But haven’t got a clue what it means and where to start looking for fixes. Has anyone an idea where to look?
Local builds don’t give errors and finish normally.

Looks to be related to the VRWorks plugin:

8852: [Unity] IOException: Failed to Copy File / Directory from 'Library/nv_cache.asset' to '/BUILD_PATH/anymotion-nl.studio-vr.default-windows-desktop-64-bit/temp.n3OciQ/Default Windows desktop 64-bit_Data/nv_cache.asset'.
8853: [Unity]   at (wrapper managed-to-native) UnityEditor.FileUtil:CopyFileOrDirectory (string,string)
8854: [Unity]   at NVIDIA.VRWorksBuildPostprocessor.OnPostprocessBuild (BuildTarget target, System.String pathToBuiltProject) [0x00025] in /BUILD_PATH/anymotion-nl.studio-vr.default-windows-desktop-64-bit/Assets/Plugins/VRWorks/Scripts/VRWorks.cs:23
8855: [Unity]   at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (object,object[],System.Exception&)

What version of the plugin are you using? I noticed some mentions of that error in the reviews of the asset store package that suggest upgrading.

Thanks for the tip!

I had VRworks imported (last version asset store) to test if performance over OpenVR would increase, but haven’t got around to it.

I’m currently not using VRworks at all, but every time I delete it from my project, it automatically gets added again. Don’t know why or how it keeps coming back. I thought as I didn’t use it, it shouldn’t be a problem just sitting in the project dir.

Any idea on how it gets re-added everytime?

Hi, did you work it out? If yes, could you please share your solution?

hard delete (shift delete) VR works dir in windows explorer and restart Unity. After loading scene directly sync to cloud. now it should be gone and stay gone. Good luck.

1 Like

Worked perfectly for me on a non-cloud, local build when I did the hard delete. Thanks for the solution.