search

lorddakkon / diablo-iii-wasd

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

Script not working? #10

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Launch script from desktop using Autohotkey
2.Launch D3 and reassigned all necessary keybinds (F12 to move and WASD to 
nothing)
3.WASD doesn't do anything in game. Click to move still working.

What is the expected output? What do you see instead?
Would like to move with WASD but when any of the 4 keys are pressed, nothing 
happens. Click to move still works. 

What version of the product are you using? On what operating system?
Diablo III WASD 1.2 on Win7 64bit

Please provide any additional information below.

Original issue reported on code.google.com by kpt8...@gmail.com on 20 May 2012 at 12:45

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Fixed. Had to start game BEFORE starting script. 

"Installation Instructions:

1) Run script with autohotkey (or as standalone .exe after compiling)

2) Start Diablo III"

Wrong order?

Original comment by kpt8...@gmail.com on 20 May 2012 at 12:57

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
No the instructions are correct. It should work in either order. I programmed 
the game detection portion of the script to calculate screen information 
anytime the Diablo 3 process was tabbed into or out of, or first detected. 

After starting the script, it will wait for up to 60 seconds to detect if 
Diablo 3 is running/you have tabbed into it. If you wait longer then that the 
script times out and closes giving you an error message. If for some reason 
that isn't working then it may just be a minor incompatibility with your PC and 
you should continue to start D3 first then the script.

Original comment by jsig...@gmail.com on 20 May 2012 at 7:22