input latency #93

Closed
opened 2021-10-03 23:07:39 +02:00 by davidak · 4 comments

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

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).

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).
gilgamesh added the
bug
label 2021-12-14 16:01:34 +01:00
Collaborator

Does this problem persist in 0.1.1.1-pre-alpha?

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.

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.
unfa added the
question
label 2021-12-14 16:22:29 +01:00

If thre's a problem still - it's upstream. We're not mesing wiht anything here.

If thre's a problem still - it's upstream. We're not mesing wiht anything here.
unfa closed this issue 2022-01-03 15:29:38 +01:00
unfa added the
upstream
label 2022-01-03 15:29:45 +01:00
This repo is archived. You cannot comment on issues.
No Milestone
No project
No Assignees
3 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: unfa/liblast#93
There is no content yet.