lorddakkon / diablo-iii-wasd

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

xbox 360 config button 4 broken #9

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?

button 4 is sending the wrong release key

believe it keeps sending button one up.  I already fixed it though on my end.

Also the shift behavior is bad.  its hard to hold down that left joystick.

I changed back the buttons to send proper left click and right click.

I changed left click to also send shift first and on release shift up.  this 
way i can shoot and not attempt to walk.

its weird you didn't map button a.  I kinda think your main for skills should 
be a,b,x,y.  ill do some more tinkering on my end.

attached slightly edited version with stuff i said.

Original issue reported on code.google.com by tracy.ro...@gmail.com on 18 May 2012 at 5:14

Attachments:

GoogleCodeExporter commented 8 years ago
All your changes make sense. I did the layout as I would use the controller so 
it isn't going to be to everyone's liking. Luckily editing which keys works for 
the hotkeys is fairly easy.

I left the A key free to use it as a Vent button myself. I will pull up your 
copy sometime and look it over. Honestly right now I am enjoying the game too 
much to spend time outside of it writing/tweaking scripts.

Original comment by jsig...@gmail.com on 18 May 2012 at 5:23

GoogleCodeExporter commented 8 years ago
with the shift change though it kinda makes it hard to pick up items :)  guess 
will need to think about this.  first time using this particular software.

Original comment by tracy.ro...@gmail.com on 18 May 2012 at 5:23

GoogleCodeExporter commented 8 years ago
Don't be afraid to dive in and learn it. I knew nothing about AHK before I 
started these scripts. 

As far as button 4 sending the wrong key, I have seen that issue before and it 
is usually a missing return some where in the script. Hotkeys go until they see 
a return so that normally is why they do unintended things. It is possible I 
missed something and/or loaded up an incorrect copy by mistake.

Original comment by jsig...@gmail.com on 18 May 2012 at 5:25

GoogleCodeExporter commented 8 years ago
SkillFour:
    Send {4 down}  
    SetTimer, WaitForOneUp, 10
return

there is the code in your file.  it should be waitforFOURup.

Original comment by tracy.ro...@gmail.com on 18 May 2012 at 5:27

GoogleCodeExporter commented 8 years ago
That was a pretty dumb mistake. Thanks for the heads up though. I will fix it 
and get a corrected version up soon.

Original comment by jsig...@gmail.com on 18 May 2012 at 6:19

GoogleCodeExporter commented 8 years ago
ill be tweaking with it more this weekend.  the other change in my config was 
this:

JoyThreshold = 7

the setting you had was too sensitive and my controls would just start walking 
by itself.  maybe my controller is worn out :)  I am also using a wireless 
controller with the wireless puck.

Would like a way for me to be able to turn the left trigger into a normal mouse 
click perhaps if another key was held.  With my shift modification to left 
trigger I can do combat really well but I can't pick up objects or talk to 
people very well.

If you have a mac you should check out controllermate.  I made a pretty great 
WoW config for that.  I was going to try to do this in controllermate but he 
doesn't have code to calculate current mouse position like you are doing.  I 
did a search and someone else also was looking for similar behavior.

Original comment by tracy.ro...@gmail.com on 18 May 2012 at 1:46