[Open Source] Lucky's Spacebot

[jackfrost]

Just delete or rename the old directory and start a new one... many things changed from 5.32 to 5.33 and 5.34.

I always put each into their own folder... this was a brand new download of 5.33 from the first post, when it went became stable.

[phagotron]

Hmm this maybe problematic... Also Phago I am going to try to boost the threshhold of image search past 125 as my son he still can use this version but I can and I believe it comes down to this. My system is more powerful than his and it seems with me I maxed the threshhold and it basically fixed most problems. It still has random problems that seem related but it works 8.5/10 but for my son it is 0/10 so I know that an issue is there somewhere. I will try to fix it on his system and see if I can get things rolling and perhaps this may fix it for other people. Unless the mission timer skew has anything to do with this.

8 of 10 is not that bad but still suxx. Guess with 125 tolerance it would even take the picture of your gramma for 4:20. I havent figured out what they did with the screenies, but it still seems to be possible to take them, alas with a fresh started client and with a certain pause in between. I discovered two issues with the timer pics, so 5.35 will have them ironed out. Anyway, I wont raise hope that all willl be good then. You'll get the actual unstable - no public - copy tonite for testing.

The mission skew normally is thought to be used for the gap between timer image on screen until image is identified. Usually the bots timer will run past the clients timer for some 100 ms. This may be no issue, except for some missions. If the ship consequently hits a rocket because it dives down a half second late, you skew the timer to +500. It also can be misused if your pc always recognizes 5:17 as 5:15 to skew the bot timer to +2000. It can do +-5000ms. So together with a high tolerance it might be abused to bypass the picture issues for running one mission in row.

[Cystacae]

8 of 10 is not that bad but still suxx. Guess with 125 tolerance it would even take the picture of your gramma for 4:20. I havent figured out what they did with the screenies, but it still seems to be possible to take them, alas with a fresh started client and with a certain pause in between. I discovered two issues with the timer pics, so 5.35 will have them ironed out. Anyway, I wont raise hope that all willl be good then. You'll get the actual unstable - no public - copy tonite for testing.

The mission skew normally is thought to be used for the gap between timer image on screen until image is identified. Usually the bots timer will run past the clients timer for some 100 ms. This may be no issue, except for some missions. If the ship consequently hits a rocket because it dives down a half second late, you skew the timer to +500. It also can be misused if your pc always recognizes 5:17 as 5:15 to skew the bot timer to +2000. It can do +-5000ms. So together with a high tolerance it might be abused to bypass the picture issues for running one mission in row.

Ok, I can see that could be an issue. I know I like to keep these things out in the open to discuss so that people are seeing our brainstorms. It allows people to see that we haven't forgotten about them and are trying to get this to 100% which is where I would like it. In about 2-3 weeks I will be sending your the new details on the targeting system and target painting system to add earlier into the 5.3 series and you can help me put it into a 6.0 unstable and test it. More like keeping each other in check. I have still been looking at and modifying the 5.3 series after you come out with new stuff but nothing worth posting yet. In the 6.0 unstable I will have the new UI put in. However, I am going to change crew skills prior to 6.0. I am also going to add functions for a reset to defaults button early and will continue into 6.0.

[Cystacae]

Phago I do like your coding style with the misc file. Not super clean but a ton better to interpret and find issues. Also, I am working on a few new cs files for BuddyWing so I am going to be doing that for the next few days. WingIt the combat routine manager is getting redone so I need to do this as I write the combat routine files for Assassins and Shadows. Also good news, my comp case for my bad shoulder got a court date for settlement which is what I was looking for.

[lawlwtfbot]

hey i need to ask because this is a big problem im having, the bot works fine on some missions but on about 3/4 of them after about 30 seconds into a mission it will crash my whole computer and have to reset computer, and this also happens if i ever try and set it to do the daily circut, i would really like to know how to fix this situation, also another issue that has been happening is after the bot completes 1 mission the bot program itself will freeze and no longer do the missions and i eventually log out from being idle

[Cystacae]

hey i need to ask because this is a big problem im having, the bot works fine on some missions but on about 3/4 of them after about 30 seconds into a mission it will crash my whole computer and have to reset computer, and this also happens if i ever try and set it to do the daily circut, i would really like to know how to fix this situation, also another issue that has been happening is after the bot completes 1 mission the bot program itself will freeze and no longer do the missions and i eventually log out from being idle

