You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: