Horrible Stuttering

[Liquidator]

I have GTX 1080 and Core i7. I get horrible stuttering on any settings,, even on the lowest resolution. I tried everything I could find online and I don't have this problem on other games. Please help. :(

[FlashBurn]

Originally posted by Zaco ℜackam:

is it always stuttering or when you are behind the lines and need to fall back?

This one is a NEW bug. Super weird.

[CaptainVietnam]

Originally posted by ManxHedgehog:

FIXED IT. Apparently having Chrome open was causing some sort of CPU problem. Still not buying the game, due to the same problems as always: 1) no friendly markers on your team unless you are right next to them, thus having to look at map constantly to see where your team is (if I can see them magically on the map, why not magically in 1st person?) 2) nobody is using voice chat 3) sniping is ridiculously easy, if I'm running sideways 200m from a sniper he should not be able to kill me 1st shot every time. In real life snipers do not shoot running targets as your chances of hitting them is close to zero, and they do not train to do this either.

1)Friendly markers mean nothing and are just put in for new/bad players. Most if not all my kills are from comfirming that it is an enemy by simply seeing his outline or colors that he is wearing. I almost never shoot a teamate unless he runs into my fire when In a firefight

2)Most coms should be resereved for team leader and sl there is voip now so you can talk to players next to you while keeping coms clear not to mention squad coms are also a thing.

3)God forbid players being able to aim and track properly. Best way to not get shot is to do the apocalypto and strafe run and use as much consealment as possible. Even with a lot of hours i'm still learning were the best spots to use are.

[Liquidator]

Originally posted by ManxHedgehog:

FIXED IT. Apparently having Chrome open was causing some sort of CPU problem. Still not buying the game, due to the same problems as always: 1) no friendly markers on your team unless you are right next to them, thus having to look at map constantly to see where your team is (if I can see them magically on the map, why not magically in 1st person?) 2) nobody is using voice chat 3) sniping is ridiculously easy, if I'm running sideways 200m from a sniper he should not be able to kill me 1st shot every time. In real life snipers do not shoot running targets as your chances of hitting them is close to zero, and they do not train to do this either.

Wow, this actually worked! It reduced the stuttering a lot! I now get microstutters, which is still borderline unplayable, but it's way better than before, so step the right direction? Thanks a lot regardless. I hope the devs fix this soon.

[Drifter]

They can't fix it. It stutters for everyone on any map with reasonable geometry.

They developed the engine themselves to avoid the licensing costs and they don't have the required competence. They're a small studio, it's outside their purview.

The lead dev replied to you up there talking about anti-virus etc. It's crazy stuff.

It's so balls out obvious and disruptive (they're still trying to improve Hue City in the most recent patch) that it's become a bit of a taboo to even mention it.

For their next title they will be forced to license a new engine. They were ~3 years behind the technology curve with this one and were forgiven because they nailed the gunplay. But at some point they will have to invest in order to make more back, or risk their niche shrinking even further.

It's a shame because they have core gameplay to be a smash hit, but it needs a better presentation to reach the wider market

etc etc blah blah blah cue whinging about 'my game' etc etc. No one cares mate.

[ASSMAN]

Originally posted by Drifter:

It's a shame because they have core gameplay to be a smash hit, but it needs a better presentation to reach the wider market

I agree entirely. I've put up with it for so long because I love it, but its pretty trying

[xBGLx狂犬]

You just must to clean your pc from pron, viruses and other problems.

I have quiet old pc ( i7 3770k, gtx 1050, ssd Samsung evo 250 gb and win10 on my Intel ssd drive) I have some lags and fps issues only on song be and forrest sometimes, otherwise its 50-100 fps. Even on my old gtx670 I've had 60-80 fps on medium + high textures and character details, lol

[Slowpork]

Originally posted by xBULLETx:

You just must to clean your pc from pron, viruses and other problems.

I have quiet old pc ( i7 3770k, gtx 1050, ssd Samsung evo 250 gb and win10 on my Intel ssd drive) I have some lags and fps issues only on song be and forrest sometimes, otherwise its 50-100 fps. Even on my old gtx670 I've had 60-80 fps on medium + high textures and character details, lol

The game runs like crap with more players on a server. And some maps have such ♥♥♥♥♥♥ optimisation that FPS can easily drop to 40-50. No need to be such a hard ass fanboy when the game is clearly doesn't work how it supposed to. Especially considering the graphics level.

[xBGLx狂犬]

Originally posted by Slowpork:

The game runs like crap with more players on a server. And some maps have such ♥♥♥♥♥♥ optimisation that FPS can easily drop to 40-50. No need to be such a hard ass fanboy when the game is clearly doesn't work how it supposed to. Especially considering the graphics level.

may be you're playing on the laggy servers? I am playing on Red orchestra .ru or PBS servers , no lags on most of the maps , song be te , operation forrest and may be firebase georgina are lagging for me . And I have quiet old pc.
I am not fan boy , I just can't understand why people with better pc's can't handle their hardware and software and post same themes without even writing all their specs and record video with lags , this will help others to solve their problems

[Slowpork]

Originally posted by xBULLETx:

Originally posted by Slowpork:

The game runs like crap with more players on a server. And some maps have such ♥♥♥♥♥♥ optimisation that FPS can easily drop to 40-50. No need to be such a hard ass fanboy when the game is clearly doesn't work how it supposed to. Especially considering the graphics level.

may be you're playing on the laggy servers? I am playing on Red orchestra .ru or PBS servers , no lags on most of the maps , song be te , operation forrest and may be firebase georgina are lagging for me . And I have quiet old pc.
I am not fan boy , I just can't understand why people with better pc's can't handle their hardware and software and post same themes without even writing all their specs and record video with lags , this will help others to solve their problems

