ConsoleTuner

So with the titan 2 and xim apex i get a bit confused with this whole output an input thing...now some say if you dont have keyboard an mouse plugged into the titan shouldnt matter but i notice it does affect aim assist. So what im trying to understand is for example lets say a guy is using just xim apex and is using 500 polling rate. With the titan 2 how could i replicate that? Does output and input need to be 500? Or just input an output can be 1000? Id assume everything should be the same to get the same feel as if you were on just the xim apex. Just hard to understand how all these settings work example some people on titan 2 an xim apex will have titan output 1000 then input 500. An many other differnt ways they do it 1000hz output then 125 input? Is this truly just 125hz? Should titan 2 always be 1000hz? An input be what you have your xim apex set to? Maybe someone can really break down all of this to help me understand...i also wonder do people always run 1000hz output to not add more latency/delay on top of say if they have xim apex set to 500 didnt know if 500 on titan 2 would add another 2ms

Bump? Hopefully j2kbr will be able to answer

To replicate using XIM at 500Hz, configure the Titan Two input polling rate to "Protocol's Default" (so it is XIM that will inform to the Titan Two how fast it should be polled) and the output polling rate to 1000Hz to ensure minimum latency, so the data received from XIM is immediately forwarded to the console.

J2Kbr wrote:To replicate using XIM at 500Hz, configure the Titan Two input polling rate to "Protocol's Default" (so it is XIM that will inform to the Titan Two how fast it should be polled) and the output polling rate to 1000Hz to ensure minimum latency, so the data received from XIM is immediately forwarded to the console.

Ok thanks for the response see someone before said these settings didnt really matter unless you had mouse plugged directly into the titan so i just wanted to make sure so thanks