daid / daid/EmptyEpsilon

[SDL-Regression] Controls

Open
#1,739 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Lua
Stars
869
Forks
222
Avg merge
18h 33m
Merged PRs (30d)
1

Description

Although this is a known regression, I figured I should file a proper issue, to keep it visible.

(Though I honestly don't remember anymore if this happened during the change to SDL or due to the change of the keybinding system)

On the older versions, you were able to easily fine-tune your impulse thrust via keybindings. If you left the key pressed, it would go up to 100% quickly, but if you did single presses, it increases/decreases by 10%.
Technically, this is still the case, but the sensitivity is now that high, that it got extremely hard to set a specific value, a single press easily counts as 3 or more. If I try to touch the key as short as possible, I sometimes get the 10% increment, but it is far from reliable.

So I think the threshold time of when a held down button counts as multiple presses, should be vastly increased.
If I have to guess, there is currently no such threshold and the binding is triggered every frame (a test with heavier scenarios, where it is way easier to do single steps, confirmed that suspicion)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue does not name a file, test, or entry point; begin by reproducing the SDL control behavior and locating the keybinding and held-button handling. Done means single presses reliably change impulse thrust by 10% while holding a key continues to increase it toward 100%.

Written by the indexing model from the issue text.

Assessment

Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.