Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steamworks always copies the plugins to an architecture specific folder on windows, this causes issues on editors prior to 2019.3 #379

Closed
LeeHammerton opened this issue Sep 28, 2020 · 1 comment

Comments

@LeeHammerton
Copy link

Editors prior to 2019.3 copy windows native plugins to the root of the Plugins folder. They don't place them into architecture specific folders. While Unity will happily run with either approach, a conflict arises if both styles are used :

E.g. a windows 64 bit standalone player will look for all plugins in Plugins/x86_64 if the x86_64 folder exists, otherwise it looks in the root.

So, if i have a native plugin dll in my build in addition to the steamworks package, then the plugin will never be loaded because it is copied to Plugins but steamworks has created a Plugins/x86_64 folder, and thus the player looks for all plugins in this location.

I believe on versions prior to 2019.3 the code in RedistCopy should be placing the native dlls Plugins folder directly and not in architecture specific folders.

@rlabrecque
Copy link
Owner

This is being tracked here: #389

Some progress has been made!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants