80 replies to this topic

[Jace11]

Has it gone for most people?

Im not getting it anymore and I've been playing alot tonight since patch.

[c0d3x]

I am not sure what the actual bug is, but playing the Ice map, if I looked down the map with the tunnel on my left I got 4 fps, if I looked any other direction it was fine, 50-60fps. This also only happened in the area near the base. Within 30M of the new tower in the capture point.

[Coltaine]

I think I had the 4fps bug today on the forest map.

[TheUnderking]

Yeah, the memory leak is still there, it hit one of my buddies today. It didn't affect me today though I only played about 10 games and had a CTD in there somewhere.

[Wireball]

Yep, still getting it.

As I thought, my CPU usage does drop noticeably when the 4FPS glitch occurs. Interestingly, MSI Afterburner claims that my memory usage dropped somewhat as well, as shown in the attached image.

One can pick out each match from the dips between matches.

Edited by Wireball, 06 November 2012 - 09:19 PM.

[Fugu]

c0d3x, on 06 November 2012 - 08:45 PM, said:

I am not sure what the actual bug is, but playing the Ice map, if I looked down the map with the tunnel on my left I got 4 fps, if I looked any other direction it was fine, 50-60fps. This also only happened in the area near the base. Within 30M of the new tower in the capture point.

Exactly this on the same spot when looking in the same direction. Other directions are fine. Didn't matter if there were enemies or not.

[GL Chozo4]

To confirm the bug is still in fact here and the fix has not made it into the current patch. For those experiencing GPU Use drops should look into enabling performance mode for their graphics cards in their graphics control panel to avoid it dropping down into 2D-Mode due to it spending more time thrashing in the GPU-Memory than using the Core. Otherwise it seems to be throttling on a GPU-Memory overflow resulting from the still existing GPU-Memory leak.

Old thread (locked from old patch subforum): MWO: Forums - 4 FPS Issue After Multiple Plays - Page 5

Posted 03 November 2012 - 05:20 AM

Quote

Thinking I've started to narrow down the actual source of the GPU-Memory Leak and can be easily replicated without entering a game. Take note of your GPU-Memory the moment the game launches...

1) Enter MechBay
2) Click any mech be it trial or otherwise...
3) Do this a few times [even the same mech works] and then watch your GPU-Memory.

You'll have taken note that depending on your settings your GPU-Memory has been consumed an additional 10.1xMB each and every time you click a mech. Keep clicking the same mech on the 2x2 square on the [home] screen or others in mechlab and you'll simply run out of Graphics Memory and cause the client to glitch out and/or crash. It's rather interesting to further note how on the [home] screen that selecting mechs will further trigger this since they are not being displayed unless you go into the MechLab.

Point I'm noting: The source of the problem is most likely the BattleMech models not being released from memory. This would coincide from other tests of a leak of roughly 170.6xmb every match meaning 10.1xMB of GPU memory for each of 16 Battlemechs per match which are not being released from memory. You can further see this as well while waiting for players to join in game with the same increase per battlemech.

First Marker is upon first launch. The second line is the result of simply clicking the same mech over and over in the [HOME] tab before glitching out and then killing the client.


I have carbon-copied this result to support to aid in their patching of this GPU-Memory leak in the event they are still trying to narrow down the source. While they may be aware of the issue - the reason for it may not have been clear.

EDIT: Got a reply and it has been forwarded directly to the devs... hope it helps it get in the next patch.

Quote

Hello GL Chozo4,
I will pass this on to the devs, thanks for submitting it!
Regards,
<redacted>
GameMaster
MechWarrior® Online™

Edited by GL Chozo4, 06 November 2012 - 09:29 PM.

[Max Immelmann]

still getting this bug every 6-7 games. problem still exists.

[Mackensen]

Why are they not fixing the memory leaks? It should be top priority by now. They have excellent and detailed feedback on the 4 fps problem. Gameplay and introduction of new features is very low on the priority list compared to that in my opinion.

[Wireball]

Incidentally, note that my GPU speed did not downclock when this issue occurred, nor has it ever downclocked in Mechwarrior Online (although it's not something I'm a stranger to - I used to experience the downclocking issue with older Nvidia drivers when running Folding@Home GPU on my GTX560 a year ago, before I hit on the 285.62 drivers).

Mackensen, on 06 November 2012 - 09:38 PM, said:

Why are they not fixing the memory leaks? It should be top priority by now. They have excellent and detailed feedback on the 4 fps problem. Gameplay and introduction of new features is very low on the priority list compared to that in my opinion.

Hit detection was the top priority before this patch, since it was affecting just about everyone on every match. The 4FPS bug is annoying, but can be circumvented (now if I could just remember to restart the client every four or five matches instead of stumbling over it repeatedly...)

