[Open Source] Lucky's Spacebot

[Darkbounded]

I accidently restarted my router and I had to relog the clients so I'm back in the queue to wait and see if I pass the evil 22 number, but I noticed another problem, when the bot restarts (even when I start the client manually so its not a bot issue) the game window starts with the correct dimensions 1024x768 BUT the picture inside it starts with the 2560xXXXX dimensions and what I see is just a biiiiig giant character on a small window again a little resizing is fixing the problem but, the bot won't be able to restart if needed, so any ideas about this one?

Hardware failure, I don't know... the HDD is brand new like 10 days old the SSD is 3 months old so is the RAM... but I would start getting BSODs if it's a failure of RAM or HDD (happened already had one defective stick)

[eibtech]

Okay I've done a lot of research on the client crashing issues and have narrowed it down and tested and this is my researched fix and suggestion.

Open Task Manager
Under the Processes tab you should see two swtor.exe processes running
'right-click' one of the processes, go to Set Affinity
This will bring up a dialog box and will have limited options, All Processors, CPU 0... CPU 8 (assuming you have 8 core cpu)

By default windows sets All Processors, this fix has been known to fix other instabilities in other games as well.

On one of the swtor.exe processes you want to uncheck All Processors and the top half of your CPU numbered list (if you have CPU 0 and CPU 1, you will uncheck All Processors and CPU 0 == Likewise if you have CPU 0, 1, 2, 3, you will uncheck All Processors and CPU 0 and CPU 1)

On the other swtor.exe process you want to uncheck All Processors and the bottom half of your CPU numbered list (if you have CPU 0 and CPU 1, you will uncheck All Processors and CPU 1 == Likewise if you have CPU 0, 1, 2, 3, you will uncheck All Processors and CPU 2 and CPU 3)

Since SWTOR is such a large game it eats up alot of ram, so I use iobit's Game Booster to kill out any background services and put the system in game mode. These steps have drastically increased the stability of the client. Therefore no crashes in a 24 hr period when I was lucky to have lasted 25-75 rounds before unless I was sweating blood crossing my fingers.

On another note..

FEATURE REQUEST:

Until the integrated starter option works for all, we should have this as an option instead of an automatic feature, for those who would like to test the starter with their computer. Those with authenticators are unable to use this feature as they need a special randomized security key to login to their account and it's in other words unable to be automated.

[Darkbounded]

So the Mem Cleaner didn't help, it's still crashing after exactly 22 missions even that thanks to the cleaner I have around 2GB of RAM free.... its still crashing with the same error.... sometimes it says the memory could not be written other times the momory could not be read... I'll try that fix with the affinity and see if it helps

Does it matter which process has 0,1 and 2,3? I set 0 and 1 to the first process that uses more RAM and 2,3 to the other one

[UseTheForce]

how are you guys not being suspended if you're still running the bot 18+ hours a day?

don't you have to limit the hours?

[TMichael]

I accidently restarted my router and I had to relog the clients so I'm back in the queue to wait and see if I pass the evil 22 number, but I noticed another problem, when the bot restarts (even when I start the client manually so its not a bot issue) the game window starts with the correct dimensions 1024x768 BUT the picture inside it starts with the 2560xXXXX dimensions and what I see is just a biiiiig giant character on a small window again a little resizing is fixing the problem but, the bot won't be able to restart if needed, so any ideas about this one?

The humungous screen is just an issue with VMWare. When you resize it and close, the resolution should be saved for next time.

FEATURE REQUEST:

Until the integrated starter option works for all, we should have this as an option instead of an automatic feature, for those who would like to test the starter with their computer. Those with authenticators are unable to use this feature as they need a special randomized security key to login to their account and it's in other words unable to be automated.

Great advice on system optimization! I hope everyone having problems reads your post.

Per the starter, it only comes into play if the client crashes or Run Times or Session Times (coming soon) are chosen as options. So it's already optional except during crashes (which are normally not planned).

Per the authenticator issue, I can include an image check to stop repeated login attempts. Would you mind taking a screenshot of the message received when you try to login without entering a security/authenticator number and then post it here?

how are you guys not being suspended if you're still running the bot 18+ hours a day?

