Game optimizer release for Windows plus obscure CPU setting

[Hyote]

# Core scrambling feature (periodically changes process affinity to different cores)

Wouldn't this add unnecessary overhead due to context switching and a process switching to a different core or ccd even? When this happens, it has to save it's state and then reload it's state. Depending on what processor you have, when switching cores, sometimes it will reload states from ram rather from the cpu cache. And windows already does this on it's own, doesn't make sense to make it happen more often.

Anyways, assigning affinities manually causes a lot of instability just for anyone who is not aware.

Assigning "Win32PrioritySeparation" to a value you (41) prefer would solve a lot of the issues where people think assigning affinities would solve.

The core scrambling is meant to be an experimental feature, hence why it's turned off by default.
The affinity part I don't agree with, but for now this program needs to undergo major changes and I plan it to be around 3 times bigger in features and it sounds bad like this but process manipulation. That's where the affinities really shine.

[soul4kills]

The core scrambling is meant to be an experimental feature, hence why it's turned off by default.
The affinity part I don't agree with, but for now this program needs to undergo major changes and I plan it to be around 3 times bigger in features and it sounds bad like this but process manipulation. That's where the affinities really shine.

You restrict what cores can be used. When you do that. Cores WILL get overloaded and the scheduler can't balance processes across cores. You also run the risk of pinning processes to cores that are specifically for high-priority tasks adding latency if those tasks are driver related. It can also cause a loop where it's trying to load balance but it can't and it continues to try, causing more latency.

Maybe it's different from intel and amds dual ccd design. It caused a lot of instability for my 5900x.

[Hyote]

The core scrambling is meant to be an experimental feature, hence why it's turned off by default.
The affinity part I don't agree with, but for now this program needs to undergo major changes and I plan it to be around 3 times bigger in features and it sounds bad like this but process manipulation. That's where the affinities really shine.

You restrict what cores can be used. When you do that. Cores WILL get overloaded and the scheduler can't balance processes across cores. You also run the risk of pinning processes to cores that are specifically for high-priority tasks adding latency if those tasks are driver related. It can also cause a loop where it's trying to load balance but it can't and it continues to try, causing more latency.

Maybe it's different from intel and amds dual ccd design. It caused a lot of instability for my 5900x.

I mentioned general system instability but only after quitting the first game I launched the program with. It's good that you describe things technically because I really am just creatively experimenting with some settings, especially this one. However it still gives me the feel of my inputs being consistent and also passed latency tests without adding or removing delay.

[RADICTIONRJ]

Sweet, looking forward to checking it out! Your GitHub has helped a lot already.

[Hyote]

Sweet, looking forward to checking it out! Your GitHub has helped a lot already.

Thanks, I'm getting suspiciously many compliments lately.

[Mr1991]

I’m having trouble with your Kernel guide, I generally find any changes Kernel related to have a large effect so wanted to give this a shot, I pointed to Windbg in CMD, then tried your first line which starts with “symchk”, but get “symchk” is not recognised as an internal or external command, curious what I’m doing wrong?

[Hyote]

I’m having trouble with your Kernel guide, I generally find any changes Kernel related to have a large effect so wanted to give this a shot, I pointed to Windbg in CMD, then tried your first line which starts with “symchk”, but get “symchk” is not recognised as an internal or external command, curious what I’m doing wrong?

Did you move LiveKd64.exe into the installed WinDbg folder? Otherwise you just have to find a way to configure symbols, usually WinDbg gives the option as well.

[Mr1991]

I’m having trouble with your Kernel guide, I generally find any changes Kernel related to have a large effect so wanted to give this a shot, I pointed to Windbg in CMD, then tried your first line which starts with “symchk”, but get “symchk” is not recognised as an internal or external command, curious what I’m doing wrong?

Did you move LiveKd64.exe into the installed WinDbg folder? Otherwise you just have to find a way to configure symbols, usually WinDbg gives the option as well.

Yes, sorry for late reply, there was 2 Windbg locations in users\appdata\local\microsoft\windowsapps and then “Microsoft.windbg (with a bunch of numbers)”

I did both just to make sure, how would I go about trying manually?

[Hyote]

I’m having trouble with your Kernel guide, I generally find any changes Kernel related to have a large effect so wanted to give this a shot, I pointed to Windbg in CMD, then tried your first line which starts with “symchk”, but get “symchk” is not recognised as an internal or external command, curious what I’m doing wrong?

Did you move LiveKd64.exe into the installed WinDbg folder? Otherwise you just have to find a way to configure symbols, usually WinDbg gives the option as well.

Yes, sorry for late reply, there was 2 Windbg locations in users\appdata\local\microsoft\windowsapps and then “Microsoft.windbg (with a bunch of numbers)”

I did both just to make sure, how would I go about trying manually?

I have a standalone install instead of the ones offered on the Microsoft website so the path for me is Program Files\Windows Kits\Debuggers\x64
I don't remember where I downloaded it from but finding it was difficult.

[Hyote]

Update: completely remade the entire program with many more functions.