For sometime now, I have been using ISBoxer along with Honorbuddy to do my own dungeons and raids since the population and quality of other players has gone down considerably. They worked quite flawlessly together where I was able to switch windows on the fly, better cpu and memory consumption, and so on. The latest patches however finally caused me to start getting the "Endscene" error after starting ISBoxer windows and then attempting to start Honorbuddy. Last week's World of Warcraft, HB 520, and ISBoxer worked just fine. So, I began to search to see if I could get it working again. There are quire a few Honorbuddy users who seemed to use ISBoxer but ended up with this error and it has been going on with many people for months. It was stated in one of the posts here on Honorbuddy forums that the issue with both programs trying to hook into the DirectX and that both cannot causing the error. When I continued on someone else's post asking if there has been any updates, Honorbuddy developers state that you should get support from Innerspace. One user in these forums states that the HB devs and the Innerspace devs know each other. I ended up contacting Innerspace devs to find out what they know about the issues. I informed him that I would be posting this information on the Honorbuddy forums to help others and to eliminate some of the questions that might be asked over and over. Here is what I got (paraphrased of course)... Innerspace devs do not know HB devs. Apoc (HB dev) used to hang out in their chat rooms back in the ISXWoW/ISXWarden days, but hasn't dropped by in some time... It has been rumored that HB thinks InnerSpace is going to disappear. He doesn't really know. As for people asking Innerspace devs about this issue, no one has brought it up. (It is against their forums to talk about bots, so they delete them pretty quickly when mentioned.) The Innerspace devs have no idea why HB would fail to work with ISBoxer as nothing towards the DirectX has actually changed. If you think it is is ISBoxer/Innerspace related, you can grab build 5670 from the archives to see if you observe different behavior, but he thinks the behavior will remain the same. He then goes on about the only way to tell how they are interacting or not interacting properly together, source code would have to be checked. Unfortunately, it is unlikely that HB devs would give the source code over to Innerspace devs and Innerspace devs would not likely give the HB devs their source code. This leaves us with the continued issue of incompatibility.
I haven't talked to Lax in a long time, correct, and no, we're well aware that InnerSpace will be around for quite a long time. It's only died off as a botting platform. We'll see what we can do about the incompatibility. This is something we should be able to fix on our end. Could you give me some more information on your setup so we can properly test and fix the issue? Windows version (Vista, 7, 8) Any anti-virus A log of the error (if possible) Any other useful information you may have.
Sorry for the delay... Windows 7 x64 bit Ultimate ver 6.1.7601 AMD FX-8150 32GB (2x16GB Corsair PC1866) MSI MS-7640 ATI Radeon HD 7870 Seagate Momentus XT750 Hybrid in AHCI mode Antivirus is Microsoft Security Essentials 1.141.2149.0 World of Warcraft 5.1.0 (16357)(Release x86) using DirectX 9... also tried DirectX 11 with same results Inner Space v1.11 (Build 5751).... also tried Build 5670 as Lax suggested to try. Honorbuddy 2.5.6647.521 and HonorbuddyBETA 2.5.6647.84 My HB log is attached. And as I said, I was working just fine with HB 507 and later 513 until I was forced to upgrade both WoW and Inner Space along with the HB.
I have the exact same failure..... I use ISBoxer with D3 and have no issues, but HB crashes instantly when trying to use ISBoxer with WoW View attachment ISBOXER instant crash.txt
Is there any update on this compatibility Apoc? I'm considering buying another set of 3 HB keys and an isboxer key for some more experimentation.
Apoc, this would be AWESOME to get back so it is usable. At present time an HB start with ISBoxer just crashes. If I can help somehow, please holler. Thanks!!!
This is something that I would REALLY like to see working again. Either that, or some sort of really stable built in feature without the current sluggishness when trying to make it work through various plugins.
it's a kind of attempt HB monopolize DX hooks? =) Anyway, i have similar problem. I'm wrote small program for my purposes which place hook in dx, and HB throw an error when trying to enumerate wow's windows StyxWoW.Helpers.CharacterSettings (i'm assuming it's first place to hook wow)
ya, I have to throw my hat in and say this would be my most strongly requested fix at the moment. and ya... I know that making HB work and play well with others takes a way way back seat to just working right no matter what else happens. I know there are more issues that everyone wants and thinks are the most important depending on the point of view of each person. still, for me... this is really disappointing hopefully it's fixed soon. (keep up the good work on the other stuff though guys, it is appreciated).
