8 replies to this topic

[Zureal]

[color=#959595]
I am having a issue with micro stutter recently with the recent patch that came out 02/20/2015, If i am doing just a testing grounds thing then it is smooth as silk, but when I go into a PUG drop or anything else at first it is also butter smooth, but as soon as **** gets real and there is heavy action on screen I get a TON of microstuter that makes the game nearly unplayable.

When I go over to tomb reader or shadows of mordar it is smooth with almost no micro stutter ever but in MWO , like i said, as soon as battle is joined there is a MASSIVE amount of it for the rest of the match

I run 2 GTX 690s In SLI as I have a 4k screen and before this latest patch it was awesome but then this happened. Has anyone else had anything like this? If so does anyone know a workaround or how to fix this? I generally play at max settings on everything but I turn AA off compleatly as it is not needed at 4k.

any help will be VERY appreciated. [/color]
<p class="ipsLikeBar right clearfix" id="rep_post_4222034" style="margin: 10px 0px; padding: 0px; float: right; font-size: 11px;">

• Like This

• Quote
  
• MultiQuote
  
• Edit
  
• 
  

[Kodyn]

Ok, this is exactly what I've been experiencing.

I had initially thought it was a torso twist thing, but further study showed me that every time I was in a match and mechs started to show up, my movement would get real choppy, making aim quite difficult, and my FPS will drop more than usual.

Just before the recent hotfix to the hotfix, I was experiencing the best FPS and performance I ever had seen in this game, so you guys spoiled me, then took it away...this is like playing an N64 game with a dusty cartridge now whenever combat starts.

Maybe undo whatever changes were made to the code for the Urbie, and find a new way to implement it, rather than breaking the game for previously playable mechs?

Not meaning that to sound snarky, just that I'm a little grumpy about barely being able to play during an event due to performance issues caused by a mech we don't really need in the game.. Unless of course it's the VOIP(which I also don't use..), in which case, I eat my words about the Urbie, but I suspect it's the more likely suspect.

[Zureal]

I just hope they fix it soon then, I doint understand how doing what they did for the urbie though would effect gameplay this badly, its a major turn off and I cant even play with my crew cuz of this

[Kodyn]

Well at one point they were saying that implementing the 360 torso twist for the urbie had broken the "Center Torso" command and whatnot, so that's why I'm assuming this is related. I haven't turned VOIP on yet at all, so i don't see how it could be that.

I've also had a few other people today mention they're experiencing this, so it's not an isolated issue.

[Troutmonkey]

I've noticed stutter and frame hangs whenever a player is killed and the death message is displayed. It gets progressively worse the longer you play. MWO is riddled with memory leaks and the longer you play the more lag, stutters and graphical artefacts appear

[Bloodweaver]

Troutmonkey, on 22 February 2015 - 12:39 AM, said:

I've noticed stutter and frame hangs whenever a player is killed and the death message is displayed. It gets progressively worse the longer you play. MWO is riddled with memory leaks and the longer you play the more lag, stutters and graphical artefacts appear

Yes, this is definitely it. Just a couple of weeks ago PGI put out a patch that addressed HUD functionality, which was causing lower-than-needed framerates for almost all players. It became especially noticeable whenever, as you mentioned, a "[Player X] has killed [Player Y]" message popped up. Turning off your HUD (Rightside Shift key + F11) would drastically improve your framerate, which is how you knew the HUD functionality was the issue. Of course, then you couldn't tell who was friend or foe, so it wasn't a solution at all. This last hotfix seems to have undone whatever they did to fix that HUD functionality, because, once again, framerates take the biggest hit when "kill" messages pop up, and once again, turning off your HUD improves your framerate dramatically. Somehow they overlooked their recent HUD changes and brought it back to what it used to be. Hoping they (re)fix this ASAP.

[Zureal]

Troutmonkey, on 22 February 2015 - 12:39 AM, said:

I've noticed stutter and frame hangs whenever a player is killed and the death message is displayed. It gets progressively worse the longer you play. MWO is riddled with memory leaks and the longer you play the more lag, stutters and graphical artefacts appear

this is exactly the problem I have to, the longer I play, once combat is joined, the worse it becomes and Using fraps I can tell u that the game at 10 FPS is compleatly unplayable and not fun at all.

[Kodyn]

Yeah, please PGI, kill the Urbie code, do what you gotta do, but make this game playable...a week or more like this and I'm probably done, and I'd be surprised if many with this issue could handle it for very long.

I just got to see almost what it's like to play this game with almost real FPS, so now I know just how bad it was before...

I just have to ask, why is it that you folks cannot add anything to this game without breaking 1-3 other things? Maybe stop with new mechs, features, etc, til you learn how to use the code you have already? (Not trying to be a ****...just saying, I'm a chef, and if I cooked bad food, i wouldn't have a job...bad code from a programmer...same thing)

[Elric]

I am also experiencing this.
For me I will notice a really high ping for the first 40-60 seconds of game around 700-800. Then it will drop down to my normal 80. But I will experience stutters regardless of any mechs in my view. Sometimes while I am standing still. It has moved me off of cliffs!