[For Free] Luckys Spacebot

[JRosePC]

I am having an issue where it just stops after doing the first space mission. Maybe it is not waiting long enough to load back into ship? If that is the case anyway to increase that?

[bk77]

I have been leveling a JK with the bot and so far had no issue with it, it's been working great.
Except for this morning. Just got to lvl 34 and started running Pakuuni.
The bot will run the mission twice, then it just stops running the mission.

Any idea what the issue might be, I was running 5.2?

[bigdawgz]

Also for drexel have noticed the bot will sometimes start befor it should and that throws the timing off from the start.Ships dont enter screen till 5 secs into mission and when the program reacts to that then its mostly a flawless mission.But somtimes it starts shooting and moving as soon as load in befor the ships are visible and throws it all out of wack.

[DjVandal]

I am having an issue where it just stops after doing the first space mission. Maybe it is not waiting long enough to load back into ship? If that is the case anyway to increase that?

try deleteing and anpacking the bot again i believe someone did this and it fixed a few pages back

[DjVandal]

Also for drexel have noticed the bot will sometimes start befor it should and that throws the timing off from the start.Ships dont enter screen till 5 secs into mission and when the program reacts to that then its mostly a flawless mission.But somtimes it starts shooting and moving as soon as load in befor the ships are visible and throws it all out of wack.

If you are running the fixed drexell then the bot shoudl always start at X:45 as it searches for 45sec.png if it isnt finding it you could try takeing a screen shot as it loads and hits the X:45 time then replace the provided picture with your own edited pic this should make you start at exactly the same point every time.

sorry long day at work if that isnt enough info ill try to explain better after a nap. Still looking at Sullust aswell but feeling blah gonna try again after some rest

[JRosePC]

try deleteing and anpacking the bot again i believe someone did this and it fixed a few pages back

Yeah I have done this a few times. no joy

[viralbug]

On my 25 Imperial Agent Jabim is great, but Sarapim is terrible, it loses most due to not being able to properly target a couple of the turrents or what have ya, it usually loses by 2, with my 41 Juggernaut Sullust is terrible, I have Lvl 5 gear and I lose everytime, it crashes into first rock at around 3:01 on timer and then gets blasted to hell long before it gets close to finish. What's wrong, any help would be appreciated. Oh and I am using v5.02

[trendkilla254]

after a while (5 wins max) on aeten it closes my swtorD:

exact same issue

[paranoid116]

Im using a x32 bit comp. I don't know if that makes a difference, But a full epic ship with converters should be able to beat the level 28 Syvis....or any but Fonder....Seems fonder is the only one I can beat. I resized, low profile, windows, screen in corner, reset. It DOES do the crew skills with no problem what-so-ever, yet space missions seems out of my reach..

[toxin86]

I just did 118-0 on Aeten. no problems whatsoever

[Orianbeter]

the ctd is an issue of bioware an occures random in the game
setting the grafiks on very low lowers the risk

[freakypreachy]

Having a strange issue. Drexel worked fine on the 4.X versions, save for a few issues with timing. When 5.0 came out with the Drexel improvements, I'd hoped it would fix the timing issues. Unfortunately, I can't tell if it did, because Drexel won't start. I mean, it will start the mission, but the bot never begins firing at the 45 second mark like it supposed to. It just never turns on once the mission has begun. I've replaced the 45 second image with my own, and it still won't start. What could have changed between 4.X and 5.X that would make the bot not recognize the start of the mission? All other missions start up and complete fine.

[Cystacae]

We are going to be working on mission stability and fixing a few missions for next patch as well as fixing dailies page. Please avoid using the dailies page as it will lock up the bot when trying to transition from the dailies to the persistent mission. As far as any other issues open config.ini and guy it completely deleting all data until it is an empty file. I changed nearly all variables from like Checkbox4 or whatever to a named variable. This was done to organize the bot as well as allow tab usage on UI for future versions. We will be using imagesearch to sync the missions better and splitting missions into sections via this system. It will allow us to remove a lot of the sync issues or atleast have a better chance to squash them as well as fixing a few more running into the rocks issues which Lucky and I discussed as to why this happens.

The running into rocks issue will randomly happen due to pixelsearch targetting and then the mission file puts the bot to sleep. This can replicate very easily and is a hard thing to combat unless we act upon it in this fashion were we can push the bot to a certain place and then hit the sleep timer. We also considered adding WASD support so that we have two individual movement functions that will allow us to counter the problem too. Big issue is that all though this will combat the problems it can also complicate the mission files. Benefit is that because these will be cut into sections and based upon timing it will be easier to identify where problems are. We haven't forgotten peeps just need more work than a simple push/reduction timer for a good amount of fixes. Hopefully through this we will eliminate the mission bugs and stabilize the bot for now and in the future.

[Cystacae]

Having a strange issue. Drexel worked fine on the 4.X versions, save for a few issues with timing. When 5.0 came out with the Drexel improvements, I'd hoped it would fix the timing issues. Unfortunately, I can't tell if it did, because Drexel won't start. I mean, it will start the mission, but the bot never begins firing at the 45 second mark like it supposed to. It just never turns on once the mission has begun. I've replaced the 45 second image with my own, and it still won't start. What could have changed between 4.X and 5.X that would make the bot not recognize the start of the mission? All other missions start up and complete fine.

To my knowledge nothing changed. Hmmm... I don't touch mission files and the mission file loads the mission all together after the crew skills are handled if any. So if it loads into the mission then it is all ready on the mission file.

[trendkilla254]

exact same issue

Any idea why it consistently closes on the 5th run? Only does this on aeten and clouds.

Sent from my SPH-D700 using Tapatalk 2