Загрузка видео...

Не удалось загрузить видео

На главную

People keep asking why spray doesn’t feel as smooth as CS:GO. My answer: until frame pacing is fixed, it won’t. I made an animation of the AK-47 spray magnitude at different FPS to show how the magnitude of the view angles, changes with FPS, as it should. CS2

eugenio8a8's profile picture

eugenio8a8

9,110 subscribers

41,799 просмотров • 8 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

CS2 – The Problem of Movement dependency on FPS In the video below, a macro holds a movement key for exactly 750.000 ms at different FPS values. The result is clear: lower FPS produces less precise final movement, while higher FPS gives much more accurate positioning.
0:21

CS2 – The Problem of Movement dependency on FPS In the video below, a macro holds a movement key for exactly 750.000 ms at different FPS values. The result is clear: lower FPS produces less precise final movement, while higher FPS gives much more accurate positioning.

eugenio8a8

33,963 просмотров • 8 месяцев назад

So, I tested armored aimpunch in CS2 vs CS:GO, and the results might surprise you. Yep, clickbait title. They’re the same. Here’s the video comparison with the AK-47, followed by the graph. Max CS2 value: 0.478784 degrees Max CS:GO value: 0.478100 degrees CS2
0:26

So, I tested armored aimpunch in CS2 vs CS:GO, and the results might surprise you. Yep, clickbait title. They’re the same. Here’s the video comparison with the AK-47, followed by the graph. Max CS2 value: 0.478784 degrees Max CS:GO value: 0.478100 degrees CS2

eugenio8a8

92,299 просмотров • 3 месяцев назад

In CS2, you lose FPS when utility is being used on the other side of the map, or even when someone else is in a gunfight. Kinda explains why this game doesn’t feel smooth. This shit doesn't happen in CS:GO. Sup CS2, please fix. 🧑‍🍳
0:36

In CS2, you lose FPS when utility is being used on the other side of the map, or even when someone else is in a gunfight. Kinda explains why this game doesn’t feel smooth. This shit doesn't happen in CS:GO. Sup CS2, please fix. 🧑‍🍳

Thour

298,796 просмотров • 11 месяцев назад

Udongein X2 is no longer locked to 60 fps. You can't tell from the video, but it was recorded at 240 fps; tested it and it's smooth as butter.
0:21

Udongein X2 is no longer locked to 60 fps. You can't tell from the video, but it was recorded at 240 fps; tested it and it's smooth as butter.

Potemki11

12,681 просмотров • 1 год назад

In my previous post about the #Nioh3 demo, I mentioned that when the game isn’t consistently holding 60 FPS or 120 FPS, several issues can show up. Here’s a clearer breakdown of what's going on. The main reason is that the game speed and physics are tied to the frame rate. When you enable the 120 FPS cap, the engine start overreacting and pushes CPU usage very high, even if the game is still running at around 60 FPS (as shown in the first example). In the second clip, you can see the uneven, jittery camera movement I mentioned before. Notice how much smoother 60 FPS and 120 FPS look compared to the unlocked side. Also, camera movement at 60 FPS is slightly faster than at 120 FPS. In the third clip, player movement is slower when the frame rate is unlocked. This doesn’t happen all the time, but it shows up often enough to be noticeable. Because of how the Katana Engine behaves, the game is clearly designed around 60 FPS. Running at 120 FPS is possible, but it’s only recommended if your system can maintain that target almost all the time, which isn’t easy to achieve. There’s also an alternative workaround where you select the 60 (locked) option and enable Frame Generation (DLSS or FSR 3), as shown in the last clip. The downside is that DLSS Frame Generation tends to show the same stuttery look as when the frame rate isn’t holding a fixed target, likely due to Reflex keeping the frame rate slightly below target. FSR Frame Generation, on the other hand, looks much smoother and works better here.
1:17

In my previous post about the #Nioh3 demo, I mentioned that when the game isn’t consistently holding 60 FPS or 120 FPS, several issues can show up. Here’s a clearer breakdown of what's going on. The main reason is that the game speed and physics are tied to the frame rate. When you enable the 120 FPS cap, the engine start overreacting and pushes CPU usage very high, even if the game is still running at around 60 FPS (as shown in the first example). In the second clip, you can see the uneven, jittery camera movement I mentioned before. Notice how much smoother 60 FPS and 120 FPS look compared to the unlocked side. Also, camera movement at 60 FPS is slightly faster than at 120 FPS. In the third clip, player movement is slower when the frame rate is unlocked. This doesn’t happen all the time, but it shows up often enough to be noticeable. Because of how the Katana Engine behaves, the game is clearly designed around 60 FPS. Running at 120 FPS is possible, but it’s only recommended if your system can maintain that target almost all the time, which isn’t easy to achieve. There’s also an alternative workaround where you select the 60 (locked) option and enable Frame Generation (DLSS or FSR 3), as shown in the last clip. The downside is that DLSS Frame Generation tends to show the same stuttery look as when the frame rate isn’t holding a fixed target, likely due to Reflex keeping the frame rate slightly below target. FSR Frame Generation, on the other hand, looks much smoother and works better here.

