I fixed my Desync/input Lag/Hitreg in CSGO

[F1zus]

I didnt tested in CS, but I can certainly say that today I have truly solved this sort of problem, so far at least in Overwatch 2, in my machine. With results I have never experienced before. I left all comments about how I did in my interrupt affinity auto file. Though I think this will be for every game.

It's been consistent across different ranked matches.

https://github.com/Anonymous/gaming_os_tw ... o.ps1#L233

Thanks for the work you've done.
Based on the algorithms for the msi interrupt mode and your description in the script, we need to set “msi limit” 34 and higher to forcefully enable the msi-x mode even if the device supports only 8 interrupts.


msi supports up to 32 interrupts simultaneously, which means that with a value of 32 the device will still operate in msi mode.

msi-x has lower latency compared to plain msi.

This needs to be checked.

[kriegsnake]

I left all comments about how I did in my interrupt affinity auto file. Though I think this will be for every game.

It's been consistent across different ranked matches.

https://github.com/Anonymous/gaming_os_tw ... o.ps1#L233

I don´t undestand the script. Can you make a little tutorial with screenshots please.

If I'm not mistaken, it seems like it's a Powershell script, you just need to download the file and then run it. Now I don't know if you just need to run it 1 time or at every restart.

It should not need a screenshot nor tutorial. If you read my message and open the link, it will redirect you straight to the comment lines I left as I mentioned. In the comments, there is my experience from the results and what I did to get to that.

https://github.com/Anonymous/gaming_os_tw ... o.ps1#L236

When I run it with powershell everything is ok, except the first line.

[KingAzar]

I got the same:

2023-09-19 19_36_42-Administrator_ Windows PowerShell.png (69.78 KiB) Viewed 17716 times

Also, I have 13900K, why isn't put on separated cores for each component?

[KingAzar]

You should read my last post before this one instead of doing what you are doing.

Sure, thanks for steering us in this direction, but I believe our attention is primarily centered on this specific post and the outcome it produced:

I didnt tested in CS, but I can certainly say that today I have truly solved this sort of problem, so far at least in Overwatch 2, in my machine. With results I have never experienced before. I left all comments about how I did in my interrupt affinity auto file. Though I think this will be for every game.

It's been consistent across different ranked matches.

https://github.com/Anonymous/gaming_os_tw ... o.ps1#L233

At this point, you're mentioning your PowerShell script line 233, and some of us are still closely following it with the assumption that we just need to run that PS script. If we seem to be making mistakes, please specify where we're going wrong and provide clear instructions instead of leaving us to guess which post you displayed. Keep in mind that some of the people here lack expertise and are simply gamers attempting to resolve that people on the forum are facing. That said we all here appreciate your results and solutions.

[[email protected]]

Can someone screenshot the "MSI mode utility" tool with the settings, which Anonymous is setting with his script?

PLEASE!

[ManWhoSoldTheWorld]

You should read my last post before this one instead of doing what you are doing.

Sure, thanks for steering us in this direction, but I believe our attention is primarily centered on this specific post and the outcome it produced:

I didnt tested in CS, but I can certainly say that today I have truly solved this sort of problem, so far at least in Overwatch 2, in my machine. With results I have never experienced before. I left all comments about how I did in my interrupt affinity auto file. Though I think this will be for every game.

It's been consistent across different ranked matches.

https://github.com/Anonymous/gaming_os_tw ... o.ps1#L233

At this point, you're mentioning your PowerShell script line 233, and some of us are still closely following it with the assumption that we just need to run that PS script. If we seem to be making mistakes, please specify where we're going wrong and provide clear instructions instead of leaving us to guess which post you displayed. Keep in mind that some of the people here lack expertise and are simply gamers attempting to resolve that people on the forum are facing. That said we all here appreciate your results and solutions.

I understand, but you can now ignore that older post and use that one that I mentioned, because changes were made and better clarification were provided.

If you want to know what to execute, depending on what you have, only network.cmd script would be enough, but you can also execute the interrupt affinity auto script if you want, based on what you devices have support for.

I think you did a great job explaining which change the readers of the forum should've looked into. Excellent information! Really enjoyed reading through your GitHub

[KingAzar]

Can someone screenshot the "MSI mode utility" tool with the settings, which Anonymous is setting with his script?

PLEASE!

2023-09-20 10_14_19-MSI mode utility.png (49.5 KiB) Viewed 14846 times

[F1zus]

AI shared a possible way to deactivate INTx (legacy interrupt) and I actually tried with the ethernet device, it just vanish when I did, but since it's a memory change, after a restart, it came back normally.

I dont recommend trying this but I will share here the command and tool.

setpci -s 01:00.0 4.w=0x0000
https://eternallybored.org/misc/pciutils/

01:00.0 is the device address that you have to change from the device you want to make the change on.

In the same zip, there are two executables, one you would use to check the address of the device (lspci.exe), and the other to set (setpci.exe).

I tried disabling INTx for the network card and in my opinion nothing happened, the card was still displayed in the MSI mode utility with all modes (lbi, msi, msi-x).
Then I entered the command to disable the INTx USB controller and it simply disappeared from the system. My mouse has stopped working. After a reboot everything returned.
Now I'll try disabling INTx for the network card and audio card and play a few matches in CSGO. Let's see if this gives an advantage.

UPD:
I entered the command for the network card again and it disappeared from the system for a few seconds, then appeared again. Now I'm starting the game to feel the changes.

[[email protected]]

That alone doesnt not do almost anything. If you read my later post, you would see that, that is not the main thing.

Please don't be so mysterious. Please explain specifically in individual steps how to achieve the same result without the script.


EDIT:

I've read up on the "interrupt" topic a bit, but as an amateur I still don't have much knowledge of IRQ, MSI, MSI-X, Legacy Interrupt.

In my opinion the interrupts interfere with each other. Consequently, the solution would be to select different channels for each hardware (graphics card, network card, sound card, USB) and switch to a continuous signal mode to different CPU cores.

This way you would have the least delay.

Someone else has to answer whether this is even possible. It´s an idea for a solution.

[cursed-gamer]

All games suppose to work just fine after plug and play. You have no idea how many players have zero knowledge about any configurations and "wInDoWs TwEaKs" and they are able to perform very well ingame.