Hi,
I've set up Process Lasso to configure settings for my games on the Ryzen 9 9950X3D. I'm wondering if there's a way to manage this setup automatically, or at least more efficiently on a manual basis.
Currently, I'm using a process match rule like: D:\Games\* and for specific games, something like cod.exe
However, games installed through the Xbox app aren't being detected, even though they should be located in
D:\Games\*I suspect this is because those titles are actually stored or called in the
WindowsAppsfolder, where Process Lasso can't properly access or match the executables.
Is there any reliable way to make Process Lasso automatically detect those Xbox games?
Alternatively, could I manually edit the configuration file to add something like this?
[ProcessRules]
cod.exe=PriorityClass=High;CPUAffinity=11111111111111111111111111111110;IOPriority=High;ProBalanceExclusion=1;PowerProfile=Bitsum Highest Performance;EfficiencyMode=Off
(similar to the example here: process_lasso_ultimate_gaming.ini (https://github.com/Safaire/process-lasso-gaming-profile/blob/main/process_lasso_ultimate_gaming.ini) on GitHub)
I've configured quite a few settings per process, but I'm starting to lose track of which settings I've already customized.
What would be the best workflow to manage and maintain these configurations efficiently?
Thanks in advance for any insights or ideas!
Xbox app games can be tricky since their executables are stored in protected WindowsApps folders. You might try enabling Process Lasso's Watchdog or use PowerShell scripts to detect running processes by name and then trigger profile changes automatically. That way, you can still manage Xbox titles dynamically. Would love to hear if anyone has tried a similar approach!
QuoteI suspect this is because those titles are actually stored or called in the CodeSelect\WindowsApps folder
That's correct, the executable can be in a different folder than where you chose to store the game. However, you should still be able to set a matching rule for these processes.
In some cases, anti-cheat systems or Windows process protection may prevent enforcement of certain rules. If there's a particular game it doesn't seem to work for, let me know the title so that we can test it and report back the underlying cause and limitations.
QuoteAlternatively, could I manually edit the configuration file to add something like this?
That INI is interesting because it has a completely invalid syntax. Is it an AI hallucination? Idk
Anyway, what you're describing is something we've been working on. I don't want to get into the details and don't have an ETA for you right now, but it's coming. Note that this work is *not* in today's pending release of Process Lasso (v16.1), which I state so that the config profile overhauls made there aren't mistaken for this separate work. Stay tuned!
UPDATE: See v17 beta for a "View All Rules" window that allows the user to view and edit all rules at once.
For the moment, you can copy/paste rules from one process to another (https://bitsum.com/product-update/process-lasso-v15-1-selective-rule-import-export-and-copy-paste/). It will copy a block of JSON to your clipboard.
You can also perform a JSON rule export with menu item "
FIle > Export Rules" then edit that JSON. See more info on modifying the JSON in this later reply (https://community.bitsum.com/forum/index.php?topic=38535.msg72436#msg72436). You can then use menu item "
File > Import Rules".
Thanks for the insights. I will be waiting for that promised update, if there is a beta I would be happy to join.
Quote from: Jeremy Collake on November 06, 2025, 05:25:34 AMIf there's a particular game it doesn't seem to work for, let me know the title so that we can test it and report back the underlying cause and limitations.
About that as for now every title works. But I would have to start up the title, apply my settings 'live' and restart. Is there a way to have something like, if started by client (steam, xbox, etc.) apply this setting?
I thought about copy-pasting, but I would have to have two games running at the same time, while do able it is very inconvenient for setting up games.
One last point. Pro Balance always restricts games, so I have to exclude them. Is this an expected behaviour?
Quote from: Jeremy Collake on November 06, 2025, 05:25:34 AMThat INI is interesting because it has a completely invalid syntax. Is it an AI hallucination? Idk
I just found that repo. Could be AI, didn't bother testing it before confirmation.
QuoteIs there a way to have something like, if started by client (steam, xbox, etc.) apply this setting?
There are some ways using Regular Expressions (https://bitsum.com/processlasso-docs/#processmatch) to match processes that are children of a specific process, but it gets a little convoluted and wouldn't be perfectly precise in determining what is a game. So, it isn't the simple solution you are looking for, and that we hope to offer in the future. For now, path matching would be the go-to, but as you allude, it will catch some extraneous (non-game) programs if you match solely to the WindowsApps folder.
Pending completion of larger projects, I've just created a ticket to add matching of rules based on game launchers. We'll try to get to this soon and I'll reply when there has been progress.
QuoteProBalance always restricts games, so I have to exclude them. Is this an expected behaviour?
In the default config it should only act on games when they are not in the foreground. When they return to the foreground, any action should be ended. Do you find it is acting on them during gameplay?
I previously mentioned use of menu item "File > Export Rules" and manipulation of the exported JSON to ease rule duplication. As an example, after exporting a rule on msedgewebview2.exe I get the following:
{
"$description": "Rulesets for Process Lasso",
"$schema": "https://bitsum.com/json-schemas/2025-02-12-00/schema",
"$title": "Process Lasso Rules",
"cpuAffinityRuleOrder": [
"msedgewebview2.exe"
],
"efficiencyModeRuleOrder": [
"msedgewebview2.exe"
],
"priorityClassRuleOrder": [
"msedgewebview2.exe"
],
"ruleSets": [
{
"cpuAffinity": "1-5",
"cpuAffinityDelay": 0,
"efficiencyMode": 0,
"priorityClass": "Above normal",
"priorityClassEnforcedByRegistry": false,
"processName": "msedgewebview2.exe"
}
]
}
To apply the same rules as msedgewebview2.exe to some other process, I'd simply duplicate that block. The rule order keys can be ignored and omitted, so don't worry about those. Example below, propagting the rules to notepad.exe:
{
"$description": "Rulesets for Process Lasso",
"$schema": "https://bitsum.com/json-schemas/2025-02-12-00/schema",
"$title": "Process Lasso Rules",
"ruleSets": [
{
"cpuAffinity": "1-5",
"cpuAffinityDelay": 0,
"efficiencyMode": 0,
"priorityClass": "Above normal",
"priorityClassEnforcedByRegistry": false,
"processName": "msedgewebview2.exe"
},
{
"cpuAffinity": "1-5",
"cpuAffinityDelay": 0,
"efficiencyMode": 0,
"priorityClass": "Above normal",
"priorityClassEnforcedByRegistry": false,
"processName": "notepad.exe"
}
]
}
I'd then use menu item "File > Import Rules" to import the resulting JSON.
Process Lasso v17 BETA, now available, adds a consolidated dialog where all rules can be viewed and edited at once. It is accessible at menu item "Options > View All Rules".
You can get on the beta channel by checking menu item "Updates > Include Betas" then using "Updates > Check Now". However, you will then receive frequent beta updates. To get back off the beta channel, uncheck "Updates > Include Betas" then run the release version installer.
Thank you for the information and the detailed help, I really appreciate the insights. I'm looking forward to a more game-focused Process Lasso, especially since it makes managing x3D processors so easy. Relying on Game Bar was such a pain. I am checking out the beta right now.
Process Lasso version 17 is now available in its final form with the new Edit Rules view (https://bitsum.com/product-update/process-lasso-v17-0-consolidated-rules-view/).