SolarStrike Software

Hi,

Anybody having problems with ks? I use rocks fastloginrevisited addon last version .Untouched as it is from download and placed in the folder. One by one my clients crash when they finish the waypoint and relog to go outside from ks instance to the ress point .
The error happens just when the 20sec wait ends and the client tries to go to char selection.
I have winxp64, quadcore 3gb 12mbcache ,4gbram1000, gt9600 and 3 hddsata for 2 clients each disk. All 6 clients go smooth at 40fps so I dont think is a lack of power. Strange error.I searched on forum but nothing conclusive, adressmemory? idk .Hope someone can bring some light. This didnt happen few months ago btw.

Thanks.

parra wrote: 3 hddsata for 2 clients each disk

You know you can run multiple clients from one installation right?

in your shortcut use this As for the problem at hand, tough one to say without being able to test it. Try loading the game from same installation see if it affects it in any way.

Normally when people suffer crashes I suguest increasing cache size but with 4gig on a win xp system you should have ample memory.

*shrugs*

There are a couple usual reasons I can think of.

• 1. You've been running it for awhile and the game crashed because of the known game memory leak. I'd say no ks script, or any script with relogs and zone changes, can run indefinately.

• 2. You don't use waitForLoadingScreen() and the relog takes longer then the wait time you specified. In this case the crash could be caused by the bot trying to access memory before the loading screen has gone. Even if you provide amply time the zone change can take longer and longer because of the above mentioned memory leak.

Hi,

Thank you for the help and comments , I wonder if I'm placing the function properly.

yrest(3000);
sendMacro("Logout();"); waitForLoadingScreen(); yrest(4*60*1000) -- wait 3m for next character to load

-- Re-initialize player
player = CPlayer.new();
settings.load();
settings.loadProfile( etc...

Lets see if works thanks.

Seeing as you are correctly using waitForLoadingScreen(), you don't need to wait another 4 minutes.

You didn't say if any of those 2 things I said was true for you. Were they?

That is all you need to relog

Hello,

Thanks for the feedback. It finally seems to work fine , I added a wait 30 sec after the logout function and now stays stable for hours. Also added a program that cleans the memory ram every minute . The 4minute wait is just to get some time for the instance to reset itself when 5min pass.I hope that can help others to solve this problem.

Thanks for all the work you guys are doing with this project, we all need you a lot.

parra wrote:added a program that cleans the memory ram every minute

What program do you use to clean memory?

hi,
It's called clean mem, it adds itself to the scheduled tasks, it can be a bit of a problem to configure because once it is installed I had to manually set the route of the program exe in the sheduled task and also add the time I want to clean the memory.It's free and can be downloaded from softonic.
Another thing I discovered , lootomatic addon affects the crashes when I add new stuff to the black list so its an important factor to have in mind.

Have fun.

Do you actually see a drop in memory use of client.exe when memcleaner runs?

Edit: I just tried it. It's unreal. Game was only using 700k mem now it's stabilized at about 200k.

I notice the memory goes up when zoning. I downloaded the portable version because I want to run it when I want to run it. I might have to see if I can find a way to run it after every zoning.Also I'll have to see if it help when memory usage has climbed to 1.4 kk.

RoM at 200k? This I gotta try.


Out of curiosity, anyone knows how is that memory cleaner working? I mean, RoM is a different process altogether, and it's simply.. shaving off 500k of it's memory usage?

tested with 2 clients. Only set it to do client.exe and every 5 minutes. The setup wizard was very easy to use.

Went from 500k and 500k to 120k and 100k

Hahaha I'm glad you liked it. Yes its brutal , makes the client reach 50mb of ram only (omg) then the clients rise again while the char moves reaching 250mb of ram after a minute when the program cuts again xD.
This will make multiboxers go wild I think . Let's see those 20 clients at the same time screenshots pls xD. I opened pandora's box ,who knows what will happen from now...

Enjoy.