[Open Source] Lucky's Spacebot

[UseTheForce]

i don't have vmware set up right now so i can't test it but it seems to me that hitting alt + enter would set it into windowed mode. and from there you could put the settings you want.

the problem you are having with it using that crazy high resolution and crashing is because of the way this game finds your max resolution settings. it actually tries to use the information in your monitor for this and because it's in a vm it does this all wrong.

[Darkbounded]

i don't have vmware set up right now so i can't test it but it seems to me that hitting alt + enter would set it into windowed mode. and from there you could put the settings you want.

the problem you are having with it using that crazy high resolution and crashing is because of the way this game finds your max resolution settings. it actually tries to use the information in your monitor for this and because it's in a vm it does this all wrong.

Yes but like I said I somehow managed to get inside and fix the settings after I closed it and tried to run it again, the settings again reseted on what they were, I checked now all files and they don't have the Read-Only mark, only the folders have it.... I have no clue whats going on this time

[eibtech]

Anyone have Clouds working? If so what are your settings atm? I havent done the dailies to get the comms to get the EMP yet, that's what I'm working on right now.

[ryaco]

Hey Everyone,
I’m experiencing a problem with the crewskills option in Lucky’s 5.35.247. It seems not to be selecting the missions anymore. It looks like the area longer clickable in the crewskills menu. Is anyone else having this problem?
I thought I read a post about this issue and thought it was fixed in 247. Any suggestions would be great.
Everything worked fine yesterday.
Thanks
r

[jstine]

yea, lockboxes arent working for crew skills in 247, and for some reason after i tested the game restart, the client window came back with full screen windowed instead of the smaller box, so it's not finding the play button.

also the bot can't be stopped when its running thru the daily quests, i had to do a hard restart to get it to stop, couldn't even shut it off from task manager

edit: now the client wont close at all.

[TMichael]

yea, lockboxes arent working for crew skills in 247, and for some reason after i tested the game restart, the client window came back with full screen windowed instead of the smaller box, so it's not finding the play button.

also the bot can't be stopped when its running thru the daily quests, i had to do a hard restart to get it to stop, couldn't even shut it off from task manager

edit: now the client wont close at all.

No worries, it's a problem with the latest SWToR patch, and it's on our fix it list. I've been out all day (literally, out like a light ), but I'll work on it this evening.

Per the dailies, the bot has always had issues stopping mid-mission, depending on what commands AutoIt is implementing. However, between missions you should be able to close it and restart as needed.

I thought I read a post about this issue and thought it was fixed in 247. Any suggestions would be great.

The patch included a graphics update which is affecting image recognition while not in space. What we fixed earlier was the image recognition for reading the inventory credit total, but I'm working on the crew skills fix next.

wow, what's up with vmware and 1.4 now? i have to toss the window around, or alt+enter to try to get the picture to show

@Dark and Bread: It's possible the SWToR graphics update (for shadows, not sure what else) is affecting performance on VMWare. Mine still seems to work, but I have no idea what the difference is between my VMWare/computer set up and yours.

[breadguy]

No worries, it's a problem with the latest SWToR patch, and it's on our fix it list. I've been out all day (literally, out like a light ), but I'll work on it this evening.

Per the dailies, the bot has always had issues stopping mid-mission, depending on what commands AutoIt is implementing. However, between missions you should be able to close it and restart as needed.

The patch included a graphics update which is affecting image recognition while not in space. What we fixed earlier was the image recognition for reading the inventory credit total, but I'm working on the crew skills fix next.



@Dark and Bread: It's possible the SWToR graphics update (for shadows, not sure what else) is affecting performance on VMWare. Mine still seems to work, but I have no idea what the difference is between my VMWare/computer set up and yours.

can you please post your vmware specs? i'm running 3 gigs mem, 1 proc 2 cores, vmware latest tools and vmware player free latest version, nothing else is installed except allt he default windows 7 ultimate x86 options

on a side note, a feature request: can you make the crew skill feature so that it looks for more than one specified crew mission type?

of course, priority 1 right now is getting it to work with the new patch's text/graphics

[Darkbounded]

My host is 16 gigs ram, 8core AMD FX-8150 @ 4,1GHz , Palit GTX 560Ti 2GB, 120GB SSD OCZ Agility 3, 500GB Caviar Green WD 7200RPM 64MB Cache

One VM is runing on the HDD the other on the SSD, they both have 3 GB RAM and 4 CPU cores.. was runing perfectly till today actually I am going to try with the old monitor and kill myself if that fixes my problemms..

[TMichael]

Now I see the issue. You will need VMWare Workstation for the game to run properly; VMWare Player has some issues and limitations. One good place to start looking for it would be the Digital Life Forums. Although, after reviewing that part of the forum, it might just be faster to go a different route.

on a side note, a feature request: can you make the crew skill feature so that it looks for more than one specified crew mission type?

I'll have a look at this as I go through the code.

[Darkbounded]

Now I see the issue. You will need VMWare Workstation for the game to run properly; VMWare Player has some issues and limitations. A good place to start looking for it would be the Digital Life Forums.



I'll have a look at this as I got through the code.

I am using the Workstation... brb few mins trying with the old monitor

[TMichael]

Ah, that was breadguy with the free version, so the post above should help him.

Your settings all look okay. There is one thing you might try - whenever you copy files from your computer onto your VM, they take up double the space they should because of the two part copy process. It could just be that your virtual hard drive is near capacity and a cache clearing is in order.

Beyond that, your settings look good, so I'm still stumped as to what's causing your problem. :confused:

[Darkbounded]

So when I start the client (after launcher) it shows that its starting in windowed mode but if I don't hit Alt+Enter twice to go fullscreen and windowed again the windows is still crashing (cursor freezing), if I do it then everything goes fine I am changing the settings to what I want them to be and everything is fine until I have to restart the client or it crashes or something. Now it's not even starting with settings set to medium or something but this just keeeeeps happening last night I also noticed that this config file that you told me about was empty (after I edited it I restarted the VM) and it kept being empty so I couldnt save the settings there aswell


Edit: I gave it 20 GB more space, and I also gave 5 to 10GB for Virtual memory lets see if this will do any difference (got 20-22GB free space atm so should be enough for caching)

I think that this helped logged in without problems this time, trying again

Nooooope again cursor freezed, I guess it was luck :d

I also noticed another "bug" that happened last night with the bot (R246) it had no images anywhere on it just plain text and buttons and that happened just like that, I had to make a fresh copy to fix it

[TMichael]

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?

[Darkbounded]

I am using 9 atm, but last night I was also trying with 8, and I think I had pretty much the same problems but I will try to reinstall again ....

You can also try with 9 on your rig (or with 8 on your wife's rig) that could also confirm/deny both statements above and we will compare results in few mins and I am working on 8 atm


The moment of truth lol wish me luck


I guess it worked i logged in twice already.. gonna make a clone and put 2 bots up and report back in few hours

[UseTheForce]

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?