Gamma video setting is resetting for me each game after I change it.
Also, gamma changing in game after entering menu, sound cuts at random moments.
Same here, performance seems a lot better.
Nice work on the patch, the bug where contrast increases/decreases when entering the menu and exiting is still there, makes the game really dark sometimes.
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
About Texture Streaming, even if my card has 4gb vram I use the 400mb setting otherwise I get bad performance. It loads up lower quality textures initially then upscales them, if you use the lowest setting and zoom with the scope you will notice textures loading after you use the scope and when you exit.
I don't think you need mouse smoothing when aiming because there is this built in effect that the slowest you move your mouse the more resistance there is to movement.
I think that the game uses a lot of vram because not everything is optimized yet which I believe is the cause of stuttering on most systems currently. I am monitoring it with msi afterburner and the game was smoother if I stayed below 3.5gb (GTX 970 which has 4gb but the 0.5gb is slower vram than normal gpus, lol).
Thing is sometimes the game starts with 4gb vram usage for some reason, so I am guessing these issues will be fixed soon. So I would recommend the lowest texture streaming and not using the .ini fix for AA but using FXAA instead for people with similar or lower end GPU's for now.
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.
Don't think TAA works to be honest.
@b4ndo Again supersampling is not the same with msaa. Supersampling upscales the resolution, so it's very demanding on the GPU. Anti aliasing settings can also cause stuttering if you are running out of vram, so be careful how much you are using on the .ini tweak.
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.
The supersampling replaces the "resolution scale" that existed in the previous patch. The AA fix of the first post still works for me.
@McFosat High texture settings can cause stutters too if the game uses more vram than your graphics card vram.
Yes, I've also reported it on the pinned topic. I think the game picks the menus' post process parameters and applies them on the game when you exit it.
I think on this instance it could be that you were suppressed that is why your shots missed. The accuracy is reduced a lot which is better for the overall feel of the game in my opinion.
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.
Still, I feel the speed of doing some actions like changing from weapon to grenade, using it and going back to weapon or sprinting and using the scope to focus etc. do not "sync" up with the pace of sprinting and the overall game speed. The flashbang change is more suitable with the overall current game speed (although now it's a bit too fast). I'd rather have Ins2 overall speed/feel though. But kudos to the devs for doing great work with the patches, the game is shaping up nicely!
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
After the latest patch I am getting lost connection to server midgame, didn't happen before at all.
Same thing happens when trying to use focus after sprinting.