- Welcome to Bitsum Community Forum.
Development (period)
Recent posts
#91
Process Lasso / Re: CPU affinity not persisten...
Last post by dfhy7had - April 13, 2026, 02:59:15 AMMake sure Process Lasso runs at startup, use "Always" (not temporary), and apply it to the actual game .exe, not the launcher. Also run it as admin.
If it still doesn't stick, the game might spawn child processes, so try a watchdog rule to reapply it.
If it still doesn't stick, the game might spawn child processes, so try a watchdog rule to reapply it.
#92
Process Lasso / Re: Call of Duty via Xbox App ...
Last post by aoihdya - April 12, 2026, 11:04:28 PMYou're not doing it wrong — you just can't reliably force it.
Windows + AMD scheduler decides CCD usage, and Call of Duty often ignores V-Cache preference. Process Lasso rules usually get overridden (or blocked by anti-cheat).
Bottom line: no consistent "safe" way to lock it to CCD0. If it doesn't choose it itself, you're out of luck.
Modern CPUs: more cores, less control. Brilliant evolution.
Windows + AMD scheduler decides CCD usage, and Call of Duty often ignores V-Cache preference. Process Lasso rules usually get overridden (or blocked by anti-cheat).
Bottom line: no consistent "safe" way to lock it to CCD0. If it doesn't choose it itself, you're out of luck.
Modern CPUs: more cores, less control. Brilliant evolution.
#93
Process Lasso / Re: For OBS, would obs-ffmpeg-...
Last post by enniferecker - April 12, 2026, 05:10:54 AMYes, adjusting obs-ffmpeg-mux.exe settings via Process Lasso can be beneficial, particularly around CPU affinity, priority settings, and power plans.
#94
Process Lasso / Re: The UI sometimes displays ...
Last post by login404 - April 10, 2026, 05:12:10 AMThe command line of the process was the same as shown in the image when the issue occurred.
No additional parameters
I've encountered the same issue with chrome.exe.
There were a dozen chrome.exe processes running when the issue occurred.
One of them will show a non-existent affinity or CPU set rule.
Other processes with the same name are showing normally.
But this is just a display error in the rule list.
It won't actually apply the affinity or CPU set settings.
I didn't keep a record of the command line for that process at the time.
No additional parameters
Code Select
"D:\XYplorer\XYplorer.exe"I've encountered the same issue with chrome.exe.
There were a dozen chrome.exe processes running when the issue occurred.
One of them will show a non-existent affinity or CPU set rule.
Other processes with the same name are showing normally.
But this is just a display error in the rule list.
It won't actually apply the affinity or CPU set settings.
I didn't keep a record of the command line for that process at the time.
#95
Process Lasso / Re: A few clarifications
Last post by Jeremy Collake - April 10, 2026, 03:40:11 AMThanks! So now we know the power profile change is the primary factor.
We'll continue to chew on this and get back to you.
We'll continue to chew on this and get back to you.
#96
Process Lasso / Re: The UI sometimes displays ...
Last post by Jeremy Collake - April 10, 2026, 03:27:00 AMIs this the only process you've seen incorrectly matched? When it happens, what is the command line of the process?
We made an adjustment in v18.0.1.11 BETA to ensure that matches are more consistent in rare cases where process metadata retrieval is delayed, which can happen when a process is in its creation phase when first evaluated, but I am not convinced this is the cause. This adjustment was necessary but may slow first-time RegEx rule evaluation time marginally.
We made an adjustment in v18.0.1.11 BETA to ensure that matches are more consistent in rare cases where process metadata retrieval is delayed, which can happen when a process is in its creation phase when first evaluated, but I am not convinced this is the cause. This adjustment was necessary but may slow first-time RegEx rule evaluation time marginally.
#97
Process Lasso / Re: A few clarifications
Last post by Peppo - April 10, 2026, 02:18:35 AMTested with CpuEater
Removed from ProBalance "ignore foreground processes, do not affect children, don't act on a different priority,
exclude system services".
In "Standard" mode with the "Balanced" power profile ProBalance works (testlasso.exe priority normal change to minor-)
In "Performance Mode Enabled" mode ProBalance does not work (testlasso.exe priority does not change and remains normal)
In "Performance Mode Disabled" mode with "High Performance" power profile ProBalance does not work (testlasso.exe priority does not change and remains normal)
Options changed before starting CpuEater, all tested individually several times,
For the color and improvements, always excellent.
Removed from ProBalance "ignore foreground processes, do not affect children, don't act on a different priority,
exclude system services".
In "Standard" mode with the "Balanced" power profile ProBalance works (testlasso.exe priority normal change to minor-)
In "Performance Mode Enabled" mode ProBalance does not work (testlasso.exe priority does not change and remains normal)
In "Performance Mode Disabled" mode with "High Performance" power profile ProBalance does not work (testlasso.exe priority does not change and remains normal)
Options changed before starting CpuEater, all tested individually several times,
For the color and improvements, always excellent.
#98
Process Lasso / Re: A few clarifications
Last post by Jeremy Collake - April 09, 2026, 02:30:58 PMDo you observe the failure to act on the CPUEater tool as well? We are theorizing on this but have not yet reproduced it. Of course, when you use the per-process "Induce Performance Mode" setting that process is excluded from ProBalance, but that does not sound like the case here.
v18.0.1.9 BETA adds the requested GPU custom color setting
.
v18.0.1.9 BETA adds the requested GPU custom color setting
. #99
Process Lasso / Re: A few clarifications
Last post by Peppo - April 09, 2026, 12:46:24 PMIt is confirmed (again, hoping there is no misunderstanding) XD
ProBalance does not work in Performance mode.
Test performed on ProcessLasso with a complete reset to default settings.
Leaving "default" mode and launching a decompression program, ProBalance limit the executable.
Closing everything and repeating after enabling "Performance" mode, ProBalance does not limit the executable.
This also occurs when test with "Balanced" power profile, ProBalance limit
also test with "Performance" power profile, ProBalance does not work.
On all tests all cores always work at 100% full with every profile.
ProBalance does not work in Performance mode.
Test performed on ProcessLasso with a complete reset to default settings.
Leaving "default" mode and launching a decompression program, ProBalance limit the executable.
Closing everything and repeating after enabling "Performance" mode, ProBalance does not limit the executable.
This also occurs when test with "Balanced" power profile, ProBalance limit
also test with "Performance" power profile, ProBalance does not work.
On all tests all cores always work at 100% full with every profile.
#100
Process Lasso / Re: The UI sometimes displays ...
Last post by Jeremy Collake - April 09, 2026, 11:44:40 AMHmm. We are looking into how this could occur and will report back.