don't you have to limit the hours?

I do limit my hours somewhat, but mostly it's a matter of luck. If you happen to be online and botting when they check, a suspension or worse will probably be headed your way. This is purely speculative, but it does seem like the more you do on your account that's not space mission related, the less likely you are to be checked in the first place, i.e. more quests done, equipment and abilities upgraded, extra characters on the account, time spent doing anything else vs. botting, etc.

[Truestorybro]

Anyone had any problems with red screen when launching SWTOR in VMWare 9 and windows 7 32 bit? For some reason that i can't figure out my AMD Bulldozer (secondary comp) is getting that red screen but on my main comp (Intel) i have no problems what so ever with VMWare and SWTOR.

[TMichael]

Anyone had any problems with red screen when launching SWTOR in VMWare 9 and windows 7 32 bit? For some reason that i can't figure out my AMD Bulldozer (secondary comp) is getting that red screen but on my main comp (Intel) i have no problems what so ever with VMWare and SWTOR.

Patch 1.4 strikes again.

VMWare Workstation 8 seems to have less issues, but I think it comes down to the power of your rig/processor. Dark had some success changing from version 9 to version 8, so that might be worth a shot.

[Darkbounded]

The humungous screen is just an issue with VMWare. When you resize it and close, the resolution should be saved for next time.

Yea I did that, multiple times but everytime when I start it, the picture inside the window is still with incorrect dimensions the window is but not the picture....

[Truestorybro]

Yea I did that, multiple times but everytime when I start it, the picture inside the window is still with incorrect dimensions the window is but not the picture....

I'm having the same issue... it doesnt get saved. I have to press alt+enter twice to get normal dimensions when i launch SWTOR.

[Darkbounded]

I'm having the same issue... it doesnt get saved. I have to press alt+enter twice to get normal dimensions when i launch SWTOR.

True story bro

[Darkbounded]

Setting the affinity didn't work it still crashed again after 22 missions....

Ok there is one thing left that I haven't done, originally I downloaded this copy of star wars (that im using on the VMs) on the host a little over a month ago, and I just copied it inside the VMs, could this be the problem? Do I need to do a fresh download for each of them?

[Truestorybro]

Patch 1.4 strikes again.

VMWare Workstation 8 seems to have less issues, but I think it comes down to the power of your rig/processor. Dark had some success changing from version 9 to version 8, so that might be worth a shot.

Some weird shit going on my AMD computer... pressing ctrl+u the red screen goes away and i see my char at login screen but i cant see any login buttons etc. Pressing ctrl+u again i get the red screen back.

[TMichael]

I'm having the same issue... it doesnt get saved. I have to press alt+enter twice to get normal dimensions when i launch SWTOR.

True story bro

Try this:

1. Manually change the VM to your desired resolution while the game client is off.
2. Navigate to C:\Users\YourLogin\AppData\Local\SWTOR\swtor\settings and open client_settings.ini.
3. Change both native resolutions back to something reasonable, then save
4. ???
5. Profit

Let me know if this works for you.

[Darkbounded]

Try this:

1. Manually change the VM to your desired resolution while the game client is off.
2. Navigate to C:\Users\YourLogin\AppData\Local\SWTOR\swtor\settings and open client_settings.ini.
3. Change both native resolutions back to something reasonable, then save
4. ???
5. Profit

Let me know if this works for you.

That's exactly what I did, resolutions are as they should there didn't help..

I'm seeing that only ppl with AMD are having these problems someone mentioned that he has AMD and Intel system and only on his AMD is this problem... anyway... I was thinking of redownloading the game, do u think this might help? Actually I don't but... I have nothing else on mind right now

Heads up for ppl who use VM, if you set the game in compatible mode for Windows XP SP2 it the Play button will load almost instantly, altho it didn't fix my other issue, but at least it did this...

[Darkbounded]

So I reinstalled one of the VMs, AGAIN, with a totally different windows, AGAIN, and seems like the memory issue is gone, it was still at around 1,250MB memory at 20 missions, but the game still went not responding after 20 missions... it's always happening in the 20-22 missions range! Trying with an older version of Lucky, and I also redownloaded the game on one of the VMs, *crossedfingers*