View Issue Details
| ID | Project | Category | Date Submitted | Last Update | |
|---|---|---|---|---|---|
| 0006109 | Valley 1 | GUI | Feb 23, 2012 7:42 pm | Feb 24, 2012 6:44 pm | |
| Reporter | Bluddy | Assigned To | keith.lamothe | ||
| Status | closed | Resolution | no change required | ||
| Product Version | 0.580 | ||||
| Summary | 0006109: Regression - movement directed keyboard aiming no longer working | ||||
| Description | First thing that happened after I updated -- I can no longer shoot straight with my favorite input method. If I shoot now, it goes straight up. Moving forward shoots diagonally up. I've got | ||||
| Tags | No tags attached. | ||||
| Internal Weight | New | ||||
|
|
I'm not able to reproduce what you're seeing, it fires in the direction I'm pressing the keys for. Except when I try it for down-right, in which case it doesn't trigger the ability at all. Looking into that one, perhaps they're related. |
|
|
My bad, sort of. Installing the update reset the direction keys to be WASD. Since I game on a laptop, I've found the best controls for me are the WASD for spells and the direction keys for movement. I did find, however, that if one key is configured twice for moving, for example to quickly clear the WASD keys I put right key as the first key for right (when right key was also the 2nd key) it counts the keys twice. So everywhere I moved, I was using storm dash. |
|
|
Gotcha, I was thinking it was something with bindings, and the unilateral reset in the last version would do that. Thanks for following up on that. My bug with the down-right thing not working turned out to just be that my laptop apparently has a really really really cheap keyboard that cannot reliably tell my computer which keys I've got pressed if there are more than 2 of them being held down :) Interestingly, it can handle down-left-1, but not down-right-1. But my other machine handled it just fine, so it looks like the game just wasn't being given the input, rather than handling the input incorrectly. Anyway, if you want to file the "if you make something both the primary and secondary key for a key-bind it will trigger it twice" issue separately, we can take a look when we get to that level of triage :) |
|
|
Whew, glad that was all it was! Normally we don't reset the bindings, but that update did reset a few. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| Feb 23, 2012 7:42 pm | Bluddy | New Issue | |
| Feb 23, 2012 8:04 pm | keith.lamothe | Note Added: 0019701 | |
| Feb 23, 2012 8:20 pm | Bluddy | Note Added: 0019702 | |
| Feb 23, 2012 8:55 pm | keith.lamothe | Internal Weight | => New |
| Feb 23, 2012 8:55 pm | keith.lamothe | Note Added: 0019705 | |
| Feb 23, 2012 8:55 pm | keith.lamothe | Status | new => resolved |
| Feb 23, 2012 8:55 pm | keith.lamothe | Resolution | open => no change required |
| Feb 23, 2012 8:55 pm | keith.lamothe | Assigned To | => keith.lamothe |
| Feb 23, 2012 8:56 pm | keith.lamothe | Status | resolved => closed |
| Feb 24, 2012 6:44 pm | Chris_McElligottPark | Note Added: 0019763 | |
| Apr 14, 2014 9:28 am | Chris_McElligottPark | Category | Bug - UI => GUI |
