I've heard of weird issues with SWTOR running from the non-boot drive. Is there any way you can free up enough space on that SSD to try putting SWTOR there? If not maybe try ISBoxer (there's a thread on it down below) if you already haven't... It can handle multiple copies of programs better then the programs themselves can sometimes. Heck even just running one copy of a game with ISBoxer can sometimes yield better system resources (especially when you're trying to bot and you turn down settings, etc, and use ISBoxer's built in limiters, etc).
We've just pushed an update that will allow you to have more than 1 BuddyWing session on your PC if you have multiiple SWTOR clients. To make it simple, I suggest you make a folder for each account you want to bot and rename the BuddyWing.exe to a unique name. This release also have the targeting of dead mobs fixed and toons no longer interrupt their self cast heals like Introspection or Meditation.
i have a problem with running vmware and swtor on one of my computers and if you can help me solve it i will buy many licenses from you guys. the problem is that swtor gets your max resolution from your monitor's EDID information and not from your current resolution. so when i try and run it in a virtual machine with let's say 1440 by 900 resolution swtor tries to start initially at like 2560 by 1600 and crashes itself. i read that there is a way to override the EDID information but it's taking me too long to do it on my own. i have run swtor fine in a virtual machine before but that was on a different computer and even then the character was all squishy looking. so a resolution to this problem could be helpful to alot of your customers and future customers. is there any easy way to override the EDID information or specific video drivers which don't cause this problem? this computer has an amd 6950 video card and the vmware virtual machine is running windows xp 32bit
The new handling of not triggering the stuck code while waiting for healing to finish is working great.
use isboxer instead of vmware; you can run 20 swtors instead of 2 vm's lol check out this thread: http://www.thebuddyforum.com/buddy-...er-cpu-gpu-utilization-consumption-swtor.html
Thanks. The underlying problem is that BioWare patches a lot. We do have a good system for updating but stuff that used to work seems to arbitrarily stop working. We have to carry on making the bot a lot more robust.
Quick question... What sort of support does the game have for gathering (crew skills) right now? I'm assuming that if you have the correct skill the bot will go loot whatever the item is since it'll be intractable.
well i figure i can run at least 4 swtor's per physical machine with vmware but in vmware i can give each virtual machine it's own internet address which helps a lot with preventing losses if they ban/investigate by ip. so each virtual machine looks totally different in vmware. each has it's own mac, ip address, etc (i get multiple ip address from business dsl and/or multiple vpn's) i don't think i can do that with isboxer.
Unless you've got access to a business level connection of some type having a different IP via NAT doesn't do you any good. Your single "real" IP (your external IP from your router) is going to be the same no matter what you use on the inside of the NAT. You'd have to be using multiple real external IPs for that to begin to do any good.
that's why i said i use business dsl and multiple vpn's i set up each virtual machine with a different external ip address i was a major botter in SWG and they banned by ip address a lot of the time, that is why i use this setup. i don't mind losing a bot here and there but i don't want to lose 20 bots at once because of ip linkage. so i don't want to mess with isboxer if it doesn't offer me the same benefits as vmware regarding ip addresses
Having problem with running multiple. If one BuddyWing crashs, causing you to force close restart. Says the game is already being used. And no more to connect to. Restart of game doesnt fix. Have to shut down all games, all bots, start over. Looked through process's and see nothing I can shut off to fix this, to save a total restart of all bots. So something is not letting the game go when it crash's stops. I'm currently running 2 clients via innerspace/ISBoxer. Notice there is no client selector but not that big of deal cause can just start 2. Only problem I can forsee with this is when one crash's and need to restart, might forget which folder you started that bot from. Since they pick the swtor client by random (I notice most times its first swtor started but not all times). So say you name each folder swtor1 swtor2. And your windows in innerspace are swtor1 swtor2. When launch swtor1 buddywing it may connect itself to 2.
I didn't experience this when I was running 5 earlier; 1 bw lagged out and I killed it - and then I restarted it just fine We'll have to have one of the devs look into the issue