https://i.imgur.com/lr2amPF.png

https://i.imgur.com/lp41tgD.png

in battle royales this scenario is probably common (being "3rd partied" is what they call it?) and afaik in 99% of scenarios the team/person sandwiched from behind is focused because those are free kills and then favour the newest opponent because the survivors of the initial 1v1 have to invest time and resources into healing back up

If you're fishing for the argument "The player who sees you has a higher chance of preparing to win the second 1v1" then I feel that's quite niche unless you look at gamemodes where time to kill is extremely low like ffa cs:go gamemodes or CoD so there's more variance with odds of a clutch flick headshot. And even there you're still favoured to win so I'd say it doesn't matter much

In TF2 I doubt it matters. I'd wait like a second so maybe they shoot each other investing more hp and ammo into the 1v1, then get an easy kill on whoever survives.
Or just shoot the guy in the back, then wm1 at the dude who saw you but has low ammo and hp now so you're still highly favoured. There's always the chance of someone magically clutching a 1v2, yes. But believe in yourself. Just don't miss 3 meatshots on the person not looking at you

need to use dx9. dx8 doesn't support it as phloglover said

using this video you can find out how to turn it off if you don't want to to switch to dxlevel 95

https://www.youtube.com/watch?v=rsWPW817xWY

• go to hudlayout.res
  
• find the section with the transparency thing
  
• turn visible 1 and enabled 1 to visible 0 and enabled 0

Keep them in French if it's more comfortable for you. They can always be translated afterwards. Plenty of people willing to help you out with that

https://clips.twitch.tv/PolishedPlumpIguanaPeanutButterJellyTime

cu@

https://www.youtube.com/watch?v=wPH6On2F0Pw

just gonna add some info here in the meantime:

• Still no crashes on my end. About 6-7 hours of playtime since I removed the .sound.cache files. Idk if that's helpful. Maybe the crash will occur very rarely on my PC and it's gonna happen again eventually
  
• someone else tried removing .sound.cache files and they still have crashes
  
• mastercomms doesn't appear to be the issue. that other person uses mostly default settings without mastercomms
  
• Could be linked to certain map textures? The one time I crashed was on gullywash. Other person also crashed last night on gullywash. I didn't think about asking them at the time so maybe they crash on other maps too. I doubt it's this, but maybe other people can confirm/deny

had it once 2 days ago
removed all "vpk.sound.cache" files in Custom
haven't gotten it since
this came from some random steam forum post

Can't be 100% sure if this is the correct fix. The crash only happened to me once and 2 days isn't a long time to say with full certainty the crashes are gone

I have no clue why a sound cache file would have any effect on a texture quality crash. However there is no harm in trying it. All custom vpk.sound.cache files rebuild themselves by launching the game so you get all the deleted ones back

He already said in the followup video to it (which he also deleted) that he was going to delete them because he doesn't want his channel to be a platform for that type of content. Just respect that wish.

There's been like 2 threads about the subjects in the video and followup threads like this one asking for a reupload. All the content is available in text form if you want to find it for whatever reason. But him deleting that video is his decision and if you don't respect that then you don't deserve to have access to it in the first place

https://clips.twitch.tv/GiftedAthleticConsoleJebaited
https://clips.twitch.tv/ArtisticDifficultOwlCclamChamp

https://clips.twitch.tv/SparklyBetterChickpeaHeyGirl

https://clips.twitch.tv/ThirstyTemperedRaisinBatChest

zet em op kaptain

zet em op marten