EQ2Bot startup dumps Game to login screen

[stafflag]

I have spoken to a few people in isxChat

Everyone seems to agree that slower systems suffer from this problem:

While EQ2Bot loads the game process is locked. If the load time exceeds about 15 seconds(?) then the client dumps the user to the login screen.


Any ideas on a workaround?


Im Running an AMD Athlon 3.0GHz chip, 2Gb RAM, Radeon X850 (256) and an SATA WD2500 hard drive on Windows XP....

 

[Pygar]

I have no workaround for this at this time.

The slowest machine I currently run eq2bot on is a p4 3.2, 1gig ram, 60gig eide laptop.

It still loads up everytime with 5-10 seconds lag.

I suspect slow disk access causes it to load slower on some systems. I would wager a guess that some anti-virus and other application software could impact the performance as well.

I've made random shot in the dark changes working with those on IRC having the problem, but without experiencing it myself, I've been unable to find a work around.

It is reasonable to believe that buy delaying the init processes further allowing for some idle game cycles between the various init sections should remedy the problem. It will take the bot longer to load initially, but by all accounts, once init is completed, there are no further issues.

The last thing to try is editing eq2bot.iss.

At line 190 change: Turbo 1000 to Turbo 10

at line 204 add an additional line Turbo 1000.

The turbo command in lavish sets how many IS processing ticks happen per frame of game time. By grossly limiting this, it may allow the init process to complete without dropping you to character select. Strangely enough, setting your in game performance profile to 'atari mode' may also help.

 

[Pygar]

Ignore my previous suggestions.

I realize now that IS is locking the thread while it pre-parses the script at runtime. While IS has your thread locked, no packets get sent back to the server and you go LD.

This is happening before the first line of code is even executed, so adjusting turbo will not affect it.

Things that would affect this are - Antivirus software, Any disk driver software.

I even suspect tortoius might affect it. For sure, do not checkout the files to your active scripts directory. if you have delete it, then do an export to that folder. I personally check out the code to a non-active folder to work on it, then do exports to the script folder to keep it clean.

Look at anything else that might be scanning that text file when its called (similar to antivirus).

 

[msboy1]

Hmm, your system is better than mine and I don't have that problem. I have two computers that are not as good as yours and I don't get dumped to the login screen, although I do get the screen freeze while eq2bot loads the UI.

AMD 2400+ with 1 gig of ram and a 9700Pro

AMD 2500+ with 1.5 gigs of ram and a 7800GS

Dell D810 Latitude with 1 gig of ram and an X600

My screen freezes for a fraction of a second when opening the IS console for the first time and for a decent amount of time when I /run eq2bot before the UI comes up. I don't think it is longer than 15 seconds though.

 

[Pygar]

Please confirm if you sitll have an issue after deleting your scripts folder and doing an SVN export to the directory, and disabling any anti-virus software you have.

It must be a export and not a copy of a checked out tree. If those little hidden .svn folders are in there, it triggers tortouis to check versions on the files.

I want to confirm that the problem still exists with these two file access barriers removed.

 

[stafflag]

I have disabled my anti-virus, deleted and exported the scripts directory from my SVN Sync directory like you asked but i am still unable to start EQ2Bot.
The Game Freezes for about 50 Seconds and then flashes what might be the Bot UI and dumps me to the login screen.

It worked one time for me a few days ago, but i have been unable to use it since...

 

[Pygar]

We had another thought...

Are you opening the console and typing run eq2bot, or are you use the /run eq2bot from inside the game?

There is very little we can do to fix this problem, on your system IS is taking 50+ seconds to read in the eq2bot script files and do pre-parsing. This basically just looks at each line for #'s and syntax, doesn't actually execute code.

The issue is IS locks the thread while it pre-parses. And while its locked no packets are sent to the server, if it takes longer than 50 seconds, then you go LD, and the script crashes cause you don't have an active character / class.

Your system should be able to run this fine. I have to suspect something is slowing down your file access / parsing of the script. I would think about any disk drivers, or software you might have installed or updated recently. You might also paste my response with a description over on the lavishsoft support forums and see if Lax has any ideas.

So far, we've successfully remedied the problem by eliminating virus scanners, and other disk driver problems.

 

[stafflag]

i open the IS console and type run eq2bot

I was Able to run the bot once today after 8 attempts... so we know it works if i can get past the load

i will start testing my system for any operating system or hardware problems i may have...

Thanks for all your input, I certainly appreciate it.