Recommended Posts

Bout time trading is on its way. Wonder what the new game mode is, also, Robin joked about Facestabs being something the new knife CAN'T do, I wonder if they finally fixed true facestabs (that is, where you can run backwards facing a spy, the spy can run forwards facing your face, and get a backstab on you).

As nice as it will be to finally have trading (and the polycount items), its probably a few months away given that they just now teased us with that info.

Bout time trading is on its way. Wonder what the new game mode is, also, Robin joked about Facestabs being something the new knife CAN'T do, I wonder if they finally fixed true facestabs (that is, where you can run backwards facing a spy, the spy can run forwards facing your face, and get a backstab on you).

As nice as it will be to finally have trading (and the polycount items), its probably a few months away given that they just now teased us with that info.

Doubtful as they've actually fixed facestabs before, but because all the crappy Spies couldn't get their cheap (Run at you swinging the knife as if they were a W+M1 derp Pyro) kills they whined about it being "liek da w0rts nerf evar" and Valve either rolled the changes back or made more changes that made the problem worse than before.

--

I do wonder how Valve will implement trading though; I can see a whole new facet to the community being born if it was done in-game (Trading servers/maps anyone?), but an out of game system would be awesome if opened up with a WebAPI. (Although it would be nice if they finished the ones they've already released too)

Doubtful as they've actually fixed facestabs before, but because all the crappy Spies couldn't get their cheap (Run at you swinging the knife as if they were a W+M1 derp Pyro) kills they whined about it being "liek da w0rts nerf evar" and Valve either rolled the changes back or made more changes that made the problem worse than before.

Valve has never fixed facestabs, they fixed facestabs caused by lag compensation, facestabs caused by buggy hitboxes have always been there. Unfortunately, to fix the facestabs caused by lag compensation, they had to reduce the backstab angle down to around where the BackBurner gets its crits at (which is only fair IMHO, as the backburner should have the same exact angle of effectiveness as the knife as they both target the back).

Spies complained because they could no longer sidestab and what not due to the fix, so Valve reverted it.

Facestabs due to a spy running straight at a person while that person is facing them, has never been fixed, so hopefully they found a way.

Valve has never fixed facestabs, they fixed facestabs caused by lag compensation, facestabs caused by buggy hitboxes have always been there. Unfortunately, to fix the facestabs caused by lag compensation, they had to reduce the backstab angle down to around where the BackBurner gets its crits at (which is only fair IMHO, as the backburner should have the same exact angle of effectiveness as the knife as they both target the back).

Spies complained because they could no longer sidestab and what not due to the fix, so Valve reverted it.

Facestabs due to a spy running straight at a person while that person is facing them, has never been fixed, so hopefully they found a way.

Facestabs have always really been an issue of lag compensation, it's ultimately the same issue as getting hit still after running behind a corner. Just the problem is more pronounced as the knife is a insta-kill.

There is always going to be fringe cases where facestabs will happen due to lag compensation, there's not much that can really be done to change that. The problem is as you mentioned though, the "back" angle. The Spy is an already powerful class if played properly, he doesn't need a 359 (Silly, but sometimes it feels like it) degree "back"stab angle.

Personally I think the original "fix" was fine, the knife is supposed to grant an instant kill for getting a BACKstab. Back does not equal side. The crappy Spies that whined about it should either play another class or learn how to use the Revolver.

</rant>

Facestabs have always really been an issue of lag compensation, it's ultimately the same issue as getting hit still after running behind a corner. Just the problem is more pronounced as the knife is a insta-kill.

There is always going to be fringe cases where facestabs will happen due to lag compensation, there's not much that can really be done to change that. The problem is as you mentioned though, the "back" angle. The Spy is an already powerful class if played properly, he doesn't need a 359 (Silly, but sometimes it feels like it) degree "back"stab angle.

Personally I think the original "fix" was fine, the knife is supposed to grant an instant kill for getting a BACKstab. Back does not equal side. The crappy Spies that whined about it should either play another class or learn how to use the Revolver.

</rant>

I do not think the legit facestab issues are due to lag compensation, you can run backwards with a spy running towards you, both facing each other, and he can still get a backstab, with your back NEVER facing the spy. Lag compensation facestabs happen when you turn quickly and the backstab gets lag compensated because the spy backstabbed you before you turned, but on your screen you were already turned (which is the same as getting shot around corners).

I do not think the legit facestab issues are due to lag compensation, you can run backwards with a spy running towards you, both facing each other, and he can still get a backstab, with your back NEVER facing the spy. Lag compensation facestabs happen when you turn quickly and the backstab gets lag compensated because the spy backstabbed you before you turned, but on your screen you were already turned (which is the same as getting shot around corners).

Both are actually lag compensation related, the "W+M1 Spy" example is caused by said Spy being lag compensated through you. While it appears he stabbed you in the face, he actually "phased" through your hitbox and hit the back/rear.

If the actual hitboxes themselves were "buggy" so to speak, then I imagine you'd be able to reproduce the circumstances while stationary.

Both are actually lag compensation related, the "W+M1 Spy" example is caused by said Spy being lag compensated through you. While it appears he stabbed you in the face, he actually "phased" through your hitbox and hit the back/rear.

If the actual hitboxes themselves were "buggy" so to speak, then I imagine you'd be able to reproduce the circumstances while stationary.

You are misunderstanding how lag compensation works. All lag compensation does is rewind the action in the game to match up the time the player clicked their mouse with where everyone was at that time. If the server "rewinds" the game to check if the lag compensated player hit the enemy, both models are moved back to where they were at the time.

For what you said to be true, the spy would have to temporarily move behind the player that is running backwards for him to "phase" through the enemy. Lag compensation rewinds the state of the game to see what the attacker was seeing. That means if the spy was seeing the enemies face, then the server is now seeing that you are seeing the enemies face (which by all logic makes it impossible to get a backstab). The problem is the server for whatever reason has a bug that sometimes causes it to ignore this, or to think that the victim is facing away from the spy (instead of towards the spy, like BOTH players saw). It may have to do with lag compensation, but it is an entirely different issue than facestabs where the SPY sees the enemies back but the enemy sees the spy as well.

The normal facestabs are like if a sniper shoots you "after" you run behind a wall which are caused by basic lag compensation. The rare and bad facestabs would be like if a sniper shoots your foot and it counts as a headshot which could be caused by lag compensation, but wouldn't happen under normal circumstances without the underlying bug.

Doesn't help a ton to explain why true facestabs are (while rare) apparently difficult to fix. Though it does help to explain why lagstabs (that is, you saw the spy on YOUR screen, but he saw your back on HIS screen) happen.

You are misunderstanding how lag compensation works. All lag compensation does is rewind the action in the game to match up the time the player clicked their mouse with where everyone was at that time. If the server "rewinds" the game to check if the lag compensated player hit the enemy, both models are moved back to where they were at the time.

For what you said to be true, the spy would have to temporarily move behind the player that is running backwards for him to "phase" through the enemy. Lag compensation rewinds the state of the game to see what the attacker was seeing. That means if the spy was seeing the enemies face, then the server is now seeing that you are seeing the enemies face (which by all logic makes it impossible to get a backstab). The problem is the server for whatever reason has a bug that sometimes causes it to ignore this, or to think that the victim is facing away from the spy (instead of towards the spy, like BOTH players saw). It may have to do with lag compensation, but it is an entirely different issue than facestabs where the SPY sees the enemies back but the enemy sees the spy as well.

The normal facestabs are like if a sniper shoots you "after" you run behind a wall which are caused by basic lag compensation. The rare and bad facestabs would be like if a sniper shoots your foot and it counts as a headshot which could be caused by lag compensation, but wouldn't happen under normal circumstances without the underlying bug.

No, I don't think I am. I think you're actually taking an oversimplified view of the situation, based more on reasoning between a single client/server relationship; Do not forget that interpolation will also be a factor.

I simply do not see any other sensible explanation for the cause of facestabs considering how easily they are reproduced, nor does it make sense to me personally that hitboxes themselves are somehow "bugged". The whole matter seems totally illogical, which is the hallmark of these sorts of interpolation/lag compensation issues.

I guess we'll just have to agree to disagree.

Facestabs are not caused by lag compensation. From what I understand it's caused by hitting the 'back' of the hitbox from the front. Since the hitbox is not the same as the player model. You can't move 'though' the player model but you can move 'through' the hitbox, so if you stab in exactly the right place your arm is going to go though the front of the hitbox and a hit is going to be registered on the back of the hitbox registering a kill.

Ultimate TF2 Rage.

It is very NSFW but sooooo funny.

"I ****ing play Heavy! I demand at least one to two medics on me at all****ing times!" ChoZo

In this video, a player records the audio of his teammate, ChoZo, having a total rage meltdown while playing as the team's only Heavy, with a helpful F-bomb count added to the bottom of the screen.

Highlights:

* "BONESAW IS READY."

* "I'm like ****ing Emperor Palpatine. UNLIMITED POWER!"

* "This isn't strawberry. It's RAWBERRY!"

* One minute in, when he's whining about losing, a teammate starts playing sad violin music.

* "I know kung fu."

* "ULTIMATE NERD RAGE!"

* "dut dut dut dut dut dut that's the sound of my ****ing gun!"

* "Nice job, ChoZo." / "Nice job? More like GREAT ****ING JOB."

Edited by GreyWolf
Changed embedded media to link - watch NSFW in stills!

Ultimate TF2 Rage.

It is very NSFW but sooooo funny.

"I ****ing play Heavy! I demand at least one to two medics on me at all****ing times!" ChoZo

In this video, a player records the audio of his teammate, ChoZo, having a total rage meltdown while playing as the team's only Heavy, with a helpful F-bomb count added to the bottom of the screen.

Highlights:

* "BONESAW IS READY."

* "I'm like ****ing Emperor Palpatine. UNLIMITED POWER!"

* "This isn't strawberry. It's RAWBERRY!"

* One minute in, when he's whining about losing, a teammate starts playing sad violin music.

* "I know kung fu."

* "ULTIMATE NERD RAGE!"

* "dut dut dut dut dut dut that's the sound of my ****ing gun!"

* "Nice job, ChoZo." / "Nice job? More like GREAT ****ING JOB."

At 1:10 Recruit's violin music haha.

This topic is now closed to further replies.
  • Posts

    • Bose Ultra Open Earbuds are once again selling at their lowest price by Fiza Ali Amazon is once again offering the Bose Ultra Open Earbuds at their lowest price ever with a limited-time 33 percent discount on their original MSRP, ahead of Father's Day. So, you may want to check it out if you are looking for a gift or if you have been wanting to upgrade your device. The earbuds feature an open-ear design and Bose's OpenAudio technology that should deliver high-quality sound while helping keep audio private. The earbuds also support Bose Immersive Audio, which creates a spatialised listening experience designed to place sound around the listener for a more engaging experience. In terms of wireless connectivity, the earbuds features Bluetooth, Bluetooth Low Energy (BLE), A2DP audio streaming, HFP, AAC, and SBC support. Furthermore, they are compatible with Bose SimpleSync technology, allowing pairing with compatible Bose smart soundbars and speakers. They are also compatible with the Bose App for setup, customisation, and software updates. Moreover, they offer an IPX4 water-resistance rating that should provide protection against sweat and light splashes. When it comes to the battery performance, the Bose Ultra Open Earbuds should provide up to seven hours of battery life on a single charge while a full recharge should take approximately one hour. Specifications Detail Fit type Open-ear Noise cancelling No Microphone Built-in Wireless Bluetooth (A2DP, HFP, AAC, SBC, BLE) Multipoint Yes; 2 devices simultaneously Charging interface USB-C Earbud size 0.73"x0.67" x 1.07" (0.014lb) Case size 1.65"x2.56" x 1.04" (0.097 lb) Materials PC-ABS plastic, metal, silicone, gold plating App support Bose app; adjustable EQ, SimpleSync Audio tech OpenAudio, immersive/spatialized sound Bose Ultra Open Earbuds: $199 (Amazon US) - 33% off Good to know This Amazon deal is U.S. specific, and not available in other regions unless specified. We only use first-party seller links (at the time of article publishing); ensure that you purchase from a first-party seller link only. Check out Today's Deals on Amazon | or our recent tech deals. Become a Prime member (for Students or SNAP) via Neowin Get Prime Access - Prime for half price (for qualifying Medicaid, EBT, SNAP) Subscribe to Prime Video, Audible Plus, Music Unlimited or Kindle Unlimited via Neowin As an Amazon Associate, we earn from qualifying purchases.
    • After enabling it in about:config, customize, density, compact; the toolbar/address bar gets smaller vertically. I enabled Nova, I notice the tab bar/title bar is a bit larger vertically now? Everything always becomes a waste of space.
    • Microsoft's Copilot Cowork now generally available with usage-based billing by Pradeep Viswanathan Back in March, Microsoft first revealed Copilot Cowork, a new agentic AI experience in Microsoft 365 Copilot through which users can assign tasks to AI to complete in the background. After testing the service with a limited set of customers in Research Preview for a few weeks, Microsoft announced the general availability of Copilot Cowork to customers in the Frontier program on March 30. Today, Microsoft announced the general availability of Copilot Cowork worldwide for Microsoft 365 Copilot customers. The company also highlighted that Cowork became the fastest-growing feature in the history of its Frontier program. Unlike regular Copilot Chat, Copilot Cowork can run complex, long-running, multi-tool tasks from start to finish in the cloud by using organizational context through Work IQ. When compared to Claude Cowork, Microsoft claims that Copilot Cowork will be 30% to 40% cheaper on average with its Microsoft 365 connector. For now, Copilot Cowork runs on Anthropic models, including Opus 4.8 and Sonnet 4.6. However, Frontier customers can now use GPT-5.5. Microsoft also announced Cowork 1, a secure fine-tuned model coming in the next few weeks, which is designed to handle everyday Copilot tasks at a lower cost. To access Copilot Cowork, a Microsoft 365 Copilot user subscription is required. Usage is billed separately through Copilot Credits, based on model use, context retrieval, tool calls, and runtime. Pay-as-you-go pricing is set at $0.01 per Copilot Credit. To offer IT teams full control over usage costs, Microsoft provides spending limits, usage alerts, user-level controls, reporting, and prepaid usage plans for organizations. Usage-based billing begins today. However, Frontier customers who used Cowork between March 30 and June 16 will not be billed until July 1, 2026. The Microsoft 365 Copilot app now includes a toggle to enter the full Cowork experience. Microsoft is also adding partner plugins, with Enosix, Harvey, LSEG, Miro, monday.com, Moody’s, Morningstar, S&P Global Energy, and TeamsMaestro available now. Adobe, Atlassian, Box, Canva, Databricks, and others are coming soon.
    • With Nova enabled I am not seeing a difference with compactmode.show?
    • HOLY THREAD REVIVAL   But yes, look for browser.nova.enabled and set it to true
  • Recent Achievements

    • One Year In
      Console General earned a badge
      One Year In
    • One Year In
      Twozo Technologies earned a badge
      One Year In
    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • Veteran
      branfont went up a rank
      Veteran
  • Popular Contributors

    1. 1
      +primortal
      522
    2. 2
      +Edouard
      196
    3. 3
      PsYcHoKiLLa
      111
    4. 4
      Steven P.
      90
    5. 5
      Nick H.
      71
  • Tell a friend

    Love Neowin? Tell a friend!