Afaik this is the reason b15b is used instead.

Also console should be spamming info about which textures might be missing, since they're not packed within the .bsp map file.

Check out scripts/game_sounds_vo.txt[/url] in tf2_misc_dir.vpk and search for Announcer or Comp, there should be loads of references to the audio files (additionally tf_sound_vo_english_dir.vpk and then sound/vo/compmode to listen to the actual .mp3 files).

Thing is that even with the sound files there, the server needs to trigger them for various events, if those triggers don't happen there's no sounds being played.

For reference:

cl_allowdownload 1
cl_downloadfilter mapsonly

Tried the huds.tf hitsound section?

Or just Google and one of the many results with more than 1 sound in the download:
GameBanana - Quake hit indicators
Overview of Quake Sound Files
Quake 4 Weapons Rip which contains hitsounds

Also found this mdv tftv post linking to a hitsound.zip on igmdb.org, but that seems to be dead, but lists a 'hitsoundQ4.wav someone might probably still have.

The capture point holos you saw on stream can also be used.

https://cdn.discordapp.com/attachments/630194734584954880/736743918955135067/unknown.png

Get a good hud that shows all players, medigun charges.

Then get CastingEssentials and launch TF2 with -insecure, this way you can make sure you don't get invisible player models anymore, outlines for projectiles, allow the charge bars of weapons to show up, separated medigun bars if hud supports it (or customize this), display status icons, force killstreak counts etc. Loads more features offered by the plugin, can be found by checking out the plugin wiki or typing cvarlist ce_ in console (or find instead of cvarlist).

For the actual observing: do not swap too quickly between players and jump across the map. Go for interesting perspectives, set up static camera angles using the ce_autocameras module per map if you're really keen for third person perspectives of pushes (pair that with bind key "ce_autocamera_spec_player free" to automatically go to an angle with a line of sight to the player were spectating).

Disable the Aero snapping there if not already disabled.

Optionally use Microsoft Powertoys' Fancyzones to still manage windows by being able to put them in dedicated areas, or Winsplit Revolution.

that video shows that it's most likely not the PSU, because then the entire system would most likely power off instead, which might still be the case if you actually start gaming, in that case it will be the PSU failing you if you don't have any others to test with at the moment.

Tried the PC in a different part of the house, so you can confirm it's not the current circuit being iffy.

Booted with the minimal amount of hardware actually plugged in? (disconnect all fans except CPU, no HDDs or DVD drives or RGB strips.

No weird overclocks?

Tried a different display cable from GPU to monitor yet? Different combination of ports on either monitor and graphics card?

What happens if you boot to safe mode? Tried a full clean driver install yet? DDU + NVCleanstall

Changed nickname from FLYING to flying

If it's just the chat and/or activity feed you need from the dashboard, you can add those popouts to your OBS window as custom docks (chat supports BTTV and/or FFZ there)

Will recommend against using SLOBS, but if you want to test, you can import scenes/settings between both versions.

---
Additionally, there's GPU acceleration you can enable/disable in Chrome somewhere, if not Firefox, see if that changes anything, if using the twitch dashboard popout as OBS docks doesn't get the job done instead.

That should already be the version used:

---
Does the framerate get impacted the same/less/more if you run TF2 in -window -borderless instead of -full?

That's most likely a hud issue BigPapi, remove resource\ui\TextWindow(CustomServer).res and see if it fixes the issue.

Which browser are you using?

Disabled the Stream Preview video player in the dashboard? (Click the pencil right of Stream Manager to edit panels)

Do not do this, since the equivalent would be doing cl_fullupdate or record random;stop every tick, which could cause a lot of clientside lag/stuttering.

The CE command fix for the view heights is the only way to make POV in STV match or be fairly close to actual POV from the player on server/their demo.

You're not taking away the best news from this post:

and as YeeHaw pointed out: