lorddakkon / diablo-iii-wasd

Automatically exported from code.google.com/p/diablo-iii-wasd
0 stars 0 forks source link

WASD keys not going North, West, South, East #11

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Open Diablo 3 in windowed mode
2. Run WASD AHK

What is the expected output? What do you see instead?
The WASD keys should move the avatar North, West, South and East respectively. 
However, it seems that the WASD keys move the avatar in any random direction, 
mostly that of East.

What version of the product are you using? On what operating system?
I am using 1.2 AFK and have tried both the corners file and the standard one. 
Windows 7 64 bit, but on bootcamp.

Please provide any additional information below.
If I run the AHK file before booting up D3, the WASD keys do not work, however, 
if I boot the game up and then run the AHK file, the WASD keys respond albeit 
not in the correct directions. Maybe this is a problem with bootcamp. I run D3 
on Windows because I get better performance that way. Keep up the good work 
regardless.

Original issue reported on code.google.com by nares...@hotmail.co.uk on 25 May 2012 at 12:02

GoogleCodeExporter commented 8 years ago
I am not familiar with bootcamp are you running it from within a linux or OS X 
client?

Either way bootcamp with Win 7 should provide all the API functions. It may 
just be a window calculating problem with that particular setup. You could try 
this. Go to the downloads section and change the search to Deprecated downloads 
or All instead of Featured. When you do that you will see all the old versions 
of my scripts. 

In that list you should see a script called Window Test or something similar. 
Download that and run it per the instructions. What it does is the same 
calculation my scripts do for window info. You can run it and record the info 
it gives you and get that to me. It might shed some light on what exactly the 
script is doing wrong with your particular setup. 

Once I have that info I will try to look into what is going on. 

If they ever fix the FPS issues with MAC (I am assuming that is what you run on 
natively) then you might just be able to use the new MAC OSX version of WASD my 
newest project contributor has just released. I haven't been able to test it 
myself yet, because I don't own a MAC heh. 

Original comment by jsig...@gmail.com on 25 May 2012 at 2:07

GoogleCodeExporter commented 8 years ago
The OS X WASD program is pretty bad.  It doesn't do foreground window detection 
(so it will click in your web browser when you tab to it), and it doesn't work 
at all with windowed mode.  

Even worse, I don't think the program author even knows how to code.  Just look 
at this snippet:

} else if (S == "1" && D == "1") {
  ...
} else if (D == "1" && S == "1") {
  ...
}

Original comment by Hermi...@gmail.com on 25 May 2012 at 3:51

GoogleCodeExporter commented 8 years ago
I honestly hadn't taken a good look at his code yet. Since I don't own a MAC I 
hadn't planned to support it. His project is in its infancy and he may just be 
learning things as he goes. 

If you can get me the info I asked about I will see what I can do as far as my 
scripts in bootcamp.

Original comment by jsig...@gmail.com on 25 May 2012 at 4:20