Inquiry on Reducing Input Lag for Third-Party Controller in Apex Legends

[FTWx123]

I hope this message finds you well. I am currently using your syscon plugin on my Nintendo Switch and I'm enjoying the enhanced gaming experience it provides. However, I've encountered an issue while playing Apex Legends.

I've noticed that there is a significant input lag when using my third-party controller. This lag affects my gameplay, especially in fast-paced scenarios where quick reactions are crucial. I was wondering if you could provide some guidance or suggestions on how to reduce the input delay for my third-party controller while playing Apex Legends.

My controller is DualSense Edge

[o0Zz]

Hi,

Interresting issue, the polling frequency of sys-con is 1ms (thus 1000 hz) which is a lot more than any controller. Thus the limitation is more on controller sides that are not be able to provide information at such frequency.

1- Could you please confirm that you didn't enable debug logs ? (Check if log_lvl=2 or more) 2- Could you check with another controller to see if you have the same issue (for example a wired controller ?)

The idea is to check here if it's an isolated issue with DualSense or if it's a more general issue.

If some other player have the same feeling, please post your comment in this ticket.

[FTWx123]

Thank you for your prompt response and valuable insights.

I confirm that in my config settings, the log_lvl is indeed set to 2, and I have not made any changes to this setting.

Regarding the testing with other controllers, I understand your suggestion. I will experiment with a different controller to see if the input latency issue persists.

As for my main concern, I am looking for advice on how to reduce input latency during frame drops. Specifically, in complex scenarios like face-to-face combat in Apex Legends, I notice what seems to be increased input latency. I'm curious if there are any specific settings or optimizations that can help minimize this latency during such situations to enhance the gaming experience.

[o0Zz]

You need to test with an official switch controller in order to compare both (with sys-con and without sys-con) because if you meet the same issue without sys-con, there is nothing to do here since you probably reach the switch limits. I prepared a new build in order to let you play with sys-con.

There is 2 new settings:

polling_thread_priority=
log_level=

polling_thread_priority allow you to change the priority of the polling thread, you can try to set it on the maximum (63) and see what's happen. I do not warranty any result, but you could try (The default value is 48)

log_level has a new level named: "performance". It's here to track performances of sys-con, you can enable it by setting log_level=2 (Note that now the default log_level is 3 - and no more 2 like it was on the previous versions) - then look in the logs if you note any latency during your lags.

Before doing any change, first try this version without any change just to make sure you reproduce the issue, then try by playing with polling_thread_priority and if there is no improvment try to set log_level=2 in order to check in the logs how many times is needed to sys-con to execute the basic functions like reading the controller, parsing data, mapping your controller (It can give you an hint where is the bottleneck)

sys-con-1.4.3+3-ATMOSPHERE-1.7.x-1.8.x.zip