Demonbuddy was working fine until the new update now I get this when I login:
[15:05:56.640 N] Demonbuddy v1.0.1353.300 started
[15:05:58.766 N] Logging in...
[15:05:58.936 N] Error attaching to Diablo III, Reason:System.IO.FileLoadException: Could not load file or assembly 'fasmdll_managed, Version=1.0.1353.300, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'fasmdll_managed, Version=1.0.1353.300, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca'
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
I've searched for that registry value and it isn't in my registry. Tried running both the game and the program as admin and I don't have any third party tools interfering with the game.
Any ideas people?
[15:05:56.640 N] Demonbuddy v1.0.1353.300 started
[15:05:58.766 N] Logging in...
[15:05:58.936 N] Error attaching to Diablo III, Reason:System.IO.FileLoadException: Could not load file or assembly 'fasmdll_managed, Version=1.0.1353.300, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'fasmdll_managed, Version=1.0.1353.300, Culture=neutral, PublicKeyToken=f20f8f99ca0718ca'
at Zeta.MemoryManagement.ExternalProcessReader..ctor(Process proc)
at Zeta.ZetaDia.TryInitialize(Process proc, String& reason)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
I've searched for that registry value and it isn't in my registry. Tried running both the game and the program as admin and I don't have any third party tools interfering with the game.
Any ideas people?
