[Open Source] Lucky's Spacebot

[mcinsane]

Well guys, i gotta say that this bot is as awesome as easy to use
but i still have serious problem, Drexal mission is not working as well as its supposed to so i tried using one of the unstable versions but all i got was leaving the mission few seconds after it started, i tried changing image detecting thingy and i could make it work at 115 but only for first mission, then when it tried to rerun it the same error appeared
tho i have to say that it worked flawlessly with psx unstable, i mean it didnt hit the rock and shot everything easily, i would love to run for hours but cant make it work more than once

what is weird, the stable version worked very well, never quit the mission, its just not effective, loses most of times

any idea how could i resolve it?
thanks

(ofc i have windowed 1024x768 with low settings and default interface)

The issue with mission starts is a top priority at the moment. We're in the process of implementing a wider range of image sets to check against so that a wider range of monitors will detect mission starts consistently. Phago or I will post once a full set for all missions is available in the Unstable build.

So, coming soon!

I have to agree with Corran, Drexel has an issue somewhere....the beginning can be easily fixed by taking a screen shot of your own computer and cropping out the timer....easy fix....but Drexel always seems to have issues, It constantly runs into rocks and has issues switching between shield and blaster with the power conversion module. But the rocks is a big issue because it takes about 50% of your health away, which is something you need if your lower level. But it does run correctly it seems 1 out of every 4 Drexel missions it does.

I also attached my drexel image if anyone wants to give it a try...its alittle brighter than the old ones, but it fixed my issue
Also check the name if you use it....i think the original name is space_drexel45.png

[warheart209]

Does this work with 1920x1080 monitors? i always get start image failed while running swtor in 1024x768 low graphics defauly everything else. Windows basic theme.

[Cystacae]

I run the game on a 1920x1080 resolution we support HD now... so you can just put the window into 1024x768 windowed (hit the adjust button) and leave your desktop at 1920x1080 and you will be or should be fine.

[Cystacae]

So I am kind of lost here. Do any versions fully work? it seems I cannot find a version that I can let go over night, do missions and have companions collect stuff. It is either one or the other.

We test these on all our own personal systems and currently all stuff minus a few missions that still need to be updated work. However, it is hard to compensate for all the hardware configurations out there. This bot is a constant work in progress. So for me the bot works nearly 100% but then other people they have problems. I can decipher if it is just human error in operation or software setup or hardware differences. It is hard to find these out with only our own systems and us being donation only we can't devote extra resources he hire to fix it. So, we have it open source and the community also assists in fixes and testing. That is the way we operate and those are the reasons why things are not universal across the board. Plus I notice some people also using outdated versions or their own mods within it.

[phagotron]

Does this work with 1920x1080 monitors? i always get start image failed while running swtor in 1024x768 low graphics defauly everything else. Windows basic theme.

If these things fail, most cases reason is its not Aero themed desktop. So check that first and make sure the Aero service is up and running.

[phagotron]

I have to agree with Corran, Drexel has an issue somewhere....the beginning can be easily fixed by taking a screen shot of your own computer and cropping out the timer....easy fix....but Drexel always seems to have issues, It constantly runs into rocks and has issues switching between shield and blaster with the power conversion module. But the rocks is a big issue because it takes about 50% of your health away, which is something you need if your lower level. But it does run correctly it seems 1 out of every 4 Drexel missions it does.

I also attached my drexel image if anyone wants to give it a try...its alittle brighter than the old ones, but it fixed my issue
Also check the name if you use it....i think the original name is space_drexel45.png

We def could use some more samples, so if anyone takes screenshots and cuts out timers, post them!

Using the current 5.35 preview/unstable (R105m x86) Drexel usually avoids collisions, If you have collisions in the first part, check the debug output and mission timer. You will see there is a gap.
If so, your timer sync had a false positive recognition. tune down tolerance until it syncs correctly. If the mission ends early, you tuned it down too much.

[Nhuts]