Because people with better hardware shouldn't be doing devs work. All these glaring problems are so ♥♥♥♥♥♥♥ obvious to most players and I won't believe for a second that the devs are not aware. Most of the developing teams don't ♥♥♥♥♥♥♥ care. That's why new maps have atrocious performance.
Releasing content without any kind of testing is norm nowadays. I'm not surprised this game is not an exception. Also, I don't want the game to run with V-sync or 60 FPS lock, the comfortable minimum FPS should be 80+ without frame drops to 40-50. This is just unacceptable in 2018. Killing Floor 2 has zero issues with all kind of ♥♥♥♥ going on. RS2 has no limbs or intense gore, like in KF2, no heavy AI calculations, there is no ♥♥♥♥♥♥♥ excuse for such a poor performance. The only explanation I can find is that Vietnam renders everything, even stuff players can't see, like in "trash-tier performance game" PUBG.

[Maki Nishikino]

Originally posted by Slowpork:

Originally posted by xBULLETx:

may be you're playing on the laggy servers? I am playing on Red orchestra .ru or PBS servers , no lags on most of the maps , song be te , operation forrest and may be firebase georgina are lagging for me . And I have quiet old pc.
I am not fan boy , I just can't understand why people with better pc's can't handle their hardware and software and post same themes without even writing all their specs and record video with lags , this will help others to solve their problems

Because people with better hardware shouldn't be doing devs work. All these glaring problems are so ♥♥♥♥♥♥♥ obvious to most players and I won't believe for a second that the devs are not aware. Most of the developing teams don't ♥♥♥♥♥♥♥ care. That's why new maps have atrocious performance.
Releasing content without any kind of testing is norm nowadays. I'm not surprised this game is not an exception. Also, I don't want the game to run with V-sync or 60 FPS lock, the comfortable minimum FPS should be 80+ without frame drops to 40-50. This is just unacceptable in 2018. Killing Floor 2 has zero issues with all kind of ♥♥♥♥ going on. RS2 has no limbs or intense gore, like in KF2, no heavy AI calculations, there is no ♥♥♥♥♥♥♥ excuse for such a poor performance. The only explanation I can find is that Vietnam renders everything, even stuff players can't see, like in "trash-tier performance game" PUBG.

i7-4790 @ 3.6 GHz
GTX 760 2 GB VRAM
16 GB DDR4 RAM
HDD
1920x1080

I have no issues running this game maxed out other than a bit of stuttering on the new map which I'm sure will be addressed. I had massive FPS issues on Firebase Georgina and now it runs like hot butter after the update.

[Slowpork]

Originally posted by Maki Nishikino:

Originally posted by Slowpork:

Because people with better hardware shouldn't be doing devs work. All these glaring problems are so ♥♥♥♥♥♥♥ obvious to most players and I won't believe for a second that the devs are not aware. Most of the developing teams don't ♥♥♥♥♥♥♥ care. That's why new maps have atrocious performance.
Releasing content without any kind of testing is norm nowadays. I'm not surprised this game is not an exception. Also, I don't want the game to run with V-sync or 60 FPS lock, the comfortable minimum FPS should be 80+ without frame drops to 40-50. This is just unacceptable in 2018. Killing Floor 2 has zero issues with all kind of ♥♥♥♥ going on. RS2 has no limbs or intense gore, like in KF2, no heavy AI calculations, there is no ♥♥♥♥♥♥♥ excuse for such a poor performance. The only explanation I can find is that Vietnam renders everything, even stuff players can't see, like in "trash-tier performance game" PUBG.

i7-4790 @ 3.6 GHz
GTX 760 2 GB VRAM
16 GB DDR4 RAM
HDD
1920x1080

I have no issues running this game maxed out other than a bit of stuttering on the new map which I'm sure will be addressed. I had massive FPS issues on Firebase Georgina and now it runs like hot butter after the update.

Guess what, I can run this game with locked FPS too! The thing is, I don't want to. And people without FPS lock or V-sync on can tell the difference between stuttery mess with FPS drops and a decent, smooth gameplay.

[Joachim]

It's a problem on some custom maps and Quang Tri TE. Quang Tri is really bad. I always fear it when that map gets chosen and during artillery or grenade spam i get drop to low 40's. Otherwise some stutter when no explosions, annoying but bareable. Actually i mostly leave server when Quang Tri or Resort get chosen.

[Maki Nishikino]

Originally posted by Slowpork:

Originally posted by Maki Nishikino:

i7-4790 @ 3.6 GHz
GTX 760 2 GB VRAM
16 GB DDR4 RAM
HDD
1920x1080

I have no issues running this game maxed out other than a bit of stuttering on the new map which I'm sure will be addressed. I had massive FPS issues on Firebase Georgina and now it runs like hot butter after the update.

Guess what, I can run this game with locked FPS too! The thing is, I don't want to. And people without FPS lock or V-sync on can tell the difference between stuttery mess with FPS drops and a decent, smooth gameplay.

I'm guessing you're using a 144 Hz monitor. I don't have my FPS locked or V-Sync on.

[xBGLx狂犬]

also no fps lock or V-sync on

[FBlue]

Originally posted by FlashBurn:

Originally posted by Zaco ℜackam:

is it always stuttering or when you are behind the lines and need to fall back?

This one is a NEW bug. Super weird.

Where did this happen? Map and grid location. There was a bug that was in game when Quang first came out that affected all maps but not all out of bounds locations. It was fixed a patch or so later. This bug might have made its way back in.