BenchmarKing

17,820 просмотров • 5 месяцев назад

Come and See (1985) is one of the most harrowing war films ever made. It doesn’t frame war as spectacle, it traps you inside a child’s point of view and refuses to look away. By the end, you feel as shattered as the boy does.
0:25

Come and See (1985) is one of the most harrowing war films ever made. It doesn’t frame war as spectacle, it traps you inside a child’s point of view and refuses to look away. By the end, you feel as shattered as the boy does.

cinesthetic.

107,161 просмотров • 5 месяцев назад

🫨 DID YOU FEEL IT?: Magnitude 6.1 earthquake strikes off the northwest coast of Cuba with reports of shaking felt as far north as Orlando, Florida. Stay with FOX Weather for the latest:
4:36

🫨 DID YOU FEEL IT?: Magnitude 6.1 earthquake strikes off the northwest coast of Cuba with reports of shaking felt as far north as Orlando, Florida. Stay with FOX Weather for the latest:

FOX Weather

278,320 просмотров • 1 месяц назад

Surprise! NASCAR: Dirt to Daytona is seen as one of the best classic NASCAR games, but it always had a downside of being locked to 30 FPS. This changes today: I uncapped the physics simulation updates, achieving perfect 60 FPS, just like Heat 2002 did.
0:30

Surprise! NASCAR: Dirt to Daytona is seen as one of the best classic NASCAR games, but it always had a downside of being locked to 30 FPS. This changes today: I uncapped the physics simulation updates, achieving perfect 60 FPS, just like Heat 2002 did.

Silent

77,000 просмотров • 8 месяцев назад

“On my 50th birthday, even though we tried as much as possible to control it so people wouldn’t spray money in the air, after everything, I was still invited by the EFCC to answer for it.” 👀👀 — Obi Cubana reveals
0:44

“On my 50th birthday, even though we tried as much as possible to control it so people wouldn’t spray money in the air, after everything, I was still invited by the EFCC to answer for it.” 👀👀 — Obi Cubana reveals

CHUKS 🍥

117,437 просмотров • 8 месяцев назад

Another day, another odd and old-school technical issue in #Nioh3. This game doesn’t just expect the frame rate to hit its FPS cap to work properly, it also wants the FPS to line up with the display refresh rate. Using the 60 fps cap at 120Hz (or higher) can result in lots of frame-time spikes and microstuttering. the only way to avoid this is to switch the refresh rate to 60 Hz, which gives a much smoother frame time graph. Frame Generation on top of a 60 FPS base at 120 Hz works flawlessly without any frame time issues.
1:16

Another day, another odd and old-school technical issue in #Nioh3. This game doesn’t just expect the frame rate to hit its FPS cap to work properly, it also wants the FPS to line up with the display refresh rate. Using the 60 fps cap at 120Hz (or higher) can result in lots of frame-time spikes and microstuttering. the only way to avoid this is to switch the refresh rate to 60 Hz, which gives a much smoother frame time graph. Frame Generation on top of a 60 FPS base at 120 Hz works flawlessly without any frame time issues.

BenchmarKing

37,677 просмотров • 5 месяцев назад

I keep getting the same question from different people here on X: “Msunu, don’t you get tired of defending the EFF and Julius Malema?” Why should I get tired? Why do you want to dictate how I should defend my own organisation and its leader? I support the EFF out of conviction, not convenience. As long as I believe in what it stands for, I will continue to defend it without apology. Misunu yenu!
0:31

I keep getting the same question from different people here on X: “Msunu, don’t you get tired of defending the EFF and Julius Malema?” Why should I get tired? Why do you want to dictate how I should defend my own organisation and its leader? I support the EFF out of conviction, not convenience. As long as I believe in what it stands for, I will continue to defend it without apology. Misunu yenu!

Msunu ka Johann Rupert

39,013 просмотров • 20 дней назад

Asmongold explains how he deals with the “toxicity” from the online left “It doesn’t bother me..i don’t even really view them as people, I view them as like animals”
0:57