Here's MHO.
You're focusing too much on synchronising with screenshots, resolutions and so on. I tested the bot very intensive by far. The key is the System-Setup. People that aren't able to play SWTOR on their 6yo machine are not able to play with the bot either. You can synchronize the mission-start as perfect as you can. If your Windows isn't set up correctly you WILL fail.
Best example for this is the Windows-Search-Index: If you're pefectly synchronised at the mission start, your client is on the same harddrive as your system and you're not using some decent SSD set up as Raid0 on your System your Windwos will scan and your SWTOR client will struggle. The bot won't, so you're desynchronized pretty soon. This case suits at least 80% of users.
So my intervention to most people here:
-Get a decent Computer that makes SWTOR runnig with 30fps at least.
-Do a System Cleanup.
-Use SWTOR on another Harddrive.
-Shut off the damn Windows Search Index.
Most of the times the Spacebot here runs "Out of the Box", but the more you cry, the more our developers here try to fix. Results are that the bot gets really overcoded and slowly looses his plug-and-play feature. Starting with Fondor. It ran perfectly since Lucky's original. Now it has to start 10-15 times before he gets the sync.
Why do i spam so much shit her? Because some are having trubles with Drexel, Pollith a.s.o.. These mission are working pretty well! My Computer isn't the strongest either, i had a lot to google. Sometimes i crash into rocks, BUT if i start to cry here i do a long-time test. My new Jedi-Toon was doing Drexel yesterday. I ran it for a huge couple of hours with a W/L 220/15. So it says for me that the Mission is working. Now he's 45 and doing Kalee. 35/1 just at this moment. I was lvling a Saboteur last week doing Pollith. W/L 180/13, bonus every time. Tried today for 15 rounds watching for bonus, misses every time(12 loss, too). SO messed up synchronisation (first rocks are proper evaded now, but rockets aren't hitting at the last ship).

So PLEASE:
Before start crying and demanding corrections here
1. check your own PC
2. do long time tests
The developers here are good guys and listen to almost everyone. (But they`re bad in filtering out requests based on lacking computer-knowledge.)

[Rogean]

Hey guys,

Been playing around with the bot for a few days now. I have been bugging Cystacae a few times in PM's but I figured it was time to make a post hehe.

I was originally having issues with having to change my tolerance to get missions to start and it not being reliable with that, but I started making my own pictures and that fixes it every time now. So I've moved on to my next issue, which is the targetting system.

When I use the bot with my Jedi Knight, the bot is constantly shooting at it's own blaster fire, since they are also red. Those of you that say the bot is running perfectly, you don't have this problem? The bot is missing objectives on certain missions because it is constantly firing at blaster fire instead of the ships.

I also have a similar problem with my Imperial Agent, which loves shooting at it's own missiles, as well as the engines of republic war ships. Both of these are causing me to fail Taspan Ambush consistently.

Those of you that don't have these issues, can I ask what type of PC you have? Video card?

I built my main PC about 2 months ago.. overclocked ivy bridge @ 4.6 ghz, nvidia gtx 680 video card, 2x SSD in Raid 0, etc it's a beast. I'm wondering if the video card settings can determine the accurateness of the targetting system though... gamma, brightness, etc?

I've tried running the bot on 2 laptops as well, all decent specs with nvidia cards in them, with generally the same result.

I saw it mentioned somewhere about compiling your own files with autoit.. does that help with the targeting at all?

And one last question.. is there a diffence between the color and capitalizations of "Yes" next to all the missions? Grey/Blue/Purple, Full caps and not, etc.

Thanks

[Nhuts]

The Taspan Ambush and the Syvris mission work only with much luck. This missions are not for EP-farming. When i start this mission he needs 10-15 attempts, even with purple equipment. While these missions are pretty hard flying "by hand", the bot isn't a perfect player either. I don't think this is your machine, its the mission itself. Farm Ezran instead, gives huge xp and with a good blaster the bonus works 100%.

[Breathofthedying]

pictures.zip

We def could use some more samples, so if anyone takes screenshots and cuts out timers, post them!

Using the current 5.35 preview/unstable (R105m x86) Drexel usually avoids collisions, If you have collisions in the first part, check the debug output and mission timer. You will see there is a gap.
If so, your timer sync had a false positive recognition. tune down tolerance until it syncs correctly. If the mission ends early, you tuned it down too much.

Ive been working on replacing most images @ 6500k temp 1920x1200 desktop

Lucky's Spacebot v5.35psx (preview R29)

System details: X64 CPU, WIN_7(X64)
RAM total:7 GB,free:3 GB, used:50 %
Desktop dimensions: 1920x1200(32bpp, 60Hz)

SWTOR Client is running with 1024x766
SWTOR Window:0,0 Win size:1040x804

On Target Time=49
Missile Delay=333
Timer Skew =+50
IMG Tolerance=108
HD Status=1
Timing override=4
Mission bonus=4
PSX OTT enabled=1
PSX DBG enabled=1
Last mission=Makem Te Assault
Win / Loss 15 / 0



Hope these help. I can Post more as I Update.

[Rogean]

The Taspan Ambush and the Syvris mission work only with much luck. This missions are not for EP-farming. When i start this mission he needs 10-15 attempts, even with purple equipment. While these missions are pretty hard flying "by hand", the bot isn't a perfect player either. I don't think this is your machine, its the mission itself. Farm Ezran instead, gives huge xp and with a good blaster the bonus works 100%.

Thanks for the reply. I'm mainly trying to get the bot working with my level 50's doing their dailies, not necessarily farming. These characters have full grade 5 purples. I'm still wondering if what I'm experiencing is normal.. are other people that say the bot works fine for them also noticing the bot routinely firing at it's own blaster fire or missiles? If not then I'd like to try and figure out and/or fix what is making this occur on my particular systems.

[Nhuts]

What i've figured out, if making dailies, better dont sit there watching. Start it and leave it alone for some hours. Of course you have to be sure that the mission works for you, but sitting there making dailies makes you crazy. The bot is flying like a complete idiot (for non-missioncoders ), but mostly gets his job done.

[Cystacae]

Hey guys,

Been playing around with the bot for a few days now. I have been bugging Cystacae a few times in PM's but I figured it was time to make a post hehe.

I was originally having issues with having to change my tolerance to get missions to start and it not being reliable with that, but I started making my own pictures and that fixes it every time now. So I've moved on to my next issue, which is the targetting system.

When I use the bot with my Jedi Knight, the bot is constantly shooting at it's own blaster fire, since they are also red. Those of you that say the bot is running perfectly, you don't have this problem? The bot is missing objectives on certain missions because it is constantly firing at blaster fire instead of the ships.

I also have a similar problem with my Imperial Agent, which loves shooting at it's own missiles, as well as the engines of republic war ships. Both of these are causing me to fail Taspan Ambush consistently.

Those of you that don't have these issues, can I ask what type of PC you have? Video card?

I built my main PC about 2 months ago.. overclocked ivy bridge @ 4.6 ghz, nvidia gtx 680 video card, 2x SSD in Raid 0, etc it's a beast. I'm wondering if the video card settings can determine the accurateness of the targetting system though... gamma, brightness, etc?

I've tried running the bot on 2 laptops as well, all decent specs with nvidia cards in them, with generally the same result.

I saw it mentioned somewhere about compiling your own files with autoit.. does that help with the targeting at all?

And one last question.. is there a diffence between the color and capitalizations of "Yes" next to all the missions? Grey/Blue/Purple, Full caps and not, etc.

Thanks

Rogean, you are more than adequate in your system. What about your OS? We develop on Windows 7 except for me which I am on Windows 8 Release Preview.

My system is a Stock Clocked AMD 8120 Bulldozer, HIS IceQ AMD 6950 2GB, 2x SSD in Raid 0 with a 500gb 7200 Hitachi just for storage, 16 GB RAM. I will be upgrading soon though to something even more. I am like Daft Punk! Bigger, Faster, Stronger!

[Cystacae]

What i've figured out, if making dailies, better dont sit there watching. Start it and leave it alone for some hours. Of course you have to be sure that the mission works for you, but sitting there making dailies makes you crazy. The bot is flying like a complete idiot (for non-missioncoders ), but mostly gets his job done.

Plus not all missions are confirmed working so if the mission doesn't work then the daily will not complete. If you mouse over the mission button it will give you more info on the mission.

[Cystacae]

Phago if you rename Impossible to Ascendancy and inside it from Impossible Sector to Ascendancy Barrier stuff it does work. They are an exact mirror... I did this and tested it... I can confirm it did work.