I’m using Unity 2017.2.0f3, I keep getting an error:
I DEFINITELY do not have duplicate DLLs. Even Unity references the exact same file in the console error twice. I type the DLL name in the project search field, and only ONE DLL appears. Also, this happens for almost every single Windows platform DLL I have in my project (so about 12 of them). This is not particular to Dissonance at all.
Attached is an image of my inspector settings. Once again, this is the ONLY DLL named opus in my entire project.
The weird thing is sometimes it lets me build and sometimes it doesn’t. But if I disable the “Editor” checkbox in platforms, it lets me create builds every time. But then obviously the DLLs don’t work in my editor until I re-enable it. This is obviously not an efficient thing to do each time I want to make a build or test in my editor. Especially for 12 DLLs.
Also, if I delete the DLL in Unity, it will eventually come back. The only way to “properly” delete a DLL is to close Unity, open Windows Explorer, and delete it from there. It won’t let me delete it while Unity is running.
Has anybody else run into this problem? Any solutions?
Also, is there a way I can write a PreProcessBuild and PostProcessBuild script to maybe change the Editor checkbox when making builds? That way I don’t have to manually change it for all the DLLs.
Any help would be greatly appreciated. This is really frustrating.
Thanks
A bit late, but I’m experiencing the same exact issue with most of my windows native plugins on 2021.3. For me the error appears after loading a scene. The plugins are definitely used before the scene change, and still used after, so my assumption is that it has something to do with Unity erroneously attempting to initialize the plugins again after they’ve already been initialized.
After a lot of troubleshooting, I think I figured out where the issue stems from. In my circumstance I had the same project on two computers synced through version control. One of the computers never experienced the errors, while the other just seemingly out of the blue started getting them. I did a lot of testing to try to figure out what was different, and I found that if I copied the UserSettings folder from the working editor and overwrote the failing editor’s UserSettings folder with it, the errors stopped!
Unfortunately, I wasn’t able to pinpoint what specific file/line/setting that was causing the issue in the first place, as I couldn’t find very specific details on the individual files inside that folder, but I’m confident that’s where the issue/bug resides.
