This is a clear example, the player also added the killcam from the match recap: https://streamable.com/vkmv6
Maybe the enemy was wearing this
There seems to be stuttering / frame drop when shooting at an enemy or getting shot at in close/medium range even with frame smoothing/limiter on or off.
Could be system related (cpu) or vram issue? GTX 970 / 2500k
Maybe has to do with hit registration detection.
Hit registration seems off.
Objects get blurred when moving the camera.
Seeing improvement since beta1, 90-100 fps with GTX 970 and i5 2500k on firefight. On skirmish it's 60-70 fps. No stutters.
Most settings on low.
Same here, I think it happens when you are using the menu or some part of it even if it's the first round.
It needs tweaking, either lower speed and keep the current TTK, or reduce TTK and keep speed the same. Should play more like Ins2.
Along with fixing the hit registration issues (maybe if that is fixed we will get a better idea about TTK).
Respawn times can be reduced to counter the changes.
I think the game mechanics will be improved later, we already saw different game feel because of the optimization/fixes the devs worked on. With more optimization and fixing the hit registration issues it will be easier to judge if the mechanics need tweaking.
Noticed the same thing, but both issues were present before the latest patch.
Same here, stuttering still present with second patch. GTX 970 i5 2500k 16gb ram and SSD. For some reason they happen on crucial moments for me, like when getting shot at or turning around in a corner.
Yes this needs to be addressed, most of the time I can only hear my own. It is also a good balance to make people sprint less and use crouch/alt key more as well.
Also getting them with newer patch as well, all settings on Low.
I noticed that sometimes it also happens when an objective is captured and a lot of sound effects/voice overs happen at this time.
In CSGO camping is FAR less of an issue compared to INS:S. Maps are less "complex", less cluttered, way less spots to camp. People usually know the common spots and just pre-aim them etc. . There are way too many situations in ins:s that go like this: you run (you have to move at some point of this game, although i've seen far too many players not moving for a whole round...), you get shot from somewhere, you die, you are wondering where the other guy was and why he was able to spray you down from some aetheral space with an Uzi. Sorry, but that's not fun for casuals.
That's the point though. Bad players ( = casuals in this scenario ) make mistakes. They don't enjoy super punishment for mistakes. That's why no one plays CPMA or other shooters with an extremely high skill ceiling.
CSGO f.e. isn't balanced around comp. The game simply works on every skill level. Look at mobas.... LoL and Dota2 aren't balanced around comp. And yet again: they work on all skill levels.
If you try to cater to "casuals" by lowering the skill ceiling, you are just making your game boring and stale. You don't want people to get "bored" that fast. That's when they stop playing.
There is no such thing as online fps and casual. You play fps to be competitive, be it reflexes, aiming skills or tactical. If someone wants to play casually he has the option to play pve or with bots, or even a single player fps game. The reason there are less players playing Ins franchise is marketing, since bigger companies have more resources to push a game. Also CS franchise is quite old and has established a big player base.
Yes, I noticed that too, the more players are in the server the more the performance drops. Might be worth trying this tweak if you are using Windows 10 creators update: https://forums.focus-home.com/topic/29705/possible-stuttering-fix-for-windows-10
There is a bug in Windows 10 (creators update) that does not allow standby memory to free up, making use of the pagefile instead of available memory. This can cause stutters on games and has been mentioned by Battlefield 1 players. To read more about it:
Instead of the .exe there is a .bat script that creates a scheduled task to clean standby memory, you can find the script here: https://www.reddit.com/r/Windows10/comments/9e1yy4/when_will_the_free_memory_bug_bug_be_fixed/
I've been testing it and I think it seems to be working for now but can't say for sure.
The 1 sec stutter when an objective is captured is still there though.
Picking up weapons is still buggy, sometimes it's hard to do and when it works for some reason the animation plays twice.
The bug that makes things darker when you go on the menu and back to the game still happens.
It's easy to reproduce when spectating: 1) Go to menu 2) Exit menu, game gets darker 3)Click space to change camera twice 4) Game gets back to normal brightness
I think the game picks up the exit menu's post processing or something funny, because if the menu's background scene is bright it makes the game brighter, if it's dark then darker