52 replies to this topic

[Teatimeted]

BerryChunks, on 01 January 2013 - 09:34 PM, said:

If netcode and memory leak get fixed, I'll pay 4.95. if they Fix the heat so that DHS can be unnerfed and stock variants properly well, and then take appropriate measures to stop super boating, I'll pay 15.00. If they go the other way, I'll pay nothing.

You hear this PGI? You could potentially earn yourselves 4.95 (Presumably dollars?), if you fix this problem ASAP. So what are you waiting for? That's at least enough for a bar of chocolate to share. Who wouldn't work for a bar of chocolate?!

On a serious note, yes the memory leak is annoying, but its not game breaking for me to have to restart my PC every 6-7 matches or so, if I want the smoothest performance possible. There is so little downtime in between matches in this game anyway, a few minutes wait every hour is not a killer for me.

I'm absolutely certain that memory leaks, client stability, and netcode are top on their list of fixes. Patience is a virtue!

[Rifter]

Teatimeted, on 01 January 2013 - 10:35 PM, said:

You hear this PGI? You could potentially earn yourselves 4.95 (Presumably dollars?), if you fix this problem ASAP. So what are you waiting for? That's at least enough for a bar of chocolate to share. Who wouldn't work for a bar of chocolate?!

On a serious note, yes the memory leak is annoying, but its not game breaking for me to have to restart my PC every 6-7 matches or so, if I want the smoothest performance possible. There is so little downtime in between matches in this game anyway, a few minutes wait every hour is not a killer for me.

I'm absolutely certain that memory leaks, client stability, and netcode are top on their list of fixes. Patience is a virtue!

It makes it a pain int he *** when grouping, especially when the group leader changes all the time because people keep resetting and the new group leader doesnt have everyone on his friends list.

Its actually one of the things thats sometimes make me not bother with grouping, and its downright embarrasing for PGI to have let this go on for amonths and months with no fix even though they had the problem identified over 3 months ago.

[Teatimeted]

Rifter, on 01 January 2013 - 10:39 PM, said:

It makes it a pain int he *** when grouping, especially when the group leader changes all the time because people keep resetting and the new group leader doesnt have everyone on his friends list.

Its actually one of the things thats sometimes make me not bother with grouping, and its downright embarrasing for PGI to have let this go on for amonths and months with no fix even though they had the problem identified over 3 months ago.

I'll bet it is a pain in a group, no doubt about that.

As I understand it though (and my understanding is very limited at best), it is not a simple fix, and could potentially consist of modifying most of the code... I'm sure that they are steadily working away at it. Last patch was a huge improvement in overall performance for me, and I'm crossing my fingers that next patch will offer the same level of improvement.

[smokefield]

i dont know abou that huge improvment..i was playing before with a crash every maybe 8-10 games. After the patch the game crashes every time..lol. tried everything then mailed the dev.s still waiting a solution.

[Phoenix423]

dilluminati, on 24 November 2012 - 07:31 AM, said:

Agree 100%

Back in closed beta I never had this game crippling problem. I really hope they get this fixed asap.

This problem has existed since the 9/4 (or thereabouts) closed beta patch. I emailed support at that time and they said they were aware of the issue even then, but the issue has only gotten worse since then. I used to be able to play for about 2-3 hours before the memory leaks caused a CTD; now, I play for about an hour before the memory leaks cause a CTD.

[Flyingcircus]

Teatimeted, on 01 January 2013 - 10:35 PM, said:

You hear this PGI? You could potentially earn yourselves 4.95 (Presumably dollars?), if you fix this problem ASAP. So what are you waiting for? That's at least enough for a bar of chocolate to share. Who wouldn't work for a bar of chocolate?!

On a serious note, yes the memory leak is annoying, but its not game breaking for me to have to restart my PC every 6-7 matches or so, if I want the smoothest performance possible. There is so little downtime in between matches in this game anyway, a few minutes wait every hour is not a killer for me.

I'm absolutely certain that memory leaks, client stability, and netcode are top on their list of fixes. Patience is a virtue!

you don't have to restart your PC
closing the client should be enough (at least on vista/7/8) as windows should automatically clear out any reserved ram for the application once it's been terminated
this works for me every time

fixing memory leaks in big applications however is not always as simple as it sounds so it might be a bit before it's fixed

Edited by Flyingcircus, 05 January 2013 - 07:15 AM.

[Orion-Regiment]

And now here we are in April of 2013--and several patches later, the problem still remains. In fact, after today's patch (02 April 2013), 4/5 games crashed. Two gave me memory errors (memory allocation failed), and I noticed that Task Manager showed the application gobbled up all of my available memory. Perhaps this game is truly hopeless. Whose willing to bet they don't make their publish date?

[Airborne Thunder]

unMourned, on 02 April 2013 - 06:41 PM, said:

