Crashs after start

[tumbum]

Hello,

got the following Crashmsg.

Invalid executor used in GetObjectName

Want to start start HB, put in my Logins can choose the WOW ID, after i accept the id, HB crashes.
System is Windows7/64bit, tryd to set it on Compatibility WindowsXPSP3 but everytime the same crash.

Someone can help?

 

[abndrew82]

Can you get a screenshot of the error.

I am having some issues on my work machine right now that is Win 7 64 Bit, but not my other machines including my home that is Win 7 64 but at work I get instant Error 132 as soon as I load HB dont even get to login.

This is the crash I am getting

http://i.imgur.com/1DNRL.png

 

[Kickazz006]

attach the log from hb

 

[tumbum]

Logfile

[18:53:25:286] Loading Honorbuddy 2.0.0.4317 settings.
[18:54:00:426] Authenticating..
[18:54:00:761] Buddy Sessions: 0/0
-----
Shared Sessions: 1/3
[18:54:05:901] Error - Endscene hook failed: Der Wert darf nicht NULL sein.
Parametername: EndSceneProc passed to Executor constructor was invalid.
[18:54:05:919] Attached to WoW with ID 5656
[18:54:15:269] Error saving settings.
[18:54:15:275] System.TypeInitializationException: Der Typeninitialisierer f?r "Styx.Helpers.CharacterSettings" hat eine Ausnahme verursacht. ---> System.Exception: Invalid executor used in GetObjectName
   bei System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   bei System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   bei System.Windows.Forms.Control.Invoke(Delegate method)
   bei ..?()
   bei ..?(Object o)
   bei System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
   bei System.Threading.ExecutionContext.runTryCode(Object userData)
   bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
   bei System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
   --- Ende der internen Ausnahmestapel?berwachung ---
   bei ..()
[18:54:15:302]

 

[Tony]

make sure that your wow is running on dx9
do this /run print(GetCVar('gxApi')) open the chatbox in wow copy paste that press enter. If it prints D3D9 ure all good if it says D3D11 you have to open your Config.wtf file and edit this row: SET gxApi "D3D11" Make sure it looks like this: SET gxApi "D3D9"

 

[abndrew82]

As an update yes running D3D9 here and log is not much help as it never loads enough to create a log

This is the extent of my log

[11:13:58 AM:852] Loading Honorbuddy 2.0.0.4317 settings.

Rest it blank as wow crashes right off.

Is wierd that it is only happening to this computer to me, but will figure out what setting or what on this machine is causing it.

 

[Crydebris]

Having same problem, tried editing gxApi and was set to D3D9. fresh install of honorbuddy and still same problem, crashes as soon as I login so it cant write a log.

 

[Crydebris]

I do get this message tho, "Error - Endscene hook failed: Value cannot be null.
Parameter name: EndSceneProc passed to Executor constructor was invalid.
Attached to WoW with ID 4436"

 

[Tony]

I do get this message tho, "Error - Endscene hook failed: Value cannot be null.
Parameter name: EndSceneProc passed to Executor constructor was invalid.
Attached to WoW with ID 4436"

open your config wtf and make sure that this line SET gxApi "D3D9" is there

you are on an official wow server right?

 

[Crydebris]

Fixed the problem when changing D3D9 it saved the file as Config.wtf file as config.wtf~ no idea why but deleted it and changed it to D3D9 now works.
Sorry about that