What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

5.3 beta error

Status
Not open for further replies.

callmebuddy

New Member
Joined
May 26, 2013
Messages
8
Reaction score
0
Honorbuddy beta for 5.3 error

I always got this error with beta1 and beta2, pls fix it


Error - Endscene hook failed: {0}
Error attaching Honorbuddy to WoW! - System.NullReferenceException: Object reference not set to an instance of an object.
at (Object )
at Styx.StyxWoW.()
at Styx.StyxWoW.(ExternalProcessReader )
at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits)
-------------------------------
You have not selected a valid instance of WoW to attach to!
Please restart Honorbuddy and choose a valid instance of WoW to use Honorbuddy with!
This version of Honorbuddy only supports WoW Build #16992
You are currently on build #16992
 
Last edited:
at Honorbuddy.MainWindow.FindAndAttachToWoW(Boolean& found64Bits)

Looks like you're running a 64bit game client.
You'll need to run a 32bit game client for Honorbuddy to operate properly.

To do this and prevent any other possible errors, follow these steps:
  1. Start WoW up using the WoW Launcher.
  2. When the launcher starts up, click "Options" at the top left.
  3. A dropdown will appear, click "Game Preferences" on that dropdown.
  4. Where it says "Display Mode" change it to Windowed.
  5. Where it says Graphics API, make sure it's set to "DirectX 9"
  6. Then, where it says "Launch 32-bit client" check the box to the right of it.
  7. Click "Ok" on the menu, then start WoW.
  8. Before starting Honorbuddy, make sure you're logged completely into your desired botting character.


After you've followed those steps, your Game Preferences menu should look something like this:

600553_10200096203431452_217379531_n.jpg
 
Last edited:
View attachment 93420

thanks bro,but i still got the same error.

Hi, Callmebuddy,

Issus such as this belong in the Support forum. We really need the log to analyze.

You might try removing your .NET4 framework, then reinstalling it. (I.e., don't just install again on top of the existing).

If you are not off and away, we really will need to see a log.

Thread closed--please follow up to the Support forum if still doesn't work.

cheers,
chinajade
 
Status
Not open for further replies.
Back
Top