Seems as though the july 25th update broke playback of most or all demos recorded prior to it, so far the workarounds are to use an earlier version of the game or to use the pre_07_25_23_demos branch which can be selected under the betas tab in game properties
Account Details | |
---|---|
SteamID64 | 76561198374045865 |
SteamID3 | [U:1:413780137] |
SteamID32 | STEAM_0:1:206890068 |
Country | Pirate |
Signed Up | March 20, 2020 |
Last Posted | April 28, 2024 at 8:10 PM |
Posts | 302 (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 |
TwiggyVac conflict = vac ban or inability to join vac servers ?
whichever it is, it's likely a drawback specific to that windows re-distribution he mentioned, as the spectre and meltdown mitigations can be disabled just fine (eg. using inspectre or manually changing the settings yourself) without any relation to or impact on VAC.
you can check which gpu tf2 is using with mat_info in console
Chances are you're using Optimus/MSHybrid which means the internal display is connected to the Vega iGP, games are running on the NVIDIA gpu, and each frame has to be copied from one gpu to the other in order to be displayed (incurring some potentially significant overhead).
If your laptop has a 'mux switch', you can connect the internal display directly to the 1660 Ti and alleviate this. If not, you could try using an external monitor if you have one, as the display outs on most dual gpu laptops are connected to the discrete gpu (this can be verified in NVIDIA Control Panel). If neither of those things are an option, it could be worth a shot to try running tf2 on the AMD iGP instead of NVIDIA, as it may actually run better that way due to no copy overhead.
Of course your cpu is on the weaker side like doiku said, so make sure nothing's using much cpu time apart from tf2, verify it's not being thermal throttled into the ground, and if HP provides any settings relating to cTDP or other power limits, set them to the highest available.
Shipping a 3 year old chromium framework version (85.0.4183.121) in current 2023 steam
Finally got around to getting these uploaded, google disabled my account for automated behavior part way through so mega it is
imgur images from posts (hopefully some 99% of them or so, impractical to get literally everything)
gallery imgur images from the galleries section
I downloaded all the imgur images linked on tftv, surprisingly it's only about 40gb of images, any recommendations for where to upload?
https://docs.mastercomfig.com/latest/next_steps/quick_fixes/#i-want-another-interp-value, however the mastercoms defaults are better anyways, 0.033 literally originated from a typo.
Should be in the same location as the weapon scripts, scripts folder in tf2_misc.vpk. You can extract with gcfscape
Sorry I should've looked at the game files before posting, it's actually volume and soundlevel under the Weapon_Scatter_Gun sections in scripts/game_sounds_weapons.txt, same file as the rocket launcher replacement
The rocket launcher sound replacement method won't allow you to use custom sounds in pure, although you can probably lower the volume of the default sound by changing "volume" or "soundlevel" in the scattergun weapon script.
If you're using weapon scripts for custom crosshairs already, you can edit it right in there, otherwise the script can be extracted from tf2_misc_dir.vpk (it's in the scripts folder and called tf_weapon_scattergun.ctx) then decrypted with CtxConverter/vice. At that point, you can edit it like a text file (change volume or soundlevel) and then put it in tf/custom/whatever/scripts/tf_weapon_scattergun.txt and it'll override the built in one.
man stop shittin up the benchmarks thread
i7-10875h, 3070 mobile max-q
crappy ddr4-3200 (tightened it from 22-22-22-52 to 17-18-18-38)
dxlevel 81, headsfeet, mastercoms low
2560x1440:
4812 frames 11.915 seconds 403.87 fps ( 2.48 ms/f) 48.195 fps variability
640x480:
4812 frames 11.112 seconds 433.05 fps ( 2.31 ms/f) 52.386 fps variability
seems okay for an old 14nm++++ laptop