![]() So, here’s a look at the things we know that have an actual measurable delay effect on the game: Now with all that said, no latency discussion is complete without reviewing the issues that really do lead to a significant delay between actions in-game and actions on-screen. The usual solution to most mouse performance issues is using the K2 App to optimize the mouse for the game being played. This means issues that previously went unnoticed in some games may suddenly be highlighted by KeyMander 2. Additionally, issues with a game's maximum turn speed or its aim/look mechanics are normally masked by controllers, because initiating movement or changing directions at high speed with a thumb stick is nowhere near the speed that can be attained when using a mouse. A wireless controller averages about a 4ms latency (which is counter-intuitive, but that’s another matter for another time), so the KeyMander 2 is technically faster than using a standard wired or wireless controller.Īny performance issues experienced are not due to latency, but rather caused by problems like incorrectly adjusted dead zones, poorly configured mouse settings, exceeding the game’s maximum turning speed, or poor aim/look mechanics built into some games, all of which can cause the mouse to feel laggy, choppy etc. This is actually a huge improvement over the console's normal wired USB bus speed or 125Hz which equates to 8ms of latency. While KeyMander 2 technically does not add any delay itself, there is 1ms of actual input lag (latency) due to the console’s increased 1KHz USB bus speed with KeyMander 2 connected. I tried one match after all these changes were made and I definitely noticed that the aim was more responsive and snappier.One of the most common questions asked by perspective KeyMander 2 buyers is what amount (if any) of delay/lag/latency does the KeyMander 2 add, so it makes sense to address it here in our FAQ for easy reference. As I said, this might be unnecessary but try it out if you don't notice any change from the previous steps. I've been playing on 1.0 base sensitivity so I turned both Vertical and Horizontal to 2.0 and then the base down to 0.5. Under Sensitivity you have your base sensitivity as well as Vertical and Horizontal. This last step might not be necessary but I'll include it anyway. I'm playing Infinite with all the settings on low, just as a side note. In Halo Infinite, change your minimum and maximum frames, 120 for minimum and 300 for maximum. Click on "Power Managment" and uncheck the "Allow the computer to turn of this device to save power" and click OK. Scroll down to find your Mouse, right click and go into properties. Go to device manager and click on "Human Interface Devices". Disable "Enhanced pointer precision" and put the pointer speed on the sixth notch. Check the box and make sure it says "Application".ĭouble check your Windows Settings on your Mouse. Right under "Disable fullscreen optimization" you can see something called "Change high DPI settings", click on this and go down to "High DPI scaling override". Click on the Compatibility tab and under Settings you will see "Disable fullscreen optimization". Go into the Halo Infinte installation folder, right click on the. So this morning I tried some stuff out and I noticed a change immediately. Last night I did some digging on various forums regarding input lag and optimization to see if I could find something that could fix some issues with Infinte. I submitted a ticket to Halo Support and got the response that they will pass it on to the devs. The aiming between Infinte and other FPS titles are like night and day so something is not right. I looked through all the settings provided in-game to see if something was causing it but found no solution. I always thought that aiming with the mouse and keyboard was off.
0 Comments
Leave a Reply. |