OK, so I've been using Tsearch for years- I'm very comfortable with it, so belive me when I say I've tried everything obvious. When I try using Tsearch to search eq2, the game freezes. This happens regardless of what settings I have- I've tried it with 'freeze game' on and off, I've tried all the options listed to speed up a search, I've tried running it in network mode, no matter what the game completely freezes. In eq1 it would get very very laggy, almost to the point of freezing, but it was still sending and reciving packets. However, with EQ2 no matter how fast I try to make my inital search, by the time the search is over I'm back at the character select screen. I've even compared the time it takes to do a search to how long I can kill the connection before the client gives up waiting- I've had searches only last 10 seconds that resulted in my being booted to character select, yet I can unplug my lan cable and the game will keep trying for almost a full min. So, is the client detecting the debug hook? I even tried lowering the priority of Tsearch and raising the priority of EQ2 (ctrl-alt-delete, right click on the process and pick 'set priority')- didn't help. I'm running Tsearch 1.6, the only thing I haven't tried is rolling back to 1.2 (the last version released by the original dev I belive).
If anyone has had sucess using Tsearch together with eq2, what version are you running, and can you think of anything I've missed to keep the connection alive while searching? Should point out, it only happens on the original search- subsequent (sp?) passes are fast enough to keep the connection open.
|