| Key: |
VWR-6806
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Yukinoroh Kamachi
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
Issue Links:
|
Duplicate
|
|
This issue duplicates:
|
|
VWR-6232
Petition *against* 1.20 RC - "double-tap to run" implementation
|
|
|
|
|
|
This issue is original of duplicate:
|
|
|
|
|
|
Relates
|
|
This issue Relates to:
|
|
|
|
VWR-6250 Implement User Definable input mapping
|
|
|
|
|
|
|
|
This will obviously cause unwanted behaviour:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, semantically, even if sometimes it doesn't cause any unwanted behaviour, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", or find a way to map it to another key.
|
|
Description
|
This will obviously cause unwanted behaviour:
- Under heavy lag (double-tap to run will be detected first because it is client-side, while other double-tap implementations are detected server-side)
- In scripts where double tap doesn't override animations
- In scripts where double tap expects the character to be walking
Also, semantically, even if sometimes it doesn't cause any unwanted behaviour, no new scripts will dare to use this previously useful key combo because it will be known by users to be used by the client. Scripters yet only have only a few usable keys detected by LSL, taking that one away is a bad move.
Hence we urge Liden Labs to revert this "feature", or find a way to map it to another key. |
Show » |
|
