Hello. I'm looking for help.
Since yesterday I get kicked every 3-5 minutes due to timeouts during ACE checks.
Can I do something against it?
Edit: Here's the screenshot
Attachment 3737

Printable View
Hello. I'm looking for help.
Since yesterday I get kicked every 3-5 minutes due to timeouts during ACE checks.
Can I do something against it?
Edit: Here's the screenshot
Attachment 3737
@SAM
Which server
IG UK
There is no lag or whatsoever going on. Just disconnect immediately without warning.
Edit: A router restart might have fixed it.
Didn't have any disconnects today.
@uenz keep me posted
It happened again randomly in the last weeks. A router restart usually fixed it and I was able to play after.
Today it happened quite frequently again.
Ooper told me to try XC_Engine, what I did. But it felt off for me. That's why I couldn't test that enough if it would fix the problem.
Allow UT in your anti-virus and fire-wall ; check for malware.
Check flood on your ip PeerBlock
Take the Google DNS
AND STOP DOWNLOAD PORN.
XC Engine has it's own frame limiter, if you use that, and remove frameratelimit in the renderer options in UnrealTournament.ini, it feels better, plus you can go over 180fps to 200fps max without being kicked.
You have to have mutate ace highperftoggle off, I turned it back on last night and the game felt horrible.
You can find out how to use it in "Framerate limiter.txt".
BTW did you install the XC_Core as well?
Quote:
-- Conformance to engine specifications:
The framerate is limited between 4 to 200, which are the minimum and
maximum ranges the level's internal update allow.
This for example prevents the game from running too fast at over 200 fps.
I'm using it now but still can't get 200 fps stable - turned highperf off and set frames to smth like 240 in the renderer. fps 200 in console says it's set to 200 but it's jumpy as hell. Sometimes even below 180.
Do you have to use compat mode or smth?
Disconnects didn't happen anymore btw.
You have to set it to a max of 200, I set it to 185-190fps. It will jump around a bit, I find it does it less if I lower the limit to the 180 area.
I don't use compattoggle.
BTW the command "fps"(the one that displays the current fps limit) resets the fps to 0, I had trouble with that at first making the fps jump all over the place, it's a bug with the command.