This is what I was about to say, not the first time I heard from a public figure who posts on youtube that it doesn't really matter how many positive comments you get, the negative ones get to you and stay with you more.

I also understand as a non-public figure how this is harder to understand or believe but it seems true.

One of the possible explanations to this bias, that I heard, is that this trait stayed with us from the prehistoric days when we as humans had to remember what hurt us so that we avoid it in the future.

Free-wolf x2 wireless with g-skates (it's a g-pro wireless clone)

I bought it since it was really cheap on banggood (it's available on other more obscure websites as well, not trying to advertise the website too much) and I have been using it for 3 weeks now and I actually have no real issues with it

even though they lied about it's specs on the website lol - the dimensions are actually those of the g-pro wireless, on the website is advertised as the longest mouse ever at 139mm but in reality it's 124-125mm and the weight is actually 79g and not 69

but all in all it was worth the 25$ for an okay day-to-day wireless mouse (I wouldn't necessarily vouch for it in gaming)

I also have a g305 and the Free-wolf actually feels more balanced since it's rechargeable (the g305 feels too back heavy even with a AAA battery)

I have also used the XM1 and MM711 for a while - XM1 is one of the top wired mice for claw grip, really solid build all around and the MM711 is okay overall, however the primary buttons drove me crazy with their wobble, I even tried the fix for it and they were still annoying to me

0.0303 is actually the most recommended interp value for hitscan (there was a misunderstanding way back when interp values first started be thrown around) and 0.0152 for projectiles.

0.0303 is what you get with cl_interp_ratio 2 and cl_interp 0, same for projectiles but with cl_interp_ratio 1).

Not sure what causes the reverse of interps but an easy fix, I would think, is to put the desired interp values in each individual class cfgs.

I tested now to see if it's a driver related issue and (for me at least) it is

I used Display Driver Uninstaller and retried with the latest driver (issue still persisted) then I tried with the June one and still the same thing, however the May one (446.14) fixed the issue.

PS: I also tried Jacky's suggestion and it didn't work for me.

1) you should delete only the other comfig vpk (not the additional vpks you downloaded from the site like no footstepts for example) before trying a new one
2) interp settings are included in the comfig vpk so you don't really need a separate cfg for that

PS: props for how you wrote and spaced out your text :D

If you like the shape and size of the g305 I suggest buying that one, since it's lighter (especially if you use AAA batteries with some tin foil or adapter) and lighter for most people playing FPSes means more control

I currently own, but stopped using, the g603 because I don't like the shape of it (it made my wrist hurt pretty badly after a couple of days of using it, I use a palm claw grip and have decently large hands)

Also the g305 is a bit cheaper, and sensor performance wise I don't think they are distinguishable.

PS: I haven't owned the g305 but a friend of mine does and I haven't heard any complaints from him in the past two months or so that he used it.

Also, I suggest this guide as well if you want to go down the rabbit hole of choosing the perfect mice for you :D

https://www.rocketjumpninja.com/mouse-search

I believe it might be caused by mat_mipmaptextures being set on 0, try setting it on 1 and see if it works.

You can change the damage color from the advanced option from in-game settings.

Rekuso's name was at some point "CVS pharmacy" probably from an inside joke that I don't know either.

I remember having this error before using mastercomfig, don't remember exactly how I fixed it, however I am pretty sure it was caused by a community server's custom sounds.

Maybe try this - https://forums.alliedmods.net/showthread.php?t=299049

-dxlevel 91 -full -w 1920 -h 1080 -freq 144 -console -novid -nojoy -nosteamcontroller -nohltv -particles 1 -nostartupsound

I don't really know what to suggest further, maybe try resetting your game to default (https://docs.mastercomfig.com/en/stable/setup/clean_up/) or roll back GPU drivers or even try to restore to a previous version of windows.

-dxlevel 91 -novid -full -w 1920 -h 1080 -console -nojoy -noff -nohltv -nouserclip -softparticlesdefaultoff -reuse -usetcp -nostartupsound -primarysound -snoforceformat -nosteamcontroller -disable_d3d9_hacks -NoQueuedPacketThread +cl_clean_texture

Out of that list, I think I had -nouserclip -softparticlesdefaultoff, if you determine that the issue is not from the headsfeet vpk I would try and remove "disable_d3d9_hacks" and "cl_clean_texture" (besides the 2 I mentioned at the beginning of the sentence) since I don't see how the other ones would cause this.

I also had this issue, for me it was from some more uncommon launch options, I would try removing those first.

yes, I was referring to steam launch options, very weird if you don't have any and you have this issue

https://www.teamfortress.tv/52951/weapon-specific-vtf-crosshair-switcher-thing

I recommend using this, it's easier:

1. You create a folder in custom called "crosshairs"
2. You start the app and you click on file->generate config and you select the "crosshairs" folder
3. You can select now what crosshair you want for whatever weapon

PS: Got to be out of the game in order to change crosshairs and you have to have the first crosshair option (crosshair "none") selected in the in-game options.