engineer class, so retarded
Account Details | |
---|---|
SteamID64 | 76561198374045865 |
SteamID3 | [U:1:413780137] |
SteamID32 | STEAM_0:1:206890068 |
Country | Pirate |
Signed Up | March 20, 2020 |
Last Posted | February 23, 2024 at 9:48 PM |
Posts | 289 (0.2 per day) |
Game Settings | |
---|---|
In-game Sensitivity | 5.2 |
Windows Sensitivity | no |
Raw Input | yes |
DPI |
no |
Resolution |
1024 768 |
Refresh Rate |
120 |
Hardware Peripherals | |
---|---|
Mouse | no |
Keyboard | yes |
Mousepad | no |
Headphones | no |
Monitor | yes |
bearodactylis it possible to have tracers work with no viewmodels cuz saam says mastercoms removes tracers? have r_drawtracers_firstperson and r_drawtracers 1, normal viewmodel fov as well
try cl_particle_batch_mode 1 if you have it on 2
tip for anyone looking for old tf2 files in the future, you can use https://github.com/SteamRE/DepotDownloader with manifest IDs from https://steamdb.info/app/440/ to download files from any version of tf2 ever released on steam
AimIsADickbut it will also interfere with the ability for players to kick bad players
every time ive seen u in game ur going 2 and 40 on an uncledane pub …
enthrowsv_pure 2 still gives some issues with the flat textures. lod tweak does seem to improve certain weirdness on sunshine, but it does not help everywhere and I don't really see a common reason as to why some textures work great in sv_pure 2 and some textures have the weirdness. Does anyone know what specifically is causing this on some textures?
In pure servers, instead of using the custom 1x1 textures from cleantf2+, the game reverts back to using the original tf2 textures but keeps the 1x1 scaling of the custom ones for some reason, so it's basically the original texture scaled down and tiled a bunch of times.
It looks pretty flat for most textures, but if the original texture is less uniform or looks far different on one edge than another edge, it'll look weirder and not as smooth. There isn't really anything you can do about it. On sunshine specifically, some of the textures lack lower res mips so that could explain why they behave differently.
quintoshwhy are metal footsteps still included in this? players caught using them receive a 1 year ban
they're not, he removed the option and posted about it a while ago https://tf.gg/post/1033132
go in dev/lists/flat.txt and dev/lists/flat_hl2.txt and delete the lines with materials\glass, then re run the generate script
if you're using the premade vpk instead of generating yourself, unpack it and delete the glass folder inside materials
I suppose I should have indicated somehow that I was responding only to the first question and not the second.
I use dd for OS migration, I have never had a single problem with it. Even my heaviest used ssd only has some 200 TBW, so I don't care about writing a few extra GB for an easy, convenient, reliable imaging method that always will work exactly how I expect it to. Are there situations in which using dd could be less than ideal? Indeed there are.
I didn't mean to argue about it, everything you have said is more or less correct.
I mean, he just asked what people use. dd is what I've used many times to clone OS installs since I find the hassle-free and headache-free nature of a bit-for-bit copy to be absolutely worth wasting whatever .00001% of an ssd's life on cloning free space. You're completely right about drive sizes though, a filesystem level tool would be better and easier if the destination drive is smaller, although there is the option of resizing partitions and then copying just the partitions and table with dd instead of the full drive.
Have you considered changing the sens directly in tf2 via rcon instead of changing it system wide in libinput? You could easily make it crossplatform that way, and also keep m_rawinput on. The game client serves rcon if you launch with
-usercon +rcon_password "whatever" +ip 127.0.0.1 +net_start
You could use something like https://github.com/n0la/rcon or https://python-valve.readthedocs.io/en/latest/rcon.html in your script, or, if you deem those clients too bloated, cap a packet, look at how it changes when you send a different value in the sensitivity command, and just send the raw bytes with nc.
Forgive my ignorance: why would anyone ever want a sensitivity randomizer for anything other than destroying their aim?
bearodactylwheres my fenoblocker9000 (maybe AimIsADick too)
just put a big CRINGE WARNING and let me click thru if i want to
here https://greasyfork.org/en/scripts/427733-fenoblocker9000-aimisadick-too/code
maybe you fixed it by now but I remember a few months ago this plugin considered rocket jumping to be 'aimsnap detections' or something