Yet another Anticheat error thread.

[[BTF]Jehar]

Not for me, but for Raine (I never had any issues with anticheat one way or the other). What's odd about this case is that it's not booting her from any servers, but it's simply sitting there and locking up during the *Loading Anticheat* line. It normally takes a reboot to get out of this. Tried both r1q2 and egl; same crash.

[X'tyfe]

SEEEE!! i told you it was coming

but NOOOOOOOOOO!! no one listened to X'tyfe 

[R1CH]

Most likely some av or firewall is popping up in the background. Run in windowed mode and check, also the latest R1GL no longer forces itself on top, so if it freezes you should still be able to task switch. Other than that I'd need more details to go on, times, IPs, full Windows version, any fw/av/as software, etc.

[rainechayens]

An av (mcafee is on here btw) or firewall would be what I suspect normally, but it's only on the TS servers. So could it be the ac protocol itself isn't getting through? When tested, a whole lot of mcafee connections come up on time wait. So... time to look into the mcafee settings. BTW, xpsp2 is what's being run here.

EDIT: Turned off Mcafee, and still freezes. Another odd thing is that 2 q2 instances come up in the taskman, but still only one r1q2.exe thread.

[R1CH]

Sounds like a McAfee problem, did you try windowed mode and see if anything pops up? You should see a TCP connection to 65.75.73.66. If you give me your IP I can also check if you were able to get through to the AC server or not.

[[BTF]Jehar]

I can tell you that the ip has little to do with it; she tried it under multiple networks. Right now hers is identical to mine; 69.326.142.28. I ran it in windowed and no av stuff came up; just locked up.

EGL: Oddly enough, it works in egl.

[R1CH]

I can tell you that the ip has little to do with it; she tried it under multiple networks. Right now hers is identical to mine; 69.326.142.28. I ran it in windowed and no av stuff came up; just locked up.

EGL: Oddly enough, it works in egl.

Haven't seen a single connection from that IP since 15th September, so whatever firewall / av is running is probably blocking the connection.