Honorbuddy Startup Error

[everix]

When I try to login with Honorbuddy (latest release) I get this error "Invalid Executor use in GetObjectName". I verified that I do have .NET Framework 3.5 installed (using the verification tool linked in the wiki). I tried with a fresh Honorbuddy install and still got the same error. This is on Windows 7 Professional 64-Bit by the way.

Also, last time I remember Honorobuddy working was before I installed Microsoft Visual Studio 2010 Professional. Don't know why that would have messed it up though.

 

[Tony]

your pic is too small,we cant see anything
make sura that you are on this net framework version(try a repair on a new installation)

Download details: Microsoft .NET Framework 3.5 Service Pack 1

 

[everix]

Well, I reinstalled Windows 7 and I'm still getting the error. Also, that version of .NET Framework comes pre-installed on Windows 7 so the only way to repair it is to either reinstall Windows or do the whole sfc /scannow command which isn't finding anything. I'll give reinstalling WoW a try tonight when I have the free time download 15+ gigs of data (since I've just been copy + pasting back onto my hard drive).

Gonna try and get a bigger pic too, but the error window will only stay open every once in a while.

 

[Tony]

hmmm...on win 7 you shouldnt have a problem with net unless its broken

the pic is still small
Hb creates a log?(check at your Hb folder,there is a sub-folder called logs)
if yes post it as attachment

and the error has nothing to do with your wow installation

btw the error has nothing to

 

[everix]

I attached the log and am still working on getting a better picture, however I can't seem to get the window that shows the error to stay open anymore. I see it flash as the program exits but it doesn't actually stay open.

 

[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"

 

[everix]

That would be the problem, it must've started up after I shoved the DX11 line into my config file the other day. Now that you mention that though I do remember seeing something a while back about that. Thanks for the help Tony!

 

[Tony]

you are welcome