20 replies to this topic

[Carl Wrede]

Its been a very long time now and the memory leak is still not fixed.. how about fixing it soon?

[Max Immelmann]

good luck with that. been barking up that tree since closed beta. apparently BASIC game play functions are not high on PGI's list of things to correct.

adding new material in a broken system is though

[Rifter]

How about the netcode, or yellow/black screen bugs, or the no hud bug, or no minimap/battlemap bug.

The truth is there are so many bugs that have been in game for months with no fixes its getting to the point where im starting to wonder if they really are just milking this for cash as fast as possible and arnt fixing the bugs because they know they will be shutting the game down in the next 6 months.

[bob1234567890]

PGI would first need to know what a memory leak is

[Havyek]

The majority of these problems seem to be with CryEngine and not anything that PGI has done.

I had NONE of these problems with FPS bugs, black/yellow screens or CTDs until the most recent CryEngine update several months ago.

[Carl Wrede]

BDU Havoc, on 21 January 2013 - 05:39 AM, said:

The majority of these problems seem to be with CryEngine and not anything that PGI has done.

I had NONE of these problems with FPS bugs, black/yellow screens or CTDs until the most recent CryEngine update several months ago.

Everybody has the memory leak, it just depends on how big your memory is for how long it takes to notice it. All of these problems have been here since forever, at least early closed beta and most likely before that.

[Program 024]

Its also can be quite difficult to track down memory leaks without testing software.

[Elkarlo]

Had a Suggestion maybe it would help

http://mwomercs.com/...59#entry1755359

[Adridos]

Carl Wrede, on 21 January 2013 - 05:43 AM, said:

Everybody has the memory leak, it just depends on how big your memory is for how long it takes to notice it.

Do you know why I'm defending this game on the forums?

Because I have a really low-end computer and I've never experienced a memory leak, or yellow screen, or any of that sort. Are those issues real? Definitly. But face the fact you're making them bigger than they are. People experiencing them are a minority on the forums and forums are a tiny minority when compared to the whole game audience.

[Felix]

Adridos, on 21 January 2013 - 06:06 AM, said:

Do you know why I'm defending this game on the forums?

Because I have a really low-end computer and I've never experienced a memory leak, or yellow screen, or any of that sort. Are those issues real? Definitly. But face the fact you're making them bigger than they are. People experiencing them are a minority on the forums and forums are a tiny minority when compared to the whole game audience.

The reason they are a minority? Most people would look at a game that has been released to the public with such glaring issues and quit to find a game with Devs who arent as embarrassing.

[Havyek]

Carl Wrede, on 21 January 2013 - 05:43 AM, said:

Everybody has the memory leak, it just depends on how big your memory is for how long it takes to notice it. All of these problems have been here since forever, at least early closed beta and most likely before that.

Wrong.

Pre-CryEngine upgrade I could play all day long and not experience any FPS degradation or crashes.
Post-CryEngine upgrade I can play 4 games before I need to restart my client or the next match will be either 4 FPS, or normal FPS until I get closer to the centre of the map, then it'll go down to 4. Same system, the only thing that has changed (and this was after the CryEngine upgrade) was the GPU. 1GB Vid card, 8 GB RAM.

Others run higher end systems and crash after several drops. Others run vastly inferior systems and have no problems at all.

[Tice Daurus]

BDU Havoc, on 21 January 2013 - 06:14 AM, said:

Wrong.

Pre-CryEngine upgrade I could play all day long and not experience any FPS degradation or crashes.
Post-CryEngine upgrade I can play 4 games before I need to restart my client or the next match will be either 4 FPS, or normal FPS until I get closer to the centre of the map, then it'll go down to 4. Same system, the only thing that has changed (and this was after the CryEngine upgrade) was the GPU. 1GB Vid card, 8 GB RAM.

Others run higher end systems and crash after several drops. Others run vastly inferior systems and have no problems at all.

