NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by admiralspeedy, January 21, 2016, 10:14:38 PM
Quote from: admiralspeedy on January 21, 2016, 10:14:38 PMI love Process Lasso because it lets me set change my power profile automatically when I play games. I have paths setup for all of major game folders (Steam, Origin, Uplay, etc) and it works great except for two problems.The first problem is with the config. I keep a backup of it because randomly I'll open PL to check things out and notice that my settings aren't right and then I check an all of my application power profiles are gone. I think this happens when the program updates and it means I have to import my config a lot.The second issue is with the blacklisted process names. I noticed that no matter what, my application power profile setting would not work for Assassin's Creed Syndicate (ACS.exe) and doing further testing, it doesn't work for any process named ACS. I did some Googling and found out that you guys added ACS.exe to the list of tamper-proof processes way back some time in version 7. I understand that this was done because some antivirus had this name and caused issues. Can you please expose this list and let us allow processes that have been blacklisted? I don't use that anti virus and it simply hinders me for no reason.
Quote from: edkiefer on January 21, 2016, 10:33:11 PMI'll have to check on the ACS.exe but one thing you should do is make sure you only use one type of trigger for a power plan.Meaning if its a game, just use game mode and set power plan there, don't have any app that are games to be in the "configure application power plan" option of PL.Only use one or other .
Quote from: Jeremy Collake on January 21, 2016, 10:36:10 PMWow, these are some odd reports, and I'm very sorry for your experience.Let us clean them up for you, then all will be right in the world! We appreciate your patience with this.First, we need to identify what is going on. So, your actual INI file settings seem changed every once and a while? Is that correct? Changed to default (essentially empty), or something else? Or is just a power plan change you are seeing?As you researched/know, most games have fairly sophisticated self-protection mechanisms that resulted in me deciding it's best for Process Lasso to just ignore them. After all, the focus of ProBalance is on keeping everything *else* in check.I will at least publish a beta early next week that removes this game from the tamper-proof list, as an immediate action, and make another attempt to get rid of that list in it's entirety by identifying and complying with the restrictions of every app on that list, a labor intensive process, but one well worth it. Only issue is we then have to track updates to those apps. Maybe the community can help with that.
Quote from: admiralspeedy on January 21, 2016, 10:55:16 PMI'm incredibly impressed at how fast you replied.I don't really like the game mode system so I don't use it. The way I have it set up is with wildcards in the normal "Configure application power profiles" setting.An example being "d:\program files\steam\steamapps\*\*.exe" which changes the power profile to High Performance whenever an execetuble launches from steamapps, which is always a game. I have this set up for my Origin folder and Uplay folder as well as a few standalone games. It however is not the issue with ACS.exe, as confirmed by the other poster in this thread and it works fine for ever other game I own.
QuoteYes, the INI file reverts to default. Probably half a dozen times now I've opened up PL to add a game folder to the power profile list and all of my settings will be back to default and all the power profile rules I have set are just totally gone. I started keeping a backup of the INI and just import it whenever this happens now. It actually happened yesterday and I believe it happened right after I updated the program.
Quote from: Jeremy Collake on January 22, 2016, 10:59:35 AMI use junction points a lot myself, and you're right, they shouldn't matter.However, something is making a difference. The update process should never kill the configuration. I need to spend some time thinking about this, then we may need to send a debug build so we can capture a debug trace/log about why it's doing what it is doing.Do you have this in a state where you can reproduce it at-will by chance? Is it seen every update? This is definitely a new one to us, I've never heard a similar report.
Quote from: Jeremy Collake on January 23, 2016, 10:26:07 AMBTW, as for ACS, are you aware of the menu option 'Options / General / Ignore problematic processes'? If you uncheck that, it should have unfettered access to that process.