Asmongold explains how he deals with the “toxicity” from the online left “It doesn’t bother me..i don’t even really view them as people, I view them as like animals”

yeet

728,362 просмотров • 9 месяцев назад

🚨🇬🇧 “WHY on Earth Wouldn’t you have an enquiry into it?” Bravo this News Presenter for asking the obvious simple question - the answer as to why Labour won’t should be obvious - it exposes those still in power who were fully complicit at the time.
0:27

🚨🇬🇧 “WHY on Earth Wouldn’t you have an enquiry into it?” Bravo this News Presenter for asking the obvious simple question - the answer as to why Labour won’t should be obvious - it exposes those still in power who were fully complicit at the time.

Concerned Citizen

292,336 просмотров • 1 год назад

Cek Mat Saleh: The aid is too slow for a disaster of this magnitude. It is as if the Indonesian government does not consider this to be its people. I think the system is very difficult at the moment. UN Development United Nations
1:41

Cek Mat Saleh: The aid is too slow for a disaster of this magnitude. It is as if the Indonesian government does not consider this to be its people. I think the system is very difficult at the moment. UN Development United Nations

Acheh Imperial Archives

43,969 просмотров • 7 месяцев назад

#WATCH | Uttarakhand | People rushed out of their buildings in Dehradun as strong tremors were felt in different parts of north India. Visuals from the Secretariat. As per National Centre for Seismology, an earthquake with a magnitude of 6.2 on the Richter Scale hit Nepal at 2:51 pm today.
0:32

#WATCH | Uttarakhand | People rushed out of their buildings in Dehradun as strong tremors were felt in different parts of north India. Visuals from the Secretariat. As per National Centre for Seismology, an earthquake with a magnitude of 6.2 on the Richter Scale hit Nepal at 2:51 pm today.

ANI

83,728 просмотров • 2 лет назад

Screaming 13 is so good. Why is Tesla not sending it out? Maybe to pair it with the holiday update. Also I show how FSD moves as if it's attached to the car in front of it. So smooth, no delay, no lag.
1:54

Screaming 13 is so good. Why is Tesla not sending it out? Maybe to pair it with the holiday update. Also I show how FSD moves as if it's attached to the car in front of it. So smooth, no delay, no lag.

Dirty Tesla

174,115 просмотров • 1 год назад

i did the thing from the SV movies where the characters move along with the camera won't keep it in the game as even at normal FPS it looks really jarring, but it's a cool attempt nonetheless
1:03

i did the thing from the SV movies where the characters move along with the camera won't keep it in the game as even at normal FPS it looks really jarring, but it's a cool attempt nonetheless

strix

22,279 просмотров • 2 лет назад

Trying to fix the FPS issues today If I'm on MacBook Pro M3 with battery >20% or power connected I get 120 FPS The moment I go below <20% battery, M3 goes in power save mode I think so FPS drops to 30 FPS 30 FPS is fine but it also decreases the entire game speed by 30/120 (so 4x) Same on iPhone, I get 30 FPS, but the game gets too slow My Cursor written animate() function is, which runs on requestAnimationFrame, but I guess that deltaTime code needs some fixes to disconnect it from the FPS, I already tried but didn't work Ideally 120 FPS or 30 FPS or 10 FPS all runs at same speed even if lower or higher frame rate function animate() { requestAnimationFrame(animate); // Calculate delta time in seconds, but use fixed timestep for physics const currentTime = const rawDeltaTime = (currentTime - lastFrameTime) / 1000; deltaTime = 1/60; // Force fixed 60 FPS timestep for all physics lastFrameTime = currentTime;
0:26

Trying to fix the FPS issues today If I'm on MacBook Pro M3 with battery >20% or power connected I get 120 FPS The moment I go below <20% battery, M3 goes in power save mode I think so FPS drops to 30 FPS 30 FPS is fine but it also decreases the entire game speed by 30/120 (so 4x) Same on iPhone, I get 30 FPS, but the game gets too slow My Cursor written animate() function is, which runs on requestAnimationFrame, but I guess that deltaTime code needs some fixes to disconnect it from the FPS, I already tried but didn't work Ideally 120 FPS or 30 FPS or 10 FPS all runs at same speed even if lower or higher frame rate function animate() { requestAnimationFrame(animate); // Calculate delta time in seconds, but use fixed timestep for physics const currentTime = const rawDeltaTime = (currentTime - lastFrameTime) / 1000; deltaTime = 1/60; // Force fixed 60 FPS timestep for all physics lastFrameTime = currentTime;

@levelsio

446,331 просмотров • 1 год назад