I am aware of this happening on certain missions when using the dailies. The other non-working missions we know are image issues with images taken when anti-aliasing is on. The crash however I have no experienced and the lockup I haven't either. This bot I have yet to see do this, not saying it isn't just haven't experienced it. I do know 5.35 is in the works to fix some more problems and add the rest of the missions with them completely updated. I am also aware of the bug in reporting successful missions and this is due to the preliminary bonus mission support.

[TNTtehbomb]

i'm havin an issue with the timer on 5.33 and 5.34, the timers for aetan doesn't seem to match up say for instance the bot says 5m 00, when in the game it is like 5m 05

[phagotron]

i'm havin an issue with the timer on 5.33 and 5.34, the timers for aetan doesn't seem to match up say for instance the bot says 5m 00, when in the game it is like 5m 05

Since 1.3 for Aetan (as well as Kalee) a false positive recognition seems to be quite likely, 5.35 will care for that. Until it is ready for unstable public, see options. You can set tolerance a bit lower, like 92 or 90 to avoid false positives. Dont set it much lower, as it might interfere with other functions then. If it still recognizes an up to 5 sec wrong time, use mission skew (-5000) to cure that. This can be done in flight too, using F5/F6.

[vapor311]

5.34 pretty much refuses to run, just seconds into every run it does nothing and aborts. Ive not found a version yet that either of the lvl 40 missions work. 5.33 and 5.31 are the same for these.

[federp]

I'm still mystified why the mission coordinates on the space map seem to be way off for me (30ish px horizontal), but everything else seems to be fine...? When I move the whole swtor window so that the mission icon lines up with where it would click, it can't find the start confirm (yes) buttun any longer, so image search location is okay again.

Could there be a difference between the coords in the mission file and misc functions? Am I the only one with this issue (if not perhaps some sort of offset option in the interface is worth considering)?

p.s. it's easy enough to fix the mission click coordinates inside the mission files. After doing that everything works just fine.

[lulwut75]

I am aware of this happening on certain missions when using the dailies. The other non-working missions we know are image issues with images taken when anti-aliasing is on. The crash however I have no experienced and the lockup I haven't either. This bot I have yet to see do this, not saying it isn't just haven't experienced it. I do know 5.35 is in the works to fix some more problems and add the rest of the missions with them completely updated. I am also aware of the bug in reporting successful missions and this is due to the preliminary bonus mission support.

Ah so this is the problem. After retesting it seems like 2/3's of the missions (repub) are done using anti-aliased images and the other 1/3 missions are not. Hopefully this gets fixed soon, as switching back and fourth for the dailies can get annoying after 3-4 runs. Thanks for the hard work!

[phagotron]

I'm still mystified why the mission coordinates on the space map seem to be way off for me (30ish px horizontal), but everything else seems to be fine...? When I move the whole swtor window so that the mission icon lines up with where it would click, it can't find the start confirm (yes) buttun any longer, so image search location is okay again.

Could there be a difference between the coords in the mission file and misc functions? Am I the only one with this issue (if not perhaps some sort of offset option in the interface is worth considering)?

p.s. it's easy enough to fix the mission click coordinates inside the mission files. After doing that everything works just fine.

Good to hear that you found a workaround. Usually Resize&Move button should fix that issue, no idea why it didnt work for you.

[Goblin21]

i'm having an issue with the timer . Any ideas ?

[lawlwtfbot]

I am aware of this happening on certain missions when using the dailies. The other non-working missions we know are image issues with images taken when anti-aliasing is on. The crash however I have no experienced and the lockup I haven't either. This bot I have yet to see do this, not saying it isn't just haven't experienced it. I do know 5.35 is in the works to fix some more problems and add the rest of the missions with them completely updated. I am also aware of the bug in reporting successful missions and this is due to the preliminary bonus mission support.

i keep trying and every time on all mission but about 2 my screen will either go black and computer will crash and restart or the screen will go pink/white/grey and just completely freeze and break pretty much, also after the first mission of the ones that do work the application itself again still breaks and freezes and i have to kill it with task manager.the bot works great and perfect on the missions it does work for but otherwise my computer is having huge problems with it, and it being a very new computer with well over needed graphics im wondering what i am doing wrong here because i would really like to get this fixed

[merock73]

Consistently getting "Logged out due to inactivity" after anywhere from 7 to 10 space mission runs. Anyone else running into this issue, or know of a fix?