[Open Source] Lucky's Spacebot

[TMichael]

maybe the difference is the operating system on the guest. i only ever got swtor working in a virtual machine using windows xp 32 bit as the guest. is that what you're using?

Yeah, he said he was using Win 7 x32. He also had it working before patch 1.4 (as it was on my wife's rig), so this is definitely something new.

It's also possible BioWare specifically did something to make it difficult to run SWToR on VMs. Hmm....

[UseTheForce]

I have some more information which might help.

My processor is an i7-2700k (Sandy Bridge), and I use VMWare Workstation 8. My wife, with a slightly older rig, is using an Intel quad core Q-something-or-other, and uses VMWare Workstation 9. While the VM and SWToR still run as expected on my rig, my wife's rig is experiencing exactly the same issues you describe.

So, we have two potential causes thus far:

1. Processor: Perhaps Sandy Bridge/Ivy Bridge tech is required to make this work now, or
2. Versions: VMWare Workstation 8 vs. VMWare Workstation 9

Which Workstation version are you currently running?

it's probably because the monitors are different. swtor uses the edid data from the monitor to determine the maximum resolution and when you're in a viirtual machine it gets it all wrong it seems.

maybe running windows xp in the guest will fix it because that operating system doesn't use edid so much if at all?

[Darkbounded]

Well I got dem both working but now when I tried to start Speedfan my host froze lol i reduced the overclock a bit now, but I think that Workstation 8 fixed the problem

[UseTheForce]

Yeah, he said he was using Win 7 x32. He also had it working before patch 1.4 (as it was on my wife's rig), so this is definitely something new.

It's also possible BioWare specifically did something to make it difficult to run SWToR on VMs. Hmm....

he also said he changed monitors? so different edid data.

maybe he can fix by switching to windows xp. also with the patch they changed the graphics i heard so maybe they made it do more edid crap.

[UseTheForce]

Well I got dem both working but now when I tried to start Speedfan my host froze lol i reduced the overclock a bit now, but I think that Workstation 8 fixed the problem

well at least we learned to stay away from workstation 9 for now.

[Darkbounded]

he also said he changed monitors? so different edid data.

maybe he can fix by switching to windows xp. also with the patch they changed the graphics i heard so maybe they made it do more edid crap.

The bot won't work on XP it needs the Aero theme + I also tried with the old monitor again and it was the same shit, so it was Workstation 9 everything is ok now, gonna try to push it to 4 bots

[TMichael]

he also said he changed monitors? so different edid data.

maybe he can fix by switching to windows xp. also with the patch they changed the graphics i heard so maybe they made it do more edid crap.

That will cause resolution/aspect ratio issues, but won't normally cause the client to freeze and crash. You're probably right about their graphics changes.

Well I got dem both working but now when I tried to start Speedfan my host froze lol i reduced the overclock a bit now, but I think that Workstation 8 fixed the problem

Great news! Well then, it looks like it's time to install Workstation 8 on the wife's rig, then reinstall the game. I'll bet back to the crew skills fix once the installation begins.

[UseTheForce]

The bot won't work on XP it needs the Aero theme + I also tried with the old monitor again and it was the same shit, so it was Workstation 9 everything is ok now, gonna try to push it to 4 bots

ok thanks, i didn't know that it doesn't work on xp.

[Darkbounded]

My third bot keeps leaving missions I tried Fondor Escort and Llanic so far wanted to do the dailies... I tried with 80 and 90 for image tolerance

Nvm 106 image tolerance fixedit


I always forget to ask, what is causing the bot to sometimes be logged out when the mission ends?


Aaaaand here we go, Kalee isnt 100% completed everytime anymore im getting something like 50-60% win ratio while till 2 days ago i had streaks like 200-5 im gonna give it more time but... the problem is that its not killing enough while 2 days ago it was completing everything like 1 min before the mission ends god why this never ends always something must be ****ed up... (I suspect that this could also be cuz my CPU is at 90-95% with 3 vms runing I stopped the 3rd to see) MOAR OVERCLOCK

[TMichael]

My third bot keeps leaving missions I tried Fondor Escort and Llanic so far wanted to do the dailies... I tried with 80 and 90 for image tolerance

Nvm 106 image tolerance fixedit


I always forget to ask, what is causing the bot to sometimes be logged out when the mission ends?


Aaaaand here we go, Kalee isnt 100% completed everytime anymore im getting something like 50-60% win ratio while till 2 days ago i had streaks like 200-5 im gonna give it more time but... the problem is that its not killing enough while 2 days ago it was completing everything like 1 min before the mission ends god why this never ends always something must be ****ed up... (I suspect that this could also be cuz my CPU is at 90-95% with 3 vms runing I stopped the 3rd to see) MOAR OVERCLOCK

The 90-95%CPU usage will definitely slow things to a crawl and affect W/L ratios. I would recommend just running two on that machine - don't risk overheating!

[Darkbounded]

Don't worry I am maniac about temperatures:P got 2x 120mm fans + big cooler with another 120mm fan on it ONLY for the CPU at 90%+ load its at around 50-51C while my "allowed" temperature by AMD is max 61C then it goes red....

Anyway it's not that it it does run a little bit better without the 3rd VM but still failing from time to time.... I'll give it more time but I had this same issue before and it was with Workstation 8 again, if I remember correctly 9 was working better for me till they ****ed it up yesterday..


Keeps failing..46/50, 44/50, 47/50..

And they are leaving on their own from the mission from time to time!!!!!!!! :@:@:@@RKQU(GTR QPFsvdbigjdsopfgjasobgsd EDIT: Increased image tolerance to 105... hopefully that will bandage it for now

Trust me this is getting really annoying -.-

[eibtech]

Okay so I have the newest build R247, been kindof waiting for the starter to start working for me What I did last night and my results this morning, below.

1) Updated the path to the launcher application in settings
2) Started Aetan Defense only as I'll wait for the new build with the crew skills fixed

This morning I awoke with the game and bot window up (so it worked) but I had 107 instances of a msgbox up the stated I could have only one instance of this application running at one time. So.. it didnt recognize the process running somehow I'm guessing. I almost thought of making a wscript that would keep the game and bot up at all times, the images and bot working on the images should keep the login. Of course we're in the middle of patching up after the client update. Ratio was 13:0 when the client crashed (so much for waking up to a couple hundred k more credits)

[Darkbounded]

Okay so I have the newest build R247, been kindof waiting for the starter to start working for me What I did last night and my results this morning, below.

1) Updated the path to the launcher application in settings
2) Started Aetan Defense only as I'll wait for the new build with the crew skills fixed

