After launching HonorBuddy and attaching to WoW HonorBuddy crashes

[shadowspawn]

After launching HonorBuddy and attaching to WoW HonorBuddy crashes "Error - Endscene hook failed: Could not setup Executor; unknown func passed to hook: 83 EC 34 A1 70"

Which Bot?
Honorbuddy when first logging in and ataching to WoW instance error occurs.

Character Information
Priest, 90, Blood Elf, Disp, however same error occurs with multiple characters.

What profile were you using?
Error occurs during initial log in. Didn't load a profile.

Date the bug occured (please be as specific as possible, eg; Weds, 12th of October, at 5:36 AM EST)
Sat, 10th of November 2012 at 10:05am

Please explain, in as much detail as possible, what the bug is.
When logging into honorbuddy and attaching to an instance of WoW launched via InnerSpace HonorBuddy encounters error and exits. Previously (~2 weeks ago) had been using InnerSpace and HonorBuddy with no problems.

Please explain any steps to reproduce this bug.
Launch InnerSpace, create character set with 3 characters via ISBoxer, export config, launch character set, launch HonorBuddy, select any character, error occurs.

Please list all plugins currently enabled (as well as links to any plugins not packaged with HB by default)
Clean installation of HonorBuddy with default plugins. (Removed HonorBuddy directory and downloaded fresh version, installed upgrade and error occurs.)

Which Custom Class are you using? Please include the version, and link if applicable.
Default that comes with installation of HonorBuddy.

Please attach a log for this bug report.
Log attached.

 

[Tony]

make sure you are running Hb and WoW (exe) as admin

also try dx11 instead of dx9

 

[shadowspawn]

I reset up the character sets to use DirectX 11 and verified that running both HonorBuddy and launched WoW instances as Admin. This was working with an older version of HonorBuddy (~3 weeks ago) and there has been no upgrades in InnerSpace or ISBoxer during this time period. I attached the latest logs. Thank you for your help.

 

[Tony]

without InnerSpace or ISBoxer works?

 

[shadowspawn]

Yes if I launch directly from InnerSpace it works without HonorBuddy attached. If I launch the 32 bit WoW process directly I can successfully attach HonorBuddy. Problem exists only when I launch WoW from InnerSpace.

This had worked previously (~3 weeks ago for so) when I was manually leveling my toons up to 85 to 90 while multiboxing and using HonorBuddy's combat bot to handle combat (which worked very nicely). I tried down grading honorbuddy to a previous version (Honorbuddy v2.5.6396.497) that I'd downloaded awhile back, declined the upgrade and it successfully attached to the WoW instance. If I try using the exact same setup using current version (HonorBuddy v2.5.6519.513) I get the error.

I've attached the log from the successful login using the older version of HonorBuddy.

 

[Tony]

we cant help on this tho,it has to do with the 3rd party tool

 

[shadowspawn]

Is there some area that I should contact the Lavish Software (publisher's of InnerSpace/ISBoxer) about regarding HonorBuddy not working? As HonorBuddy was previously working with it, it does seem that there has been a change in HonorBuddy that triggers the issue. Is it using a new API to connect to the WoW process or anything?

Just trying to see if there is some way to contact Lavish and say 'there appears to be a problem using this API when launching WoW via InnerSpace'.

Thank you for any help you can provide.

 

[Tony]

you can do it via their our forums most likely

 

[daviswoody]

any luck with a fix ? I to use innerspace to bot with

 

[daviswoody]

i really think its HB causing the problem. After the patch HB started to crash if i use a older copy of HB it (2.5.6441.507) works with innerspace

 

[Tony]

we never supported 3rd party tools and we never will,sorry

 

[shadowspawn]

I would agree, unfortunately don't know the API that is being used to call into the WoW 32 process that it is failing at to even discuss with Lavish software.