That being said, I don't doubt that they're working on the memory leaks - but such things can be a massive pita (like the food) to track down, so I'm not particularly surprised that it's taking a while. Sometimes it seems like programming is 10% writing code and 90% trying to figure out why it isn't working right.

Edited by Wireball, 06 November 2012 - 10:48 PM.

[Guilty1]

Hello

I have huge issue with my FPS. Couple of months ago when i first tried this game my FPS was pretty good (50 when not fighting and 30-40 in combat). Then i didnt know how to play or anything and i didnt continue playing. Now i came back week ago because lots of my friends from our gaming community started playing this. My FPS was very poor. maybe 30-35 when just walking (20-30 in forest colonny) and 20-25 in combat (10-20 in forest colonny) but still it was playable. Now after this latest patch i cant play. Now my FPS is 18-25 (havent try forest colonny yet) when im just walking around and 5-15 in combat.

We have like 30-40 active MWO players in our community and we started to promote this game in community just 1 week ago. That number is rising every day and most of them have used real money allready (i planned to put my first € in this month but not anymore.Not until i can play again). And now some of them (including me) cant play this game properly or at all.

What are you doing in these patches? Making new ways to drop people (potential customers) from game by adding more smoke or some other crap to drop FPS?

Is there anyway i can turn those huge smoke things (i dont know the correct english word) or moving trees OFF? Or is there any way to drop graphics lower than low? Or is there anyone who can help me with this issue and has some mods to make it run better?

I have all craphic setting available at low or off and my specs are below.

My specs:
Intel C2D E8500
4g RAM
Ati HD 6950 2Gt
Win 7 64 bit.

Pls do something about these issues and help me play again! I really love this game but i just cant play anymore.

- Guilty1

Edited by Guilty1, 07 November 2012 - 04:08 AM.

[MadPanda]

The map caustic valley now suffers from seemingly random fps drops. It seems to happen sometimes when you are turning (rendering areas?). The fps drops significantly, to like 5 fps. It happens at random times during the game, so not all the time. This problem was not present in previous patch, it is only in this patch. This problem occurs every game on caustic valley.

[The Image]

Seriously, if you're going to make this open beta, then and start requiring that we buy MC and such, you'd better consider adding a "disco" bonus.

So far, every, AND I DAMN WELL MEAN EVERY mission I've played as had at least ONE disco on either side. Either because they get kicked before the mission starts, or have to drop because they have the 4ps issue, or at some point in game they just get randomly kicked for no apparent reason.

The last few, I've had 2 on my side, none on the other. So we're starting at a 25% disadvantage.

Add a DISCO bonus to the losing side, just enough to pay the difference between the money earned and what it takes to repair their mechs, if their side had disco's.

If I have to start every match missing 1/8, to 1/4 of my fire side's fire power, I want to be compensated for it.

It's very frustrating, and I'm tired of hearing how it's beta. At this point going to OPEN beta, sets up an expectation that while the game mechanics may have flaws, or may be incomplete, the INFRASTRUCTURE and CLIENT STABILITY are ready for paying customers.

It's very extremely, painfully, and frustratingly obvious that at this point, it's not.

[costi]

I hear you, except I'm the one having drops. My client crashes every single match, at random points (if I'm lucky it's after I'm dead), making the game completely unplayable.

[Kobura]

I think the problem is deciding who clicks quit, who yanks their ethernet cable for a second, and who legitimately has a connect failure

Because a lot of people (A LOT OF PEOPLE) snip a trial mech or two into random matches, walk out, then go play a "real" game in their own mech while the trials do nothing and farm free 0-risk cbills

Vote that disconnected players get what they earned to that point and nothing more (including win/lose bonus)

At least until they can discern who's gaming the system.

[Kittamaru]

First time I ever experienced it... I started at the docks and if I faced the rest of the map, I got 4fps... if I turned around, I was fine. I ended up hiding behind the ship and powering down since I couldn't do anything useful.

First time it happened was after several rounds in a row... and I played river city probably half a dozen times before this happened *shrugs*

[Zombie SixNine]

I had the same issue in River City. Close your client and restart, I do believe it is a known issue. It has also happened to me in Caustic Valley and Forest Colony.

[CPL Madison]

Sometimes when launching matches my frame rate gets locked to 4 FPS

solution is to close client and restart


Is anyone else experiencing this problem?

(F9 in game to see fps)

[Hidirian]

Yes, This bug has been around quite awhile and frankly I'm surprised it hasn't been fixed yet. : /

[John MatriX82]

yep, happens after you leave the game open for a lot of time, or after several continuous matches without restarting the client. Best fix is after having 4-5 matches to close the client and restart it.