-
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 ?