Xcrap help.

[Hyper]

Can someone list suggestions as to how to make Xcrap d/c me less frequently?

It just started letting me on my main comp yestersday. (Yay!)

Now it just d/c's me every one in a while. It's getting REALLY annoying though.

[MaxOff]

xtrap isn't the kind of software that comes with a config dialog/file.

But what the is concrete error? maybe its not xtrap fault.

[Hyper]

I have no idea what the problem is, since the message is in Chinese... x_x

[Ralath]

Screenshot?

(And why is the message in Chinese? ~_~)

[Hyper]

^LOL no idea.

It hasn't done it yet today... If it ever comes up again, I'll screen it.

[Horinia]

I made a post about this in the Outspark forums, but it was quickly buried so im just copying and pasting what I wrote before.

In response to the Xtrap issue, I can partially explain why so many people have problems.

Xtrap is an application that scans your memory for processes or blocks that are in use that interact with Fiesta beyone the normal sections. In every application that accesses memory blocks, there are parts that are left behind that are called garbage. This garbage in the memory is part of what you see when your game gets slow after leaving areas that are laggy, such as events or the Spider KQ if you spawn from GS.

Xtrap mistakes these garbage blocks in the memory as third party apps trying to access the game beyond the active sections at the time.

I have done my own tests on this and verified it. I can further explain if needed, but really its something the developers should have checked before initializing this application. However as in most companies, quick is more prefered then right.


Keep in mind that this is just 1 of the many collision errors that causes Xtrap to DC your game.