I use Process lasso to exclude cs2 from foreground boosting can u tell me how to do that via registery ?kyube wrote: ↑18 Apr 2025, 09:10Thank you for posting.krash wrote: ↑17 Apr 2025, 19:25b1.pnga1.png
these r the old rams im kinda lazy to stick the new ones in again since it's fine now after using 23h2 & 551.23 & old rams
i don't think process lasso has an issue since i'm just lowering certain things priority and removing foreground boosting from cs2
and i think i'll pass on buying anything for the laptop atm
disabling iGPU isn't an option i've tried it and had to reset bios
It's great to see that your laptop doesn't apply any XMP, which can cause instabilities.
ProcessLasso's driver causes SW overhead, taking up CPU cycles unnecessarily.
You can do affinity changes without relying on ProcessLasso for that, resulting in gained performance.
However, what caught my attention is this:Using a custom OS in general is detrimental to performance, not beneficial.krash wrote: ↑17 Apr 2025, 19:42just test and revert avoid big regedit files or utility tweaks like exm if u want anything from them just open the .bat as a notepad and find it
avoid using XOS if you're running custom ISOs. my friend and I used to use XOS, but after trying other options, we realized how noticeably stuttery it was in comparison.
here are the versions we had issues with (and earlier ones too), just listing them here in case things get fixed in future updates.
XOS W11 - 012 - 23H2
XOS W11 - 012 - 24H2
ur never fixing "floaty mouse" just find a good ground you can get used to
i personally untick my "usb host controllers" in msi util and drag out or delete "xinput1_3.dll" from system32
i would be down to drop everything i kept on using but alot would ask for benchmarks and ignore if the game actually felt different
not everything that changes how ur game feels is better some turn out to make it worse but u just think "different = better"
You can easily make your own installation by following the resources I've linked in my previous post (PC-tuning has a .reg file which you run after installing a stock Windows ISO)
"Floaty mouse" is very fixable. It's not a casper ghost hunting journey. It's a matter of proper HW & SW optimisation practices, which have substantiated, verifiable & repeatable testing data to back the claims up.
Deleting that specific file you've mentioned has no basis & proven benefits. I assume you've come across some anecdote that it helps and you've placebo'd yourself that it does something.
Disabling MSI-mode on your USB controller results in worse DPC/ISR driver performance, it's recommended to avoid doing so.
It seems to me that your issue might be rooted in SW optimisations. That is, you're applying "tweaks" which cause performance loss and not performance benefits.
I'm using custom OS installs to skip some of the setup steps sure, I could do clean installs and manually tweak everything, but this method works just fine for me.
regarding the "floaty mouse" issue, that was just my personal experience. If others have managed to fix it, that's great to hear and would like to see a guide.
as for MSI mode, it behaved better for me when unticked, but I’ll test both on and off over a few sessions to think if i want the better benchmarks or behavior
removing that file just changed the mouse behavior in a way I personally preferred nothing more.
and there's not much u can do HW wise to this laptop everything bricks when u change bios
the stuff i apply aren't usually aimed towards performance or changing much it's usually really generic stuff
MouseSmoothingX&Y changes
M&K DataQueueSize
PreRenderedFrames
and anything that's just fine to change