job000188
Open
Perforce's call to SetDllDirectory() is interfering with other Packages
We've just integrated Audiokinetic's Wwise audio package for Unity and found that it disagrees with Perforce changing the default DLL directory.
The error we're getting is:
Failed to load 'Assets/Wwise/Deployment/Plugins/Windows/x86/Profile/AkSoundEngine.dll' with error 'The specified module could not be found.
', GetDllDirectory returned 'C:\Path\to\Project\Assets\P4Connect\Editor'. If GetDllDirectory returned non empty path, check that you're using SetDirectoryDll correctly.
AkInitializer:Awake() (at Assets/Wwise/Deployment/Components/AkInitializer.cs:171)
AkInitializer:Awake() (at Assets/Wwise/Deployment/Components/AkInitializer.cs:93)
Is it possible to restore the DLL directory after it's loaded the relevant DLLs?
This is so heinous a bug we've had to completely remove the Perforce integration in order to continue using Wwise.
Perforce server version "p4 -Ztag info"
: ... serverVersion P4D/NTX64/2014.2/978861 (2014/12/19)
P4Connect release (look at the bottom right corner of the Perforce Configuration window)
: P4Connect 2.7 betaR.12101
Unity3d Version
: Unity 5.0.0b22 (32 bit)
Operating system version, 32bit or 64bit
: Windows 7, SP1, 64 bit.
We've just integrated Audiokinetic's Wwise audio package for Unity and found that it disagrees with Perforce changing the default DLL directory.
The error we're getting is:
Failed to load 'Assets/Wwise/Deployment/Plugins/Windows/x86/Profile/AkSoundEngine.dll' with error 'The specified module could not be found.
', GetDllDirectory returned 'C:\Path\to\Project\Assets\P4Connect\Editor'. If GetDllDirectory returned non empty path, check that you're using SetDirectoryDll correctly.
AkInitializer:Awake() (at Assets/Wwise/Deployment/Components/AkInitializer.cs:171)
AkInitializer:Awake() (at Assets/Wwise/Deployment/Components/AkInitializer.cs:93)
Is it possible to restore the DLL directory after it's loaded the relevant DLLs?
This is so heinous a bug we've had to completely remove the Perforce integration in order to continue using Wwise.
Perforce server version "p4 -Ztag info"
: ... serverVersion P4D/NTX64/2014.2/978861 (2014/12/19)
P4Connect release (look at the bottom right corner of the Perforce Configuration window)
: P4Connect 2.7 betaR.12101
Unity3d Version
: Unity 5.0.0b22 (32 bit)
Operating system version, 32bit or 64bit
: Windows 7, SP1, 64 bit.
- Status
- Open
- Project
- perforce-software-p4connect
- Severity
- A
- Reported By
- StuartHarrisonSumo
- Reported Date
- 10 years ago
- Modified By
- pmclary
- Modified Date
- 9 years ago
- Owned By
- StuartHarrisonSumo
- Dev Notes
- 2015/12/08: Perforce Dev has not been able to reproduce this issue.
This needs more investigation. Under Unity5 we do not do anything to SetDllDirectory().
Need more information about this so I can reproduce the issue.
Priority: Low - Type
- Bug
This is very curious.
The SetDllDirectory() Code is totally disabled when running in Unity 5 under Windows.
I have some really (IMHO) sophisticated SetDllDirectory() code, but it only runs in Unity 4.X under windows.
When porting the code to Unity 5, I discovered that using it really broke things. Using Unity default locations for DLL's seemed to fix the problem, no code needed.
https://swarm.workshop.perforce.com/projects/perforce-software-p4connect/files/main/src/P4Connect/P4Connect/P4Connect.Main.cs look for SetDLLDirectory() in the code.
Maybe this is a Unity bug with loading multiple assets with Native DLL's ?