stone19delta
New Member
- Joined
- Apr 6, 2014
- Messages
- 43
- Reaction score
- 0
Hi there, Tried starting Honorbuddy both from launcher and the honorbuddy.EXE once in game and it just sits at the logging in screen. I tried deleting the settings folder and re logging but I am still having the same issue. I have pasted my LOG. Any ideas?
[14:46:27.829 N] Honorbuddy v2.5.10811.740 started.
[14:46:32.969 N] Logging in...
[14:46:33.334 N] T: 5247064374357431984 H: 4256508816
[14:46:37.050 D] System.IO.FileLoadException: Could not load file or assembly 'RemoteASM, Version=2.5.10811.740, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'RemoteASM, Version=2.5.10811.740, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda'
at GreyMagic.ExternalProcessMemory.Init(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm)
at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits)
at Honorbuddy.MainWindow.HandleSuccess()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
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].
[14:46:27.829 N] Honorbuddy v2.5.10811.740 started.
[14:46:32.969 N] Logging in...
[14:46:33.334 N] T: 5247064374357431984 H: 4256508816
[14:46:37.050 D] System.IO.FileLoadException: Could not load file or assembly 'RemoteASM, Version=2.5.10811.740, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'RemoteASM, Version=2.5.10811.740, Culture=neutral, PublicKeyToken=3c0d9607d7ff1dda'
at GreyMagic.ExternalProcessMemory.Init(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm)
at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits)
at Honorbuddy.MainWindow.HandleSuccess()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
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].
Last edited:
