Hello, I've been using Process Lasso for about 2 years. I have a potato PC with Intel UHD 630 integrated graphics and an i3 7th gen processor. I usually play Valorant, and because of starters and lags, I started using Process Lasso. I also use Discord while playing. But for the last couple of months, when I play Valorant running Discord in the background, sometimes my mic doesn't work, and my in-game ping starts jumping up and down from 50ms to 100ms consistently. If I close Process Lasso from the background, the issue is fixed automatically; also, when I close Discord, the ping issue is fixed eventually. I uninstalled Lasso a week earlier because of these problems, but without Lasso, Valorant is kinda unplayable. I think there must be some sort of settings I need to fix.
Can anyone please help?
Ensure that the process priority of Valorant and Discord is set to "high" or "real-time" to ensure they receive sufficient CPU resources. Check if the CPU usage of these applications has been accidentally restricted, and ensure that there are no settings preventing them from running properly
Quote from: anyto on October 09, 2025, 09:46:17 AMEnsure that the process priority of Valorant and Discord is set to "high" or "real-time" to ensure they receive sufficient CPU resources. Check if the CPU usage of these applications has been accidentally restricted, and ensure that there are no settings preventing them from running properly
I tried "real-time" for both applications. In that case, when I launch Valorant, Discord's mic glitches, and no one can hear my voice. I have to restart my PC to solve this issue. Additionally, can you give me some insights on how to check if CPU usage is restricted for these apps and other settings?
If you paste your config here by exporting it from "Files > Export Rules" then we can take a look at what you've got set.
I suspect that the issues could ultimately be unrelated to Process Lasso. Sometimes it's hard to tell with sporadic hiccups like that, and not all problems can be solved by rules set with Process Lasso. You may want to try uninstalling Process Lasso for an extended period to get a baseline of your system performance and quirks.
I have tried adjusting settings in Process Lasso or Discord to improve my gaming experience while playing Valorant.
Process Lasso or Discord really takes it to the next level.
Quote from: Jeremy Collake on October 10, 2025, 01:51:28 PMIf you paste your config here by exporting it from "Files > Export Rules" then we can take a look at what you've got set.
I suspect that the issues could ultimately be unrelated to Process Lasso. Sometimes it's hard to tell with sporadic hiccups like that, and not all problems can be solved by rules set with Process Lasso. You may want to try uninstalling Process Lasso for an extended period to get a baseline of your system performance and quirks.
Here is my rules config
{
"$description": "Rulesets for Process Lasso",
"$schema": "https://bitsum.com/json-schemas/2025-02-12-00/schema",
"$title": "Process Lasso Rules",
"cpuModel": "Intel(R) Core(TM) i3-7100 CPU @ 3.90GHz",
"ioPriorityClassRuleOrder": [
"valorant.exe",
"valorant-win64-shipping.exe"
],
"priorityClassRuleOrder": [
"discord.exe",
"valorant.exe",
"valorant-win64-shipping.exe"
],
"ruleSets": [
{
"priorityClass": "High",
"priorityClassEnforcedByRegistry": false,
"processName": "discord.exe"
},
{
"ioPriority": "High",
"ioPriorityEnforcedByRegistry": false,
"priorityClass": "High",
"priorityClassEnforcedByRegistry": false,
"processName": "valorant-win64-shipping.exe"
},
{
"ioPriority": "High",
"ioPriorityEnforcedByRegistry": false,
"priorityClass": "High",
"priorityClassEnforcedByRegistry": false,
"processName": "valorant.exe"
}
]
}
Those don't look problematic, so I don't think the fundamental issue is any of your Process Lasso rules. Closing Process Lasso won't undo the rules it's already applied. It might, however, switch the active power plan -- so pay attention to what power plan you are in.
Anyway, the issue sounds sporadic and suggestive of some other performance issue that you haven't been able to fully mitigate with Process Lasso. As to what else to try, I'm sorry that I don't have any immediate suggestions :o.