FBS Stuck on Sides of the Arena

[Urjak]

Anyone else ever had there FBS's get stuck along the sides on the arena (as in they keep trying to spin in the same direction even though they are pressed into the wall)? Is there anyway to prevent this?

[JoeBlo]

Increase the radius in the bindings

[Urjak]

Increase the radius in the bindings

That doesn't seem to help. If my FBS gets pushed intro a wall, he will just keep spinning the same way he is programmed to spin, even if he is spinning into the wall and not going anywhere. Is there anyway to change this?

[JoeBlo]

whats with all the odd formatting ?

FBS.py or FBSplus should get off the walls no problems if you tweak out the right transitional movement.

for FBS_1 and FBS_2 nothing can be done.

[Urjak]

whats with all the odd formatting ?

FBS.py or FBSplus should get off the walls no problems if you tweak out the right transitional movement.

I am using FBS.py. What exactly do you mean by tweak transitional movement.

[JoeBlo]

best info is in the py itself (whenever in doubt you should always look in the py's first as many provide info)

Code: [Select]

name = "FBS"
    #An AI specially made for SnS that you want to go for the opponent while spinning. (Not to be confused with FBS_1 or FBS_2, that aren't as good as this anyways :P)
    #Actually will move towards the opponent by spinning in small circles while advancing (for the math geeks out there, the path it will follow is an epicycloid)
    #Wire your bot normally, and then use the binding entries to customize your FBS. Spinspeed and Direction are the most important.
    #'spinspeed' defines how your bot will balance rotational speed and translation speed.
    #A low spinspeed will make it faster but it will spin on itself slower, and it will make wider circles while advancing.
    #A high spinspeed will make it slower but it will spin faster (=> more damage and knockback in most cases), and will move regularly.
    #'direction' will define the direction of your bot's spinning (1 is positive axis, -1 is negative axis on your LeftRight control)

[Urjak]

Already fooled with those. The issue with my bot is he has a surface that is perfectly shaped to snag on walls. What he really needs to do is reverse his spin direction after he stops being able to spin.

[Naryar]

best info is in the py itself (whenever in doubt you should always look in the py's first as many provide info)

Code: [Select]

name = "FBS"
    #An AI specially made for SnS that you want to go for the opponent while spinning. (Not to be confused with FBS_1 or FBS_2, that aren't as good as this anyways :P)
    #Actually will move towards the opponent by spinning in small circles while advancing (for the math geeks out there, the path it will follow is an epicycloid)
    #Wire your bot normally, and then use the binding entries to customize your FBS. Spinspeed and Direction are the most important.
    #'spinspeed' defines how your bot will balance rotational speed and translation speed.
    #A low spinspeed will make it faster but it will spin on itself slower, and it will make wider circles while advancing.
    #A high spinspeed will make it slower but it will spin faster (=> more damage and knockback in most cases), and will move regularly.
    #'direction' will define the direction of your bot's spinning (1 is positive axis, -1 is negative axis on your LeftRight control)

Hopefully I wrote that. And the most important thing is that it is BETTER than FBS_2.

And "many py's provide info" ? What is this ? There is barely any info on most py's.

[JoeBlo]

And "many py's provide info" ? What is this ? There is barely any info in most py's.

Yes that's out of your comments in the FBS file.. I cannot seem to find my copy of Click's Lowlag one...

And your picking on a figure of speech really, although a lot of Madiaba's provide info, Click usually puts info in his... you know yourself you write notes in yours and I do in mine..

Its always worth the look inside them though

------------

On topic..

nothing currently exists for such a thing Urjak, at least not publicly

though it could maybe, be possible with Clicks RPM Monitoring Python

[Clickbeetle]

On topic..

nothing currently exists for such a thing Urjak, at least not publicly

though it could maybe, be possible with Clicks RPM Monitoring Python

My RPM monitoring AI already does this.  If the weapon goes too long without passing the end rotation checkpoint (in other words, it is jammed), it reverses direction. 

[Urjak]

My RPM monitoring AI already does this.  If the weapon goes too long without passing the end rotation checkpoint (in other words, it is jammed), it reverses direction. 

Where is this life-saving AI of which you speak?

[JoeBlo]

to find it you must follow a series of clues, each more difficult to solve then the last... ah screw it

its in the Modifications and Designs section with the title RPM monitoring AI.

[Urjak]

to find it you must follow a series of clues, each more difficult to solve then the last... ah screw it

its in the Modifications and Designs section with the title RPM monitoring AI.

Thanks. I talked to Click about it, and he mentioned utilizing apanx's exporter. But when I downloaded it, I could not run it without some error message appearing. Is there something special I have to do to get it to work?

[JoeBlo]

.. not that I know of

you just double click then find your bot file ?

[Urjak]

.. not that I know of

you just double click then find your bot file ?

Odd... when I double click the .exe it claims that there are necessary files missing.

[JoeBlo]

I dont know.. try this.. its my copy of it.. I know it works.

https://gametechmods.com/uploads/files/Exporter.rar

if not its something to do with your computer..

[Clickbeetle]

.. not that I know of

you just double click then find your bot file ?

Odd... when I double click the .exe it claims that there are necessary files missing.

What are the files?


I remember this occurring before, and the solution is to do a Google search for the missing file(s) and put them on your computer.