pontius001
New Member
- Joined
- Mar 15, 2010
- Messages
- 260
- Reaction score
- 3
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.
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.