anything i haven't tried ?

[Slender]

same on battery / wifi mode?
do you connect external display?

[Unreazz]

Hi,

how did you fixed input lag ?

[joseph_from_pilsen]

I just specify more what i have written previously to explain more. I meant that all the issue is that playermodels often DONT move the way and the speed favouring the player as the interpolation and client prediction is moving them too fast and teleporting them back after a while making them hard to hit. In my case, after i switch from WiFiber to DSL, the player models are harder to hit as they tend to teleport away at the moment i fire at them, like normally only 70ms players do (i literally cant hit high pingers, they react too fast and flashy as they see me before i see them so they stop and kill me sooner and at more close or distant place than players with low ping and real time reactions. Also there is no chance to play deffensive moves as they never arrive to the lagger, they are protected by a huge ping barriere from any instant counter-reaction).

But with DSL connection which has only 7ms higher latency (that cant be the main reason, also jitter and loss are OK), the game is noticably less responsive in term of being (un)able to oneshot enemies without giving them time to counter-act or ending in desperate spray as my tracking is behind. They do too many flashy moves which some of them obviously dont come from their input but from bad client prediction and i need only one thing from the client - to delay them so they cant teleport away after they stand still a while. Just the opposite thing which is happening (first they tend to overpeek so i just aim at the spot they are moving to, knowing they cant dissipate the speed isntantly, but then they stop and teleport a bit back or forward or sideways, so i miss, baited to a shot which goes half meter off). And when the opponent is standing and i shoot his head, its usually arm or nothing, because they accelerate not from zero speed following some harmonic curve of acceleration, but they start moving like a kicked ball, instantly fast. Just more like 70ms players (when i track A they already do D and shoot and vice versa).

[krash]

-software changes: Yes *different process lasso configurations*
-peripheral changes: i only switch between 2 mice now n then ( op1 8k, ulx ) * i don't think the problem is from me changing those ? *
-external interference: i don't think so
-if it's due a cs2 patch i don't know since it's fine with my friend we usually comment after any update on how the game feels
-hw temperatures 60 - 70 C while playing
-testing w10 i never knew theres a verison that supports faceit ill check this one
testing 23h2
-will test the drivers
currently trying 551.23 possibly fixed ? giving this a week and ill talk more about it i guess
was deathmatching before and after changing drivers
-i'm going to be moving to a pc soon so i don't think id upgrade anything anymore
-yes i've upgraded my rams but the laptop doesn't even support xmp so timings are capped at the same thing ?
*i don't know if i faced the problem's after changing or not but i think i had normal clips even after upgrading*
-upgrading cables will be a lil too much if i upgrade mine i have to also work on the other cables in the house i might do it

You should avoid using ProcessLasso, it's function is redundant for most users (especially this use-case).
Yes, FaceIt forces newer versions of Windows for “security purposes”. Otherwise, everyone would be on W7 or earlier W10 versions such as 1703–1909.
Here are a few references which might be of interest to you:
https://github.com/valleyofdoom/PC-Tuning
https://github.com/BoringBoredom/PC-Optimization-Hub
https://calypto.us/
https://github.com/djdallmann/GamingPCSetup

Disabling IGPU and switching do dGPU only (if your laptop supports Advanced Optimus) would also be desirable, though they don't implement that on laptops often.
https://jarrods.tech/list-of-gaming-lap ... ux-switch/

Just in case, could you take a ZenTimings screenshot and post it here? RAM instabilities can severely impact your entire computing experience.
As the user above has mentioned, getting a external USB-based NIC might be beneficial as a test.
Realtek is the only vendor which makes USB network adapters, as far as I'm aware.
In particular:
RTL8159 — 10GbE
RTL8157 — 5GbE
RTL8156 / RTL8156B — 2.5GbE
RTL8153 / RTL8153B / RTL8153C / RTL8153D / RTL8153E — 1GbE

ASIX has a older 1GbE model, such as the AX88179_178A

Keep in mind, most people have not checked how any of these adapters perform in practice (DPC/ISR performance, networking performance, overall latency,...)
There's also the factor of server variance (how good the HW & SW setup is) + how good your ISP's routing to a specific server is, so it's somewhat difficult to evaluate this properly without trying out different hardware configurations.

