Octopus 1.3.4b thread

1.3.4
Added instance options for sound, maxfps, maxfpsbk.
WoWhook: removed prevention of window going to background (disables maxfpsbk and is pointless with focus-follows-mouse).
WoWhook: now optionally hooks Direct3D ;)
WoWhook: added a green border when window gains focus.
WoWhook: added some on screen status messages.
Focus-follows-mouse has it's own delay value.
Removed the keyboard/mouse hook installed messages.
Fixed bug where toggle keys were getting stuck, and required mapping to itself workaround.
Possibly fixed the bug with LSHIFT being stuck.
Now you can exit the program by holding SHIFT and closing it when 'close to systray' checked.
Fixed checkbox text color not theming.
Broadcast is properly paused on startup.
While cursor broadcasting, server can cross local links (when toggled from the server, i.e. server=active).
Cursor broadcasting also toggleable from any networked client game window.

Bugs n Quirks, Notes, etc.
green focus border will jump to window in the bottom right, with focus-follows-mouse on, due mouse hiding.
when hooking direct3D seems to crash out on startup now and again.
sticky keys assumed fixed unless reported.
Incompatibility's with Xkeys/G15.

Todo:
key uprades: Round robin, per instances mappings, etc.
fix mapping to scan codes
tab stopping!

1.3.4b addresses the DLL hook causing a crash on load, and is loaded only if needed, and won't crash :P.
Just to clarify a copy of the hooking DLL is loaded by Octopus to communicate with itself, it's never was/is loaded into WoW unless specified.

Upgraded from Octopus 1.3.3 and after starting Ocotopus 1.3.4, I receive the following error message:

Code:

---

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
  at Octopus.Components.Client.ClientConfig(Config conf)
  at Octopus.Components.Client.TransferConfig()
  at Octopus.MainWindow..ctor()

---

Fresh run without configuration file is not working, too.

I received same error message, and program crash, going back to try out 1.3.3. Great software.

After upgrade to DX10, or whatever the version MS currently have on their website, 1.3.4 and 1.3.4 work great

However, I'm still using 1.3.3 because there is a function that was missing in 1.3.4 and 1.3.4b, in 1.3.3 every windows of wow acted like they are on top, I can just do 1 click to skin/pick up item or target mobs, as for 1.3.2 and older + 1.3.4, this function seem missing, I have to go back the old way, click an instance to bring it on top, than do rest of the clicking in it.

ok make sure you have the latest DirectX http://www.microsoft.com/downloads/d...displaylang=en. Note that 9.0c alone might not be sufficient, run it again ;). The WoWhook (tm!) depends on this now and i'm too lazy to do another release right now.
:)

Not using WoWHook here. Plus I have WIndows Vista with Service Pack 1, thus I do have DirectX 10.1.

it doesn't matter in this build, its loaded by Octopus on startup. And DirectX 10 != DirectX 9.

I'm trying to get the WoWhook feature to work, not sure if I am doing it right.

I have on the Client, WoWhook with everything checked, and in my profile for each instance, "Inject WoWhook DLL" box is checked, is this correct? Because when I mouse over an instance, it still has me click on it to gain focus.

the wowhook is not focus follows mouse, totally seperate. focus follows mouse is on client/mouse. it's a windows feature also found in TweakUI or Ease of Access in Vista.

Hi. I just started dual boxing this morning haha and i tried out octopus because I didnt wanna drop 10$ haha. I have had a little problem though where whatever key I press in the enter key combo box becomes "home" and I am unsure how to fix this...All other aspects of the program run great and I am very happy with other than this problem as it looks like it will be great fun...

the home key could be, a stuck key on the keyboard or via anything else like a mouse driver or something. pretty confident it's not a code error!!!. although, try it when the server is stopped.

enjoy, free things ftw :)

Not a stuck key but I'm pretty sure it's some driver of some sort and not coding haha just unsure of how to fix it...Could you possibly upload a key file that only blocks out the up down left and right keys so i could import it by any chance? Those are the only keys I need to block as the rest is working perfectly...

Just want to bring this to your attention, not sure if it was ment to do so, but there was a click function in 1.3.3 that is missing from 1.3.4b.

1.3.3 seem to treat every wow instance as it's on top, I can move my mouse over and do my regular operation, this click function is missing, 1.3.4b I'll have to click on each instance first before I can do anything.

For example, turn in quest, in 1.3.3 I can right click and turn in quests, in 1.3.4 I'll have to double click to turn in quest, it essentially is a double click, but when moving through many alts, it can slow down a bit.

Not sure if the software was meant to do so.

WoWhook: removed prevention of window going to background (disables maxfpsbk and is pointless with focus-follows-mouse).

it's not bad feature but needs an option. I didn't really like it because, even if the mouse focused the keyboard didn't.

and no, if your windows reports your home key is down, its your problem. i may look at adjusting the key catching in a future version.