0 Members and 2 Guests are viewing this topic.
Quote from: SpiltCoffee on April 25, 2008, 09:23:14 amQuote from: Bloo on April 25, 2008, 06:13:20 amRubbish. 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.
Quote from: Bloo on April 25, 2008, 06:13:20 amRubbish. 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.
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.
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?
I vote that enesce shall fix the netcode instead of having sable work his ass off.
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.
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.
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?
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.