This morning I awoke with the game and bot window up (so it worked) but I had 107 instances of a msgbox up the stated I could have only one instance of this application running at one time. So.. it didnt recognize the process running somehow I'm guessing. I almost thought of making a wscript that would keep the game and bot up at all times, the images and bot working on the images should keep the login. Of course we're in the middle of patching up after the client update. Ratio was 13:0 when the client crashed (so much for waking up to a couple hundred k more credits)

Happened to me aswell few times but mostly was working, half an hour ago one of the clients turned into a transperent white color and I had some error that needed to be clicked to close the game (windows error with some code on it) but i didnt remember what it was if it happens again ill give more detailed explanation, anyway i had to manually close it then after the client was restarted by the bot, it wasnt standing on the right spot and it was all black (easily fixable with just resizing it a little bit manually) so that it can show the character and stuff and this is related to our latest issues, if it happens again ill try to give more detailed explanation

[breadguy]

this game is behaving so weird in my VMWare after patch 1.4, the login button takes like 10 seconds to go through, then the play button stays dark for another 10 or 15 seconds, but then it becomes clickable....none of these things happen in my desktop

[TMichael]

UPDATE R248 - CREW SKILLS

Changelog:

• Crew skills will now work with SWToR patch 1.4 when an Item Type Focus is selected

This latest revision is now available for download.


COMING SOON

• 24 Hour Run Time Schedule - have even more control over when your bot runs and closes

Please post if any other crew skill bugs crop up.