Exactly. I have a top end system. Not bragging but I have a i7 core overclocked to 4.0 ghz, with 16 gig of ram with a GTX 680 with 1.5 gig of ram on that. It takes me about anywhere from 8-10 games played before I end up having to restart. Sometimes a little longer. It seems the more I play with the mechlab and change stuff, the quicker the game craps out. If I change nothing and play with one mech right off the bat and change nothing, I can go longer before having to restart.

The DEV's know about this and a UI 2.0 will be coming to hopefully address the memory leaks there, but as for anything else? I dunno. I figure let the dev's work on it.

[DaZur]

Wait...WHAT? There's not an app that scrubs code and displays a big flashing warning when it encounters a bit of code that causes a memory leak?!

Clearly this programming stuff is harder than I initially thought!

[Krazyjim]

BDU Havoc, on 21 January 2013 - 06:14 AM, said:

Wrong.

Pre-CryEngine upgrade I could play all day long and not experience any FPS degradation or crashes.
Post-CryEngine upgrade I can play 4 games before I need to restart my client or the next match will be either 4 FPS, or normal FPS until I get closer to the centre of the map, then it'll go down to 4. Same system, the only thing that has changed (and this was after the CryEngine upgrade) was the GPU. 1GB Vid card, 8 GB RAM.

Others run higher end systems and crash after several drops. Others run vastly inferior systems and have no problems at all.

Tice Daurus, on 21 January 2013 - 06:19 AM, said:

Exactly. I have a top end system. Not bragging but I have a i7 core overclocked to 4.0 ghz, with 16 gig of ram with a GTX 680 with 1.5 gig of ram on that. It takes me about anywhere from 8-10 games played before I end up having to restart. Sometimes a little longer. It seems the more I play with the mechlab and change stuff, the quicker the game craps out. If I change nothing and play with one mech right off the bat and change nothing, I can go longer before having to restart.

The DEV's know about this and a UI 2.0 will be coming to hopefully address the memory leaks there, but as for anything else? I dunno. I figure let the dev's work on it.

.......Have you guys tried reinstalling the game? I had some performance issues after a patch a month or so ago and I'm fine now after a reinstall.
Oh, and yeah, messing around with the mechlab too much eats up at your memory and you eventually have to restart if you go crazy in there (or sometimes just right after a match!)

Edited by Krazyjim, 21 January 2013 - 07:31 AM.

[SpiralRazor]

BDU Havoc, on 21 January 2013 - 05:39 AM, said:

The majority of these problems seem to be with CryEngine and not anything that PGI has done.

I had NONE of these problems with FPS bugs, black/yellow screens or CTDs until the most recent CryEngine update several months ago.

Umm...I dont know who is at fault here, but clearly something should have been done about it immediately in front of everything else.

Showstopping bugs are showstopping.

[Apoc1138]

SpiralRazor, on 21 January 2013 - 07:44 AM, said:

Showstopping bugs are showstopping.

because for a lot of users they aren't showstopping... re-starting the client every 2 hours is hardly a massive issue

[Havyek]

Krazyjim, on 21 January 2013 - 07:20 AM, said:

.......Have you guys tried reinstalling the game? I had some performance issues after a patch a month or so ago and I'm fine now after a reinstall.
Oh, and yeah, messing around with the mechlab too much eats up at your memory and you eventually have to restart if you go crazy in there (or sometimes just right after a match!)

I reinstall every other patch just in case, but no. Nothing has resolved my FPS problems.

[QuantumButler]

No why would you fix a critical game breaking issue that's been present for over 2 months don't be stupid.

[EvilCow]

Apoc1138, on 21 January 2013 - 07:45 AM, said:

because for a lot of users they aren't showstopping... re-starting the client every 2 hours is hardly a massive issue

A lot of those users who don't experience the problem seem to be very busy on the forum posting about it and adding noise to a serious problem that should have long been resolved.

I agree that it started after the engine update, it never happened before. After the update we got the memory leak and the textures corruption, apparently PGI is unable, not allowed or unwilling to fix problems in the engine code.

The only fact is that after months from the engine update the bug has not been fixed and barely acknowledged.

Edited by EvilCow, 21 January 2013 - 08:14 AM.

[Thorn Hallis]

If its so easy to fix I wonder why noone told PGI how to do it.