The project descriptions says "low input lag"--what are the details? #489
-
|
I'm assuming there isn't zero input lag. Does anybody know just how much there is? Does it vary by input device? Does having the Mission Control service enabled create any extra input lag for native Switch controllers? If so, does disabling the service revert that issue? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
I've never actually done any quantitative testing. The dot point is mainly there because many people seem to believe that Bluetooth inherently has large input delays, and that this will make them worse. Supposedly, on the Switch USB controllers actually have worse input delay than Bluetooth. Of course, by introducing an additional link in the chain of processing input data, Mission Control increases the input delay on all controllers it handles (including official controllers) in theory. The amount of possible delay can vary between controllers depending on how many CPU instructions a controller handler needs to convert one input format to another. E.g controllers that support motion controls also have to do a bunch of additional calculations to calibrate the motion data, whereas official controllers just copy over their data more or less untouched. In practice though, I don't think these delays are significant enough to have any tangible impact on the existing delays without mission control. If someone had the time and means to conduct some accurate tests I would love to see the results. |
Beta Was this translation helpful? Give feedback.
-
|
Wow, I'm amazed by the swiftness and comprehensiveness of your answer, thank you. While I don't have a dedicated slowmo camera, I might use my iPhone to film at 240fps and see if I can detect any kind of lag at that framerate, doing a comparison with sysNAND. |
Beta Was this translation helpful? Give feedback.
-
|
Did you ever perform any tests? I would be very interested in the results. Thanks. |
Beta Was this translation helpful? Give feedback.
-
I designed a setup and started doing some preliminary tests a couple of months ago. I haven't had the time to complete everything, but these are the current standings:
Basically, we can conclude so far:
|
Beta Was this translation helpful? Give feedback.
I've never actually done any quantitative testing. The dot point is mainly there because many people seem to believe that Bluetooth inherently has large input delays, and that this will make them worse. Supposedly, on the Switch USB controllers actually have worse input delay than Bluetooth.
Of course, by introducing an additional link in the chain of processing input data, Mission Control increases the input delay on all controllers it handles (including official controllers) in theory. The amount of possible delay can vary between controllers depending on how many CPU instructions a controller handler needs to convert one input format to another. E.g controllers that support motion cont…