AI-ing (.py files, coding, nose-orienting R+D, and help)

[Conraaa]

Make sure the names the same, sometimes that is what causes it for me.

[d-lark]

There it is, I had to look in .bot but sure as , it had a space after the last number in the name! Found it, thanks for the tip

[d-lark]

Double Post.
Alright this is something I haven't seen before, the AI is a standard Rammer AI used in countless bots fine, but when applied to this particular one, the robot acts.. well, derpy, its nose is fine and it is oriented fine in the arena, but all it does is drive forward into a wall, slowly, when it starts to get counted out, it backs up quickly enough, but then again drives forward. I've searched the bindings but don't know what could be causing this problem for the particular robot, its a very simple Rammer with Forward and LeftRight controls.

Code: [Select]

    list.append(("Narrowhead","Rammer",{'invertible':True,'ThresholdSpeed':1.5,'radius':0.5,'topspeed':100,'throttle':100,'turn':30,'turnspeed':2,'weapons':(1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24)}))


[Pwnator]

Try increasing the radius.

[d-lark]

Thanks, I'd given that a go already to no avail.

What did end up working, was deleting the LeftRight Analog, replacing it again, and re-exporting it, dunno why but it worked, so hooray for that

[MassimoV]

Does anyone know of an AI which combines THZ and omnimultizone?

[Virus Bomb]

Is there anyway to AI bots using OmniInverted so that they don't have to turn around after they flip themselves over? I'm tired of fighting robots such as Drowning Pool that have to turn around to face me right after they invert themselves. I tried messing around with the nose settings so that the bot's starting position would result in the bot facing the right way right after inverting itself, but the bot then turns around and drives away from the opponent. I also tried messing around with the drive wiring but still to no avail. Anyone have any other suggestions?

anyone ever found a solution to this?

[Virus Bomb]

the inverted caster popups such as this:



Drowning Pool is pretty much just like it.

[090901]

Quick question, I'm trying to use SwitchWep.py to get a spinner to stop spinning and go to Pusher.py if the weapon breaks, how would I do this?

So is there any way to do this?

Most .pys already auto-switch to Shove/Ram tactics if their spinner breaks.

[Mr. AS]

he means .py files

[ianh05]

Looking for help AI'ing Clickbeetle's AW Hammer (ElectricHammer.py) in Ultimate Stock AW AI.

Currently I think the main problem is 'StartAngle':math.pi, because this bot uses a front caster and tips over at the start of the match I have no idea what to use as the starting angle for the weapon. Also while I'm here do ElectricHammer.py bots use a button to fire or analog?

[Badnik96]

Analog to fire. What is the problem with the bot when AI'ed?

[ianh05]

The weapon seems to get stuck under the bot so I'm not even sure if it's firing. I'm sure it has something to do with the start angle.

[Badnik96]

Is the motorid correct?

[ianh05]

Not sure, I'm using this:

    list.append(("AW hammer","ElectricHammer",{'invertible':True,'nose':math.pi*2,'radius':1,'topspeed':100,'throttle':100,'turn':100,'turnspeed':2.5,'MotorID':2,'NoChassisTime':2,'StartAngle':math.pi,'SwingTime':5,'weapons':(0,)}))

For this:
https://gametechmods.com/uploads/files/5099Bot2.rar

[Virus Bomb]

Are your weapon IDs listed in the bindings?

[Virus Bomb]

You mean the numbers? If so, then only the ones that I'd need the robot to switch tactics for if it broke (so things like static weapons were not included)

yeah.

[090901]

Well, I don't get why it matters so much to have it stop spinning when you have it set up to stop spinning after the DSL bar breaks.

[Trovaner]

The weapon IDs used by that piece of code come from the IDs that you gave in your bindings. With that in mind, there shouldn't be any reason for your bot not to switch tactics (assuming that the three IDs that you have listed are correct). On a side note, tactics deal with the movement of your bot and the AI.py deals with controlling the weapon and changing tactics as necessary.

The part that actually tells your AI to stop spinning is actually the "if self.weapons:" line found in the Tick method (in combination with the method that you posted). Once all the weapons that you listed have broken off, the condition becomes false which means that the Spin control is not triggered again.

I suspect that you are using a switch to control the weapon motor. You need to use either an analog controller or button for it to turn off when all the weapons are broken.

[Trovaner]

Assuming that you have three weapons that you want to break before switching tactics, it would look something like this "'weapons':(13,14,15)" in the bindings (exactly how you posted it). Just be sure that 13, 14, and 15 are the correct Component IDs (if you aren't already using it, Apanx made a really good tool for getting these).

If it still doesn't work, feel free to PM me the bot file and I'll take a look at it when I get the chance.