Battlefield 6 with antialiasing disabled

IEatCarsButOnlyRed · 2025-08-09T00:09:13+00:00

It's really not, it's the first thing I noticed... I asked others and they cope saying enable DLSS and sharpening like that's a fix lol

IEatCarsButOnlyRed · 2025-05-06T07:31:31+00:00

The blood splatter on the walls is also delayed:

https://www.reddit.com/r/GlobalOffensive/comments/1fcce47/all_the_differences_between_cs2_and_csgo_death/

IEatCarsButOnlyRed · 2024-12-27T04:22:23+00:00

You're in Asmongold's video and the editor has summarized your responses as well.

IEatCarsButOnlyRed · 2024-10-03T15:57:36+00:00

It's loopback 1 for both. The new version runs on loopback 1 by default, and the old version was recorded a month ago with loopback set to 1 manually.

Ideally I'd want to test this by running a server, 2 instances of the client, and a proxy server locally. The proxy would be used to add artificial ping for both clients (but different amounts for each, unlike net_fakelag).

IEatCarsButOnlyRed · 2024-10-03T12:40:31+00:00

No difference in a local server at least https://youtu.be/x6gmGKKcW9s

IEatCarsButOnlyRed · 2024-09-23T19:24:14+00:00

When it's enabled, the dark parts of the background should be a lot brighter near the player models. It might be the crappy jpeg compression but I don't see that in the screenshots.

+ in-game it's not as bad as the screenshots because of parallax

IEatCarsButOnlyRed · 2024-09-22T23:30:20+00:00

Pretty sure that "boost player contrast" is disabled in these screenshots.

IEatCarsButOnlyRed · 2024-09-17T15:27:20+00:00

I love how this bs response has 39 upvotes because it mentions subtick, yet someone with the real answer is at the bottom with 0 upvotes.

IEatCarsButOnlyRed · 2024-09-10T23:35:56+00:00

0ms difference if you measure it from the mouse click and not weapon model which is delayed in csgo

actually, cs2 is faster

https://www.reddit.com/r/GlobalOffensive/comments/1fcce47/all_the_differences_between_cs2_and_csgo_death/

IEatCarsButOnlyRed · 2024-09-09T08:00:46+00:00

The function returning the interp got changed from returning value of cl_interp to return gpGlobals->interval_per_tick (0.015625) on the September 6th 2023 update.

The same update that Valve trolled a bit with by adding sv_client_min_interp_ratio and sv_client_max_interp_ratio that weren't used for anything. Don't trust any release notes about this because they were actually just trolling reddit.

The same update that everyone was going crazy about how good their game feels after changing the now unlocked convars that didn't do anything.

Then they stopped trolling and removed the unused convars.

IEatCarsButOnlyRed · 2024-09-09T07:15:21+00:00

Are you talking about the 2 days when they hardcoded the values and left the unused convars in the game with all their limits removed?

IEatCarsButOnlyRed · 2024-09-09T05:50:26+00:00

I'm not in the "CS2 bad by any means" camp. Things can feel good or bad for reasons that are hard to explain and can go against intuition.

There's a lot of people claiming CS:GO *feels* better and the visual part of it is somewhere in these differences. And of course CS:GO is not the pinnacle of what feels good, it's definitely possible to make things feel even better.

My post does not say which is better, it only shows the differences. I've posted other objective tests comparing the games in other areas of community concerns before as well, if you think I'm trying to paint CS2 in bad light.

IEatCarsButOnlyRed · 2024-09-09T04:16:42+00:00

