(INTEL ONLY) An easy way to instantly lower input latency

[dougg0k]

Lol, that is a different script, for interrupt affinity. I suppose it needs to be looked upon too.

Yeah, I dont know almost anything about powershell, but I wanted to automate these repetitive processes, so that's what I been doing.

Sorry about that it is 4:30 am here
i tried the right script giving the same last error

Haha, It's fine, at least there is feedback. That is a different error now, I suppose the value being fetched are not only numbers, that why the errors.

This is what I have been saying, instructions from djdallmann doesnt seem to include complete information, which is why I was not confident in the script being 100%. Like if there were a scenario with non-numbers. I suppose it will stay broken till someone who understand the domain part of it are able to fix or provide complete information. Maybe in a PR.

[sherifmagdy32]

Yeah, I dont know almost anything about powershell, but I wanted to automate these repetitive processes, so that's what I been doing.

Sorry about that it is 4:30 am here
i tried the right script giving the same last error

Haha, It's fine, at least there is feedback. That is a different error now, I suppose the value being fetched are not only numbers, that why the errors.

This is what I have been saying, instructions from djdallmann doesnt seem to include complete information, which is why I was not confident in the script being 100%. Like if there were a scenario with non-numbers. I suppose it will stay broken till someone who understand the domain part of it are able to fix or provide complete information. Maybe in a PR.

Oh well hopefully someone figure this out soon enough
Thanks for your time really appreciate it

[dougg0k]

Yeah, I dont know almost anything about powershell, but I wanted to automate these repetitive processes, so that's what I been doing.

Sorry about that it is 4:30 am here
i tried the right script giving the same last error

Haha, It's fine, at least there is feedback. That is a different error now, I suppose the value being fetched are not only numbers, that why the errors.

This is what I have been saying, instructions from djdallmann doesnt seem to include complete information, which is why I was not confident in the script being 100%. Like if there were a scenario with non-numbers. I suppose it will stay broken till someone who understand the domain part of it are able to fix or provide complete information. Maybe in a PR.

Oh well hopefully someone figure this out soon enough
Thanks for your time really appreciate it

Yeah, for sure.

btw I updated the interrupt affinity script, maybe it wont give those errors anymore.

[sherifmagdy32]

Sorry about that it is 4:30 am here
i tried the right script giving the same last error

Haha, It's fine, at least there is feedback. That is a different error now, I suppose the value being fetched are not only numbers, that why the errors.

This is what I have been saying, instructions from djdallmann doesnt seem to include complete information, which is why I was not confident in the script being 100%. Like if there were a scenario with non-numbers. I suppose it will stay broken till someone who understand the domain part of it are able to fix or provide complete information. Maybe in a PR.

Oh well hopefully someone figure this out soon enough
Thanks for your time really appreciate it

Yeah, for sure.

btw I updated the interrupt affinity script, maybe it wont give those errors anymore.

oh cool
will check it out later tomorrow i can barley stay awake and will report the output

[dougg0k]

Haha, It's fine, at least there is feedback. That is a different error now, I suppose the value being fetched are not only numbers, that why the errors.

This is what I have been saying, instructions from djdallmann doesnt seem to include complete information, which is why I was not confident in the script being 100%. Like if there were a scenario with non-numbers. I suppose it will stay broken till someone who understand the domain part of it are able to fix or provide complete information. Maybe in a PR.

Oh well hopefully someone figure this out soon enough
Thanks for your time really appreciate it

Yeah, for sure.

btw I updated the interrupt affinity script, maybe it wont give those errors anymore.

oh cool
will check it out later tomorrow i can barley stay awake and will report the output

Yeah, be sure to get latest update when you do.

I just had an idea about the non-numeric issue that was happening in the imod usb script, I built a solution, but again, it addressed the problem, but I dont have an intel to know that is going to the right values / address space, someone should test and someone with domain understanding should review and fix if not correct.

I know that for AMD it is not correct, since all I get are zeroes when checking manually.

But, at least now should be closer to be properly implemented.

[sherifmagdy32]

Oh well hopefully someone figure this out soon enough
Thanks for your time really appreciate it

Yeah, for sure.

btw I updated the interrupt affinity script, maybe it wont give those errors anymore.

oh cool
will check it out later tomorrow i can barley stay awake and will report the output

Yeah, be sure to get latest update when you do.

I just had an idea about the non-numeric issue that was happening in the imod usb script, I built a solution, but again, it addressed the problem, but I dont have an intel to know that is going to the right values / address space, someone should test and someone with domain understanding should review and fix if not correct.

I know that for AMD it is not correct, since all I get are zeroes when checking manually.

But, at least now should be closer to be properly implemented.

Does this mean it worked ??

[dougg0k]

Yeah, for sure.

btw I updated the interrupt affinity script, maybe it wont give those errors anymore.

oh cool
will check it out later tomorrow i can barley stay awake and will report the output

Yeah, be sure to get latest update when you do.

I just had an idea about the non-numeric issue that was happening in the imod usb script, I built a solution, but again, it addressed the problem, but I dont have an intel to know that is going to the right values / address space, someone should test and someone with domain understanding should review and fix if not correct.

I know that for AMD it is not correct, since all I get are zeroes when checking manually.

But, at least now should be closer to be properly implemented.

Does this mean it worked ??

It means it ran and without errors, so yes in a way, though now what remains is for someone to check/test if the implementation are correct or not (pointing/changing to the right value) and also figure out what to do for AMD.

Update:

BoringBoredom have been helping out in answering questions at https://github.com/djdallmann/GamingPCSetup/issues/12
Now I am very close to fully understanding, maybe there is a possible solution to be built. But it's going to take more time.

[sherifmagdy32]

oh cool
will check it out later tomorrow i can barley stay awake and will report the output

Yeah, be sure to get latest update when you do.

I just had an idea about the non-numeric issue that was happening in the imod usb script, I built a solution, but again, it addressed the problem, but I dont have an intel to know that is going to the right values / address space, someone should test and someone with domain understanding should review and fix if not correct.

I know that for AMD it is not correct, since all I get are zeroes when checking manually.

But, at least now should be closer to be properly implemented.

Does this mean it worked ??

It means it ran and without errors, so yes in a way, though now what remains is for someone to check/test if the implementation are correct or not (pointing/changing to the right value) and also figure out what to do for AMD.

Update:

BoringBoredom have been helping out in answering questions at https://github.com/djdallmann/GamingPCSetup/issues/12
Now I am very close to fully understanding, maybe there is a possible solution to be built. But it's going to take more time.

Oh cool great work waiting for the final ver

[dougg0k]

It's done.

https://github.com/dougg0k/gaming_os_tw ... on_usb.ps1

[Mimi123]

Hello,

Thank you for your work, amazing stuff!

Although when running the script I get an error as enclosed. Do you have any idea where it comes from? My drivers are up to date