[Open Source] Lucky's Spacebot

[TMichael]

TM and Phago are we packaging x86 and x64 version together now?

As it takes less than a minute, I try to copy over the latest changes and recompile once per day for x64. More often if we have a hotfix. This way the x64 unstable link on the front page stays relevant.

[TMichael]

I have to have my skew set to my latency and the mission timer skew to +10500 for Ascendancy Barrier to succeed. I kind of am using this as an example.

You should check the mission start ... it just wont work if the timer sync fails. With 5.32 timer skew had been a last ressort possibility to run a mission, but even then it has been everything else than suggested.

With 5.35 the timer sync MUST work. There is no alternative. No way around. We want it to work that way. If it works its fun. Everything else is no fun.

Agreed. If this is happening to you, chances are the start time image is being misread early. The best fix for this is to tighten up the images a little (crop and place black pixels in any negative space between primary shapes). I had the same issue with Hydrian, reading 59 and 58 as if they were 55, and this solution solved the problem.

[sejin]

Lets see if this works, This is for Zosha, its just the 45 second one timer check image, not the 40 because when I added the 45 it worked so yea. xD I still ended up failing the mission, only ran it once.


Zosha45.rar

[Cystacae]

Since currently have an ACK by TM and no NACK by any of the rest of the team and as there has been no argument against that too, I'll put the 5.35 under GPLv3 tomorrow.

So ... until then last chance to raise voice.

ACK and NACK... hmmm... I am fine with GPLv3.

[Cystacae]

Agreed. If this is happening to you, chances are the start time image is being misread early. The best fix for this is to tighten up the images a little (crop and place black pixels in any negative space between primary shapes). I had the same issue with Hydrian, reading 59 and 58 as if they were 55, and this solution solved the problem.

Do I have to get an extra image software? I only have paint. Not a difficult thing to do but shouldn't we just remove the background color and put a transparency with the image instead?

[Cystacae]

As it takes less than a minute, I try to copy over the latest changes and recompile once per day for x64. More often if we have a hotfix. This way the x64 unstable link on the front page stays relevant.

I am going to change your directory structure for you, Phago, and myself to reflect. You can just keep it all in one archive and just move the non-compiled pieces to the proper setup.

[TMichael]

Do I have to get an extra image software? I only have paint. Not a difficult thing to do but shouldn't we just remove the background color and put a transparency with the image instead?

Paint works great for pixel editing. I believe pure black (0x000000) is interpreted as transparent. Just be careful and test if you do this - I attempted to remove some of the red background from the IS mission start time images, and they were no longer recognized. It's probably best to black out image background which is already close to black in color.

What worked for Hydrian was to carefully black out some of the faded (near black) pixels that helped to distinguish the second "5" in "55".

[TMichael]

Lets see if this works, This is for Zosha, its just the 45 second one timer check image, not the 40 because when I added the 45 it worked so yea. xD I still ended up failing the mission, only ran it once.


Zosha45.rar

Thanks for the image contribution! I'll add that one to the mix, which will probably show up in the full build by tomorrow.

Per Zosha, that's one I haven't gotten around to yet, but it's now on my to do list after Drexel and Syvris.

[Cystacae]

Paint works great for pixel editing. I believe pure black (0x000000) is interpreted as transparent. Just be careful and test if you do this - I attempted to remove some of the red background from the IS mission start time images, and they were no longer recognized. It's probably best to black out image background which is already close to black in color.

What worked for Hydrian was to carefully black out some of the faded (near black) pixels that helped to distinguish the second "5" in "55".

Ok, thanks... I am also going to just have the link for the download of the unstable go to the server Phagotron trunk/current and they can use what is what from there. I will compile the x64 versions if you don't desire to TM or Phago and I will just link the x86 versions for now until I can come up with some automation way to zip up the versions on a time schedule and it will just zip both directories up.

[TMichael]

Ok, thanks... I am also going to just have the link for the download of the unstable go to the server Phagotron trunk/current and they can use what is what from there. I will compile the x64 versions if you don't desire to TM or Phago and I will just link the x86 versions for now until I can come up with some automation way to zip up the versions on a time schedule and it will just zip both directories up.

Per the x64 build, sounds great. Per the x86 build, wasn't the Phagotron/current trunk already in the first page unstable link?

EDIT

Ohhh... I see what you did there. Nevermind

[Cystacae]

Per the x64 build, sounds great. Per the x86 build, wasn't the Phagotron/current trunk already in the first page unstable link?

EDIT

Ohhh... I see what you did there. Nevermind

I eliminated our personal workspaces forcing us to work in the same folder. I also will keep the x64 link on the first page I will update it once a day if there is any updates to x86. Also Phago since we will be working together can we just names the unstable builds like Spacebot v5.35a.rar or Spacebot v5.35b.rar as psx is not just psx anymore. We are a team and we will work as a team. I am also going to go through the code and make it look good also going to add a few little additions and fixes to the current UI. Also, I am going to look into the crew skills and see about enhancing them via user submitted code and my own code.

[phagotron]

Ouch. Always a great idea to change an SVN structure instantly without warning.

[mcinsane]

Fix for Drexel

Starts at line 125:

Drexel1("1:51",False)
shield_on()
evader_off()
sleep(200)
MouseMove(600,100)
sleep(1000)
shield_off()
evader_on()

The shield_on() and shield_off() switches to fast right here and the client sometimes wont receive the key command. Its a 50/50 chance that it will work correctly...I added a 4 second gap between shield_on and shield_off and fixed the issue. I dont know if anyone else experienced this issue or if i was just the lucky guy.

[ls427]

I downloaded the version 5.34 and gave it a try, the problem I have and not sure if there is a fix for it, is that I can't do crew skills. If I have it do crew skills, the mouse just repeats the same movements, it goes to the top right, goes to the middle, then goes back to the top right, then back to the middle, and just keeps on doing this over and over and over again. Is there a way to fix this on my end?

Thanks in advance.

[Cystacae]

Ouch. Always a great idea to change an SVN structure instantly without warning.

I am sorry man... I do things immediately due to the fact I will forget. If I don't say anything right away I forget what I am to say. I can also forget what I am saying in the middle of a conversation or sometimes even what I said. I did it cause I didn't want to forget. In you I sense much anger and uncertainty...