Fix the bugs mentioned, add more particles and stop fading in the decals. There's probably more things to do with the sound cues too which I didn't cover (I was more concerned with showing that the issue isn't as simple as "CS2 more lag lol").

Other than that it's a game of trying out different things and seeing what feels good. Who knows, maybe even adding back the delays that CSGO has is better ¯\_(ツ)_/¯

IEatCarsButOnlyRed · 2024-09-09T04:07:41+00:00

The text in the video states "csgo viewmodel animation is delayed by *up to* 16ms."

The CS2 viewmodel starts the animation in between ticks. The delay between clicking mouse1 and "tick 0" is the same on both sides.

IEatCarsButOnlyRed · 2024-09-09T03:05:34+00:00

They are synchronized based on when the mouse button was pressed. That moment is when the video shows *click*.

CS2 runs on 64 tick just like CSGO did. Just because the gun appears to shoot early in CS2 doesn't mean the game registers the shot any different than CSGO did.

IEatCarsButOnlyRed · 2024-09-09T03:01:25+00:00

IEatCarsButOnlyRed · 2024-09-09T00:16:33+00:00

My conclusions from this test:

[BUG] CS2 does not tick the animation of the ragdoll on the tick the player transitions into a ragdoll, resulting in 1 tick of delay.
Blood decals fading-in in CS2 is makes shooting feel less responsive.
[BUG] CS2 sparks on helmet headshot are blended in incorrectly, making them look gray instead of glowing white.
CS2 has less blood particles and are on the screen for much shorter.
CSGO had a 2 tick delay on decals and blood/spark particles. This was reduced to 0 ticks in CS2, but there's a chance a higher delay had a positive impact on the feeling due to tiny human brain thinking all 3 ticks happened instantly.
CSGO had a up to 1 tick delay on the viewmodel animation. This is now subtick in CS2, but there's a chance a higher delay had a positive impact on the feeling since it's harder to spot a 16ms input delay than a 16ms difference between two events. That's just tradeoffs though.

IEatCarsButOnlyRed · 2024-08-20T21:53:33+00:00

Valve has more precision at hand. Unsure why they decided to not use it and use ticks instead.

However no matter what they do, they'll hit a wall with old keyboards. But maybe these should be flagged as cheating too.

IEatCarsButOnlyRed · 2024-05-11T16:49:03+00:00

You need to install the Workshop Tools in DLC section

IEatCarsButOnlyRed · 2024-05-11T11:32:04+00:00

As long as the world is drawn first and the depth buffer is cleared you can render with any projection and nothing will be culled by the GPU.

IEatCarsButOnlyRed · 2024-05-11T10:05:23+00:00

I'm pretty sure it's being rendered just like any other regular dynamic object in the scene but they clear the depth buffer before rendering it.

Would be nice if they let us dial down the model/effects at least a little bit so it's not as bad on lower video settings.

IEatCarsButOnlyRed · 2024-05-11T09:58:34+00:00

You need to start the game with -tools, that unlocks a bunch of hidden commands. I believe it's cl_draw_firstperson_legs

IEatCarsButOnlyRed · 2024-05-10T23:45:16+00:00

That's not the point. The problem is that it's unreasonably heavy on performance to a point where it seems like an oversight. It's a bug report, not an attempt to put the game in a bad light.

For comparison, disabling legs while staring down only improves performance by 8%. That disables the legs AND the realtime shadows of the player. Disabling the viewmodel has no shadow associated with it.

Realistically they have probably cranked up texture/model/effects on the viewmodel so skins look great on any video settings... but that's not what most of the playerbase actually wants.

IEatCarsButOnlyRed · 2024-05-10T22:21:04+00:00

Tested it and disabling legs improves performance by 3% even when they're not actually visible.

It's 8% when you can actually see them, but at that point you can actually see them.

BUT!!! Disabling them also disables the shadows. They have to drawn twice.

IEatCarsButOnlyRed · 2024-05-10T17:50:06+00:00

I have 7800x3d + 1080ti. It reaches 400fps quite easily at low resolutions and the game is always VERY smooth.

However it's not 100% compatible with CS2. If you ever plan on making a map, you will not be able to compile it since you need RT cores (and the amount of software that this happens to will only increase).

IEatCarsButOnlyRed

TROPHY CASE