Some issues, mainly with broadcasting keys

[Kezo]

Hi,

I want to report some issues I had while using Octopus 1.3.3 and 1.3.4b. I haven't been multiboxing for a few months now and was surprised how much Octopus had changed. It already has been a great tool for me back then, so I wanted to use it again and try out all the new features, but I encountered some issues:

1. The key broadcasting whitelist does not seem to work at all. Broadcasting keys with a blacklist works fine, but as I only want to broadcast a few keys, it is pretty annoying not to be able to use a whitelist.
2. So I was using a blacklist now and playing with two characters, and after a few minutes of playing, my slave suddenly kept breaking follow and running into walls - Octopus was broadcasting EVERY key I pressed, completely ignoring the blacklist. I don't know how this happened, I didn't have a key mapped to activate passall and did not touch any options in Octopus at all. The only way to fix this problem was to restart Octopus. I don't know how reproduce this, but if I find a way to do it, I will let you know.
3. This was the strangest bug for me: I mapped a key to toggle Bypass mode, and every now and then I pushed it it caused some serious graphical issues in the game window that the mouse was currently active in. I tried mapping the toggle function to a different key, but that didn't help. Here's a screenshot where my character textures were changed:


One time this happened all my wall textures were changed, so all the walls were paved with icons from my action bars. /reload doesn't help, alt-tabbing usually seems to fix the textures. Again, I am not a 100% sure how to reproduce this problem, it seems like the problem always occures the first time I press the button after starting WoW or Octopus, and in some other situations. I'm using Windows XP x64 with a GeForce 8800 GT on the one machine and Windows XP x86 with a Radeon 9600 on the other one, the glitches occure on both computers.

[Ughmahedhurtz]

Have you tried this with 1.3.2 to see if it happens there? I've been using 1.3.2 for a while now and don't see any of that behavior.

[skarlot]

to fix the graphics stuff I *assume* you must be using the wowhook. I expect any OSD message would trigger the texture problem. You could update http://www.microsoft.com/downloads/d...a-9b6652cd92a3 and see, but it was released really with 'it works for me' and my understanding of how the linking/versioning to the DirectX runtime DLL's is not crystal clear.

however i just decided to not release any further builds of this app so the key problems you seem to have aren't gonna be fixed. This project = code and support hell. For me, the whitelist is fine, and for it to suddenly broadcast all keys, beats me.

Tooooooooo much.