input latency #93
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
upstream
wontfix
No Milestone
No project
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: unfa/liblast#93
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
there seem to be an input latency
when i move the mouse, it feels like it takes 0.5 seconds until i see movement on the screen. it is noticable and the game is not really playable in this state
i was not able to capture that in a screen recording because that also seem to have some lag
for a competetive game, you really have to optimize the input lag
Liblast 0.1.0-pre-alpha
Run inside steam-run FHS bwrap container on NixOS 21.11.git.b7bd131f9cf
I wonder if the bwrap container could have an impact.
I have not experienced any input lag, and have not seen a report of that happening, I wondere if it coould be an engine issue.
Could you please test running the game without any container on top?
(I don't know what bwrap even is to be honest).
Does this problem persist in 0.1.1.1-pre-alpha?
I haven't had anyone complain, if so - I am afraid it's an upstream problem in Godot engine.
@davidak - could you test this again in the latest
main
branch? We've updated the Godot engine a few times since it was tested last so maybe it's not longer the case?If it is - pleasse report it to Godot team.
However - I know Godot wa implementing some new input system to lower the latency, maybe it's already fixed, or can be fixed fro you just by enabling that feature.
If that doesn't help I am afraid it's nothing we can fix in Liblast.
If thre's a problem still - it's upstream. We're not mesing wiht anything here.