Hotfix not fixed?

[Facetentacles 92]

I was playing on experimental a few days ago when they were working on the hotfix and other than the desync and rubberbanding I was just fine, not getting the BattleEye not responding bs... And I get on today, update to .43... No desync at all... Then 2 minutes in I get BE not responding and booted again. Try another server, same problem...

Is anyone having this issue still? I was under the impression it was fixed

Danke

[Irish. 4886]

Worked excellent for me all night last night for about 5 hours straight.. besides that I cannot say.

[Martmital 436]

I've lost session 5 times in the past hour.  Been right as rain for the previous 5 hours.

[byrgesen 1341]

I was playing on experimental a few days ago when they were working on the hotfix and other than the desync and rubberbanding I was just fine, not getting the BattleEye not responding bs... And I get on today, update to .43... No desync at all... Then 2 minutes in I get BE not responding and booted again. Try another server, same problem...

Is anyone having this issue still? I was under the impression it was fixed

Danke

 

Battleye errors is, 99% of the time, not caused by the game it self.

It can be caused by a corrupt BE installation on your computer, BE client not being able to connect to the master server or steam query timeout :)

 

In Arma III, the number one reason for kicks is "BE client not responding" and its caused by steam timing out for a sec, and then Be times out and you get a kick, even though steam already have reconnected.

 

Now i could be wrong, in this particular insident ofc, but BE problems and lag/desync/session lost issues, almost never have anything to do with each other.

[Facetentacles 92]

I've lost session 5 times in the past hour. Been right as rain for the previous 5 hours.

Do I just have really bad luck about logging on at the worst possible time? ;)

Anyways, computer is restarting now... I'm trying that network adapter change I saw on the forums here a couple days ago. I'll keep you posted if this actually works or not

[Facetentacles 92]

Battleye errors is, 99% of the time, not caused by the game it self.

It can be caused by a corrupt BE installation on your computer, BE client not being able to connect to the master server or steam query timeout :)

In Arma III, the number one reason for kicks is "BE client not responding" and its caused by steam timing out for a sec, and then Be times out and you get a kick, even though steam already have reconnected.

Now i could be wrong, in this particular insident ofc, but BE problems and lag/desync/session lost issues, almost never have anything to do with each other.

So should I reinstall steam? BE connection lost was the issue I was having when everyone was getting session lost a couple days ago, so I reinstalled battleeye then and it didn't fix anything... I could try reinstalling it again I suppose

This is just frustrating that it worked totally fine on experimental lol

[byrgesen 1341]

So should I reinstall steam? BE connection lost was the issue I was having when everyone was getting session lost a couple days ago, so I reinstalled battleeye then and it didn't fix anything... I could try reinstalling it again I suppose

This is just frustrating that it worked totally fine on experimental lol

 

I dont think that will solve your issue.

Ive yet to see an actual, 100% working each time, solution to the "BE not responding" message mate :(

 

I think your best bet would be to wait for a new update for BE, only go for very low ping servers and always run steam as administrator, if possible.

Perhaps manually add it to the firewall exceptions and possible anti-virus exceptions aswell, it might be blocking the communication, if it doesnt know what BE is.

At least it looks like BE is alot less prone to fuck up, when steam is granted admin rights on the PC, i rarely see this anymore at least.

 

But have a look here aswell mate, it might help you:

http://forums.bistudio.com/showthread.php?134972-BattlEye-Client-not-responding

 

EDIT:

Another helpfull thread from the steam community:

http://steamcommunity.com/app/221100/discussions/1/648816742423641272/

Edited March 23, 2014 by Byrgesen

[Facetentacles 92]

Okie dokie. I'll give those a shot. Thanks

Also, previous post about changing network adapter settings solved nothing, as well as a quick reboot afterwords (which if you change network adapter things it tells you to do) so don't bother with that if anyone else is having the issue.

I'm out of time to mess with it today as I leave for work soon. I'll just have to revisit it tomorrow when I get up and have the whole day to play around with it.

Sigh... All I wanted to do was find a leather jacket.

[nik21 287]

In Arma III, the number one reason for kicks is "BE client not responding" and its caused by steam timing out for a sec, and then Be times out and you get a kick, even though steam already have reconnected.

 

This is actually wrong, BE and Steam are 2 different things and if Steam times out, the client will be kicked with Steam ticket check failed: null or sth. The player will only see "You were kicked", "Connection with host has been lost" or similar.

 

This kick is caused by the BE Client not communicating with the server over a period of time, reason for this can be software blocking the BE Client or hardware isses (there have been problems with some routers).

[Facetentacles 92]

This kick is caused by the BE Client not communicating with the server over a period of time, reason for this can be software blocking the BE Client or hardware isses (there have been problems with some routers).

I am wondering about that. The day I downloaded the new patch was the same day I had installed a new motherboard and processor, and consequently had all new drivers obviously and new network adapters.

The only thing I can't figure out, though, is why it worked just fine on experimental but since the exp patch went to stable I had issues... Both times. Is something different or disabled with battleeye on experimental compared to stable?

[byrgesen 1341]

This is actually wrong, BE and Steam are 2 different things and if Steam times out, the client will be kicked with Steam ticket check failed: null or sth. The player will only see "You were kicked", "Connection with host has been lost" or similar.

 

This kick is caused by the BE Client not communicating with the server over a period of time, reason for this can be software blocking the BE Client or hardware isses (there have been problems with some routers).

 

Go to BI forums and read up on it mate, its connected.

I know you wil get the "Steam Ticket Check Fail", when steam times out for longer periods of time, but its been confirmed a short timeout will cause BE to timeout aswell, and they have been working on it since the Alpha of Arma III, when they started making games Steam dependable.

 

So we are both right and wrong in this matter tbh :)

 

 

I am wondering about that. The day I downloaded the new patch was the same day I had installed a new motherboard and processor, and consequently had all new drivers obviously and new network adapters.

The only thing I can't figure out, though, is why it worked just fine on experimental but since the exp patch went to stable I had issues... Both times. Is something different or disabled with battleeye on experimental compared to stable?

 

 

As far as i know, theres no difference in the BE clients from stable and experimental, at least we have no official information confirming this.

 

EDIT:

Ofc i cant find the damn threads where i got this information Nik21....

Im certain i did read it, during the early alpha of Arma III, where this problem was really bad, but ofc i cant verify it now :(

Edited March 24, 2014 by Byrgesen