Started by SHJordan, August 31, 2011, 01:57:32 AM
Quote from: gtweak on August 31, 2011, 09:13:16 AMWhat do you mean? Lags? If so, try excluding game processes from ProBalance restraint by right-clicking process on the list and selecting Exclude from ProBalance restraint. Additionally, you can add their processes to Gaming mode introduction list by right-clicking process and choosing Enter Gaming mode when running.
Quote from: gtweak on August 31, 2011, 10:13:04 AMExcluding from ProBalance restraint will prevent Process Lasso from changing process' priority, Gaming mode introduces some core engine tweaks not to disturb game processes.
Quote from: gtweak on August 31, 2011, 10:18:52 AMYes, taking these two tweaks should (not necessarily) make games work more smoothly. I can said as Worms Armageddon fan.
Quote from: gtweak on August 31, 2011, 10:29:55 AMIt's optimized anyway! Just look how small (even tiny) amount of memory it uses with so big functionality. Mentioning "not necessarily" I wanted to give no guarantee.
Quote from: bitsum.support on August 31, 2011, 01:16:59 PMThere is an option 'Automatically enter gaming mode'. Set this for your games, then you do not need to also exclude them from ProBalance restraint, though doing so won't hurt anything either. The 'Configure game processes' option is just that. It tells Process Lasso what processes are games. That is all you need to do .Often people ask what configuration changes they should make to further improve their systems. My best recommendation is usually not to make any. I mean, you *do* want to identify your games as 'games' by setting them to automatically enter gaming mode, but you don't want to go around tweaking a bunch of other settings. Why? Because the process of tuning a system is so complex that you're more likely to do more harm than good. It is best to rely on Process Lasso's default settings, which have been tuned over many years of real-world use.One thing I would like to warn against is 'Foreground boosting', a feature Process Lasso does offer, with warnings attached. It is disabled by default for this reason. Some games can have big problems when this sort of boosting is used. Further, it does not help things at all. Windows already boosts the effective priority of the foreground process, and further boosting is usually detrimental. Sadly, most of the cheap '[some application]' type apps you see spun out from the 'cheap software factories' do just this - raise the priority of games and then lie to consumers, saying that somehow gives them more 'horsepower'. In fact, that is not at all how CPUs work, and not at all the purpose of priorities. A High priority process runs no 'faster' than a Low priority process. The priorities simply help the scheduler decide what should get the CPU when two or more processes (actually threads) need it. By selectively lowering background process priorities, you can boost responsiveness and prevent things from 'getting in the way'. Our demo proves how well this works. However, this must be done carefully, and our ProBalance algorithm is the result of many years of tuning .Hope this helps some. If you have additional questions, please ask.