Community Forum

Hi everyone,

We're getting reports of at least one user having this problem in Unity5 64bit using the latest alpha:


Is anyone else getting this after importing and attempting to use AT2 Alpha 32 ?

I"m seeing this error:

Code: Select all

System.DllNotFoundException: Assets/Plugins/x86_64/AmplifyTextureNativeEditor.dll
  at (wrapper managed-to-native) AmplifyTexture.NativeEditor:HashUtil_ComputeCRC32 (uint&,byte[],ulong)
  at AmplifyTexture.FileUtil.CRC32 (System.String fname) [0x00000] in <filename unknown>:0
  at AmplifyTexture.AssetMonitorCache.Add (System.String path) [0x00000] in <filename unknown>:0
  at AmplifyTexture.AssetMonitorCache.UpdateDB () [0x00000] in <filename unknown>:0
UnityEngine.Debug:LogError(Object)
AmplifyTexture.AssetMonitorCache:UpdateDB()
AmplifyTexture.AssetMonitorCache:Start()
AmplifyTexture.AssetMonitor:Start()
AmplifyTexture.InternalEditor:Start()
AmplifyTexture.InternalEditor:CheckInstance()
AmplifyTexture.InternalEditor:.cctor()
AmplifyTexture.VirtualTextureEditorBase:.cctor()
AmplifyTexture.VirtualTextureEditorBase:.cctor()
UnityEditor.EditorAssemblies:SetLoadedEditorAssemblies(Assembly[])

Hello Eric,

Thank you for letting us know, I will get in touch via email.

We are still working on a solution for the DLL issue.

Thanks

Hello everyone,

We were finally able to debug the issue and it turns out that the solution is quite simple. The DLL issue is caused by a missing Visual C++ Runtime Redist (2013) package, this is why it was randomly working on some machines and failing on others.

Download the Windows package here: Visual C++ Redistributable

We also recommend that you include this package in your client applications or other released products; it’s a common practice to include Redist packages just in case the users do not have the required version.

In any case, we hope that this will only be a requirement for Amplify Texture 2 Build a32. We are working on a possible solution that envolves eliminating the specific dependencies causing the issue and we will soon release a new build (a33).

Hopefully this was the only cause for the DLL issue, in any case, please do let us know if it persists.

We apologize for the inconvenience.

All the best,
Ricardo Teixeira

This issue is now resolved, starting in Alpha 33. VS2013 Runtime installation is no longer required as a workaround.