Battle Eye Corrupted memory #0-5

[Ray]

Good news! I no longer get Corrupted Memory #x!
Now the client's not responding. =D

[SpiltCoffee]

Rubbish. I know for a fact and have seen it happen to others, that it kicks for not responding whenever it damn well feels like it. There doesn't need to be a non-responsive period for it to kick. It happens in every server I've been in and not just to me and only since things started going wrong with the corrupt code.

You did create another problem, because it wasn't there a week ago. End of. If you want to blame it on everything under the sun that's your problem. Just don't expect people to be kind to you when they can't play for more than 5 minutes. Also, I never said there weren't problems with the Soldat netcode.

Stop deviating from the subject, fix whatever you did that screwed it up and let us play Soldat.

$able's done his job, so now it's up to EnEsCe to do his, so go annoy him instead.

Try reading what I said. Battleye could deal with it before onesingleupdate and then suddenly all hell broke loose. + what BombSki said.

Oh, you should have seen the servers before this. At least every server in Australia had a hacker in it making everyone get kicked for bad packets. At the moment, the kicks that are occuring are extremely mild in comparison.

[Bloo]

I think that there is something that you should realize, bloo. Battle-eye is a constantly changing piece of software, which has to be patched and maybe even redesigned whenever a bunch of geeky 'hackers' find another exploit in it. If you read sable's post you must have seen that one of those exploits was that a hacker could use BE to kick you!
This means two things: BattleEye was, is and will be updated CONSTANTLY. If it stands still, the exploiters win. Another thing is that maintaining such a piece of software is everything accept easy. Creating some software is one thing, but making sure it will be adaptable for the future and on top of that keeping it compatible with third party software (like the soldat netcode) looks like a hell of a job to me.
Therefor I think sable deserves a little more respect than you give him.

I have now released another workaround fix that reduces the amount of BE packets being sent. Could everyone who had problems before please post if that fixes it for him/her?

All he had to do was release the fix days ago or tell us he was going to do it and there would have been no problem. I'm not entirely stupid and I have a pretty fair idea of how this stuff works, so thank you for your pointless rant, but I do understand.

Also, thank you $able for releasing a fix - It seems to have worked.

[JupiterShadow]

Omg ray, your sig is huge!!!

[-Major-]

I vote that enesce shall fix the netcode instead of having sable work his ass off.

[Bloo]

I vote that enesce shall fix the netcode instead of having sable work his ass off.

It's probably easier for $able to work his arse off for a year than for Enesce to 'fix' the netcode.

[$able]

All he had to do was release the fix days ago or tell us he was going to do it and there would have been no problem. I'm not entirely stupid and I have a pretty fair idea of how this stuff works, so thank you for your pointless rant, but I do understand.

Also, thank you $able for releasing a fix - It seems to have worked.

See, you still don't get it.

I have not really fixed anything, I have only worked around it to cope with the problems in the Soldat netcode. The reason I didn't do this immediately was that I first wanted to find out what the actual problem is and look into a possible real solution.

[Bloo]

See, you still don't get it.

I have not really fixed anything, I have only worked around it to cope with the problems in the Soldat netcode. The reason I didn't do this immediately was that I first wanted to find out what the actual problem is and look into a possible real solution.

Yeah, bored hearing about the Soldat netcode now. There are several other ways to look into a 'possible real solution' - Most of which don't involve banning the general public from Soldat for a week.

It's not like this hasn't happened in the past.

[$able]

No, something like that never happened in the past.

What I'm trying to make clear is that it's not BE's fault. But, oh well, you will still think it is, so I give up trying to convince you now.

[Bloo]

No, something like that never happened in the past.

What I'm trying to make clear is that it's not BE's fault. But, oh well, you will still think it is, so I give up trying to convince you now.

Er, yeah it has. And I never said it was BE's fault, I said it was yours.

Thanks, though. ^_^

[$able]

There was never a bug like this in the past.

And come on, that bug isn't my fault, blame MM or EnEsCe for it.
Fyi, it's still there, but much less likely to happen now (no real fix).

[TheToast]

Do i have to update the client/Server manually? i still get corrupted #1, and not only me.

[-Major-]

I feel so sad for Sabel right now . how come this only happens for some people? are you sure it isn't something with their ISP? or some sort of port-forwarding?

[TheToast]

I'm not blaming anyone, but obviously somewhere is a problem, so i'm just asking if there will be a solution in the next days.

[Ray]

Woot! I only got kicked for Client not responding once today! I can finally play on BE servers now >_>
For those of you that are still getting it, I guess you guys just gotta be patient and wait.

[MikeStarkweather]

If anyone is still experiencing corrupted memory kicks, have a look and see if you have Punkbuster's process resident. Should be called "PnkBstrA.exe".
Before turning it off I was getting kick banned every couple of minutes. Hasn't happened once since I got rid of PB's process.

[souljaboy88]

or it could be that your hacking or tried to hack?

[blackdevil0742]

I feel so sad for Sabel right now . how come this only happens for some people? are you sure it isn't something with their ISP? or some sort of port-forwarding?

I think it has something to do with people playing on bad servers and because Soldat's netcode is bad according to $able then maybe the worse the connection to the server the most likely it'll happen(i guess).

Bloo you're an idiot.

[SpiltCoffee]

If anyone is still experiencing corrupted memory kicks, have a look and see if you have Punkbuster's process resident. Should be called "PnkBstrA.exe".
Before turning it off I was getting kick banned every couple of minutes. Hasn't happened once since I got rid of PB's process.

Battlefield? I think I remember my friend telling me about PunkBuster running OUTSIDE of the game...

[$able]

Yes, but PunkBuster shouldn't be active while you are not playing the PB game.