Add Input Time Debugging to Logger #115
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
stale
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-streetpea/chiaki-ng#115
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Device: ROG Ally Z1 Extreme
OS: Windows 11 22H2
Chiaki build: latest windows release
1080P, 60FPS, 30000 bitrate
Using the latest windows Chiaki build on ROG Ally, I am experiencing a slight input delay of about .5 seconds. This becomes very noticeable in games such as Doom Eternal and Dead Space. Is there any documentation on how to configure settings to improve the input delay?
Also, could you add input debugging for response time in logs?
The biggest thing would be to hardwire your ps5 (via Ethernet) if it isn't already. Beyond that, I would try the following list of things https://streetpea.github.io/chiaki4deck/setup/configuration/#troubleshooting-performance-issues and see if they help your situation
Yup, my PS5 is already on ethernet and I've followed the docs exclusively.
Turns out ROG Ally can cause ping spikes when using Silent Mode power template. Swapping to Performance+(Can also adjust power settings) fixed ping time and improved the input delay I was experiencing.
Would it be possible to add input debugging to the logger? This way, if this issue occurs again I can turn on verbose logging and see if my response times have improved or got worse based on settings I've changed.
Thanks!
@jbaiter would the performance overlay you were thinking of have this kind of info (i.e., ping time, etc.)?
I'm not sure, we get the current round trip time from the console, that might be related to the input lag, but I'm currently not 100% sure how to interpret the value, since it's quite different from the ping times I'm getting from the console. Need to investigate more.
This issue is stale because it has been open for 90 days with no activity.
This issue was closed because it has been inactive for 30 days since being marked as stale.