search

resonance-audio / resonance-audio-unity-sdk

Resonance Audio SDK for Unity
https://resonance-audio.github.io/resonance-audio/develop/unity/getting-started
Other
297 stars 38 forks source link

CopyFile/Reverting issue with Unity Collab and plugin "audiopluginresonanceaudio.dll" #25

Open mages-gamedev opened 6 years ago

mages-gamedev commented 6 years ago

Specifications

Issue

We are consistently getting the same error for the file mentioned above when attempting to Update/Sync Unity Collab on Unity 2017.3.0f3 (64-bit). Our project has been up on Unity Collab since Day 1 and we already have a few thousand files up in Collab with several plugins and only this file is giving us issues since we imported and synced it yesterday.

Logs

[Collab] CopyFile failed:
From path: 'C:/Users/<project_path>/Temp/Revert/Assets/ThirdParty/ResonanceAudio/Plugins/x86_64/audiopluginresonanceaudio.dll', To path: 'C:/Users/<project_path>/Assets/ResonanceAudio/Plugins/x86_64/audiopluginresonanceaudio.dll'

Additional information

It was only yesterday that we imported and uploaded the Resonance SDK to Collab and members pulling from Collab would get this error/conflict. The only way to resolve this for is would be to constantly restore the latest push - which is unacceptable as we would have to manually copy over our changes to a temporary location and re-apply each one one by one as the restore wipes local changes.

All third-party assets we import are placed in Assets/ThirdParty

We have tried the following solutions:

Here is an experiment of us completely deleting the ResonanceAudio/Plugins folder and re-opening Unity afterwards. Since we are on PC Standalone, only the x86_64 folder got regenerated automatically (as shown in Fig. 1). We suspect this is the cause of the collab conflict issues.

resonance-lib-autogenerated (Fig 1. The regenerated file after removing ResonanceAudio/Plugins folder and restarting editor)

mauskopf commented 6 years ago

Sorry you're experiencing this issue. We're following up with Unity directly since this seems to be a Collab specific issue, and will update you shortly.

monroeberg commented 6 years ago

Sorry you're having this issue. After some testing, it sounds like the best work-around is to delete everything locally and re-download the project from the Cloud when the Resonance SDK has been updated and pushed to Collab. Also, this bug does not appear to reproduce in 2018.1, so when that version is officially released and you are able to upgrade, that seems like the way to go. (It should be noted that once a projects starts having these issues locally, just upgrading Unity to 2018.1 will not fix it. You still need to re-download the project to get it back to a good state apparently.)