b1.png (35.09 KiB) Viewed 2854 times

a1.png (35.12 KiB) Viewed 2854 times

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

[krash]

same on battery / wifi mode?
do you connect external display?

wifi disabled
i never used my laptop off charge unless i'm dismantling it
im using an external display as my main display zowie xl2546

here's the cru settings i'm using

image (1).png (58.51 KiB) Viewed 2850 times

[krash]

Hi,

how did you fixed input lag ?

Hello,

just 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

The main goal here is to reduce click delay both keyboard and mouse and reducing stutters.

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"

[krash]

I just specify more what i have written previously to explain more. I meant that all the issue is that playermodels often DONT move the way and the speed favouring the player as the interpolation and client prediction is moving them too fast and teleporting them back after a while making them hard to hit. In my case, after i switch from WiFiber to DSL, the player models are harder to hit as they tend to teleport away at the moment i fire at them, like normally only 70ms players do (i literally cant hit high pingers, they react too fast and flashy as they see me before i see them so they stop and kill me sooner and at more close or distant place than players with low ping and real time reactions. Also there is no chance to play deffensive moves as they never arrive to the lagger, they are protected by a huge ping barriere from any instant counter-reaction).

But with DSL connection which has only 7ms higher latency (that cant be the main reason, also jitter and loss are OK), the game is noticably less responsive in term of being (un)able to oneshot enemies without giving them time to counter-act or ending in desperate spray as my tracking is behind. They do too many flashy moves which some of them obviously dont come from their input but from bad client prediction and i need only one thing from the client - to delay them so they cant teleport away after they stand still a while. Just the opposite thing which is happening (first they tend to overpeek so i just aim at the spot they are moving to, knowing they cant dissipate the speed isntantly, but then they stop and teleport a bit back or forward or sideways, so i miss, baited to a shot which goes half meter off). And when the opponent is standing and i shoot his head, its usually arm or nothing, because they accelerate not from zero speed following some harmonic curve of acceleration, but they start moving like a kicked ball, instantly fast. Just more like 70ms players (when i track A they already do D and shoot and vice versa).

i have no comment on DSL or WiFiber

If you're misreading their peeks, it's usually just gamesense try their shoes

what gun are they holding?

-awp: peek tighter to the angle
-ak: expect a wide swing or crouch peek
-smg: maybe a jump or wide

are they desperate to kill me?

-they’ll probably wide swing

do they know I’m holding?

-might crouch peek or jiggle close

there’s a lot of tendencies in cs2 or any tac shooter, and they change as you rank up.

[joseph_from_pilsen]

Believe or not...
i reinstalled the shitty game this night with manual delete directx folder + cache... and issues are gone. Now just tuning visual look (for me seems good compromise between smoothness and input delay -noreflex, vsync FAST, gsync on, low latency mode -ultra (at 390hz). After reinstall it SOMEHOW synces correctly now at the slower DSL. Also the smoothness is day and night, i thought the 30ms frame spikes are "normal". Joined 2 DM and no single framespike all time, i was playing A HALF YEAR with frame spikes here and there.
Im very curious when the game fucks up itself again. The freezes started at the moment valve released some glorious patch in autumn + my previous connection suffered from microlags but not all the freezes were network sided, after fixing malfunctional network the other half of framespikes still persisted (the ones not being caused by red netgraph networking lags which came to existence the same days the connection got broken, in autumn 2024). From some weird reason, at DSL with lower bandwith the game was more desynced than at 1Gbps 60Ghz WiFiber.

Weird things - i reinstalled the PC (fresh install windows, no backup restore, all apps and drivers manually downloaded and installed) in march, didnt help at all, after installing the game was running with the same frame spikes and after trying to solve them with another internet connection, i only noticed that at DSL it does weird broken animations like everybody had 50+ms as a bonus. Also my gaming secondary laptop is running with frametime spikes since i bought it (even now actually). May try to reset the game at the book too whether it helps too lol.

[kyube]

b1.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

Thank you for posting.
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:

just 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"

Using a custom OS in general is detrimental to performance, not beneficial.
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.

[Bobo]

Go into the bios and max out the voltages for VCCIO and VCCSA. in my mobo they max out at 1.4 and 1.3.