And now here we are in April of 2013--and several patches later, the problem still remains. In fact, after today's patch (02 April 2013), 4/5 games crashed. Two gave me memory errors (memory allocation failed), and I noticed that Task Manager showed the application gobbled up all of my available memory. Perhaps this game is truly hopeless. Whose willing to bet they don't make their publish date?

Agreed, this "cryengine error" and "memory allocation of ##### bytes failed" crash to desktop is getting pretty old. I want to give you guys my time and cash but not until I can play more then 1 game without having to restart my PC. I'm sure you guys are busy creating bobble head dashboard items but please fix this soon. This thread started last year after all. Meanwhile I guess I will continue to play my 10 year old version of Mechwarrior 4 Mercs.

wait... there is a publish date?!?

Edited by x Totenkopf x, 10 April 2013 - 08:41 PM.

[Lord Psycho]

if this where the HUD issues are coming from..then dang it I'm also a victim..but I Just blow on my laptop's cooling fan to make it kick out more heat.........>.>

if this where the HUD issues are coming from..then dang it I'm also a victim..but I Just blow on my laptop's cooling fan to make it kick out more heat.........>.>

[SPencil]

Alright, I made sure to read through the whole thread to make sure no one else brought this up: memory leaks are a pain in the a** to fix.

Go ahead, ask a software engineer about how difficult a memory leak can be to trace and fix. Depending on the scale of the application in question sometimes it can be easy, but other times it can be a nightmare. Hell, what if the memory leak is in code they didn't even write, inside a CryEngine library? They have tens of thousands of lines of code to look through. Remember, not everyone in PGI is a programmer. Some people's jobs are creating and animating models, some are making maps, others are recording and mixing sounds, etc. You can't tell those people to stop working while the programmers find the needle in the heap.

I'm not trying to be an apologist, I just feel people don't truly appreciate the hard work that goes into programming

A free +1 to whoever recognizes this code:

float Q_rsqrt( float number )
{
		long i;
		float x2, y;
		const float threehalfs = 1.5F;
 
		x2 = number * 0.5F;
		y  = number;
		i  = * ( long * ) &y;					   // evil floating point bit level hacking
		i  = 0x5f3759df - ( i >> 1 );			   // what the ****?
		y  = * ( float * ) &i;
		y  = y * ( threehalfs - ( x2 * y * y ) );   // 1st iteration
//	  y  = y * ( threehalfs - ( x2 * y * y ) );   // 2nd iteration, this can be removed
 
		return y;
}

[Airborne Thunder]

I just did a complete reinstall and I was able to play 3 games including River City (Night) with NO CRASH! I uninstalled the game and deleted all related folders and did a clean reinstall and it seems to be working a lot better. You guys having the "cryengine error" and "memory allocation of ##### bytes failed" crash to desktop problem might try a clean reinstall. Seems to be working fine (fingers crossed) for me right now. I am going to do a fresh install after every new patch comes out from now on. Good luck!

[nabechewan]

SPencil, on 10 April 2013 - 09:25 PM, said:

Alright, I made sure to read through the whole thread to make sure no one else brought this up: memory leaks are a pain in the a** to fix.

Go ahead, ask a software engineer about how difficult a memory leak can be to trace and fix. Depending on the scale of the application in question sometimes it can be easy, but other times it can be a nightmare. Hell, what if the memory leak is in code they didn't even write, inside a CryEngine library? They have tens of thousands of lines of code to look through. Remember, not everyone in PGI is a programmer. Some people's jobs are creating and animating models, some are making maps, others are recording and mixing sounds, etc. You can't tell those people to stop working while the programmers find the needle in the heap.

I'm not trying to be an apologist, I just feel people don't truly appreciate the hard work that goes into programming

A free +1 to whoever recognizes this code:

float Q_rsqrt( float number )
{
		long i;
		float x2, y;
		const float threehalfs = 1.5F;
 
		x2 = number * 0.5F;
		y  = number;
		i  = * ( long * ) &y;					   // evil floating point bit level hacking
		i  = 0x5f3759df - ( i >> 1 );			   // what the ****?
		y  = * ( float * ) &i;
		y  = y * ( threehalfs - ( x2 * y * y ) );   // 1st iteration
//	  y  = y * ( threehalfs - ( x2 * y * y ) );   // 2nd iteration, this can be removed
 
		return y;
}

So much this. I'm no proper programmer, but I know how difficult it is to sort out a single memory allocation problem in endless lines of code. I'm sure PGI is working on it as quickly as possible.

[SPencil]

x Totenkopf x, on 14 April 2013 - 04:46 PM, said:

You guys having the "cryengine error" and "memory allocation of ##### bytes failed" crash to desktop problem might try a clean reinstall.

That starts happening when a file is corrupted. A clean reinstall is the only way to fix it