Author Topic: AI-ing (.py files, coding, nose-orienting R+D, and help) (Read 238669 times)

G.K. · « **Reply #600 on:** May 29, 2010, 10:25:13 AM »

Go through the steps you took.

Gazea2 · « **Reply #601 on:** May 29, 2010, 10:30:47 AM »

I named the controls.
Then I moved the bot into "Team 35".
Next, I updated the teams.txt by putting a number 1 in the correct place.
After that I did the bindings using omni.py.
Finally, I went into the game and it crashed.

I've sent everything to you so that you can check it over. :)

G.K. · « **Reply #602 on:** May 29, 2010, 10:37:06 AM »

You need a comma after the 6 in the weapons entry.

Naryar · « **Reply #603 on:** May 29, 2010, 10:42:42 AM »

Are you sure the bot's name in the bot file fits exactly the bot's name in the bindings file (beware spaces) and the controls are correctly named ?

If it still doesn't works, then pray to the higher powers of RA2 it would work one day. When I AIed Ounce's ICM rebuild, it didn't work despite me having correctly wrote bindings, name, controls and EVERYTHING...

And it worked two days after being AIed.

Gazea2 · « **Reply #604 on:** May 29, 2010, 10:43:58 AM »

@Naryar - Wow, that's weird.

@G.K. - Ok, thanks. I'll do it and then send the finished bindings to you. :)

G.K. · « **Reply #605 on:** May 29, 2010, 10:44:14 AM »

Also Gazea, you need to remove the 'nose:math.pi', as well.

And I've done it, so you don't need to send me it.

Gazea2 · « **Reply #606 on:** May 29, 2010, 10:48:34 AM »

I noticed that and I've done it. Do I need to fine tune it or is it fine as it is?

G.K. · « **Reply #607 on:** May 29, 2010, 10:49:04 AM »

Feel free to fine tune it, or I can for you.

Gazea2 · « **Reply #608 on:** May 29, 2010, 02:00:16 PM »

You can fine tune it if you want. It'll probably be better that way. :P

G.K. · « **Reply #609 on:** May 31, 2010, 11:01:09 AM »

J'ai un petit issue avec a couple of rammers.

I was AI'ing them for BTTB, but they both have the same issue. After the first charge, instead of continuing to seek out and ram opponents, they just swish from side to side, only actively ramming the opponent if they make contact. I have tried Omniram.py and Rammer.py, and 2 versions of tactics.py, but all produce the same effect at different levels.

Does anybody know what is going on?

JoeBlo · « **Reply #610 on:** May 31, 2010, 11:21:19 AM »

whats the turn values like ?

G.K. · « **Reply #611 on:** May 31, 2010, 11:24:15 AM »

Well Pwn gave me one and I borrowed one from an Inf AI rammer...

Code: [Select]

    list.append(("Killdozer II","OmniRam",{'invertible':True,'topspeed':130,'throttle':130,'turnspeed':30,'turn':65,'radius':0.3,'range':99,'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,25,26)}))


    list.append(("Rusty Seringe","OmniRam",{'invertible':True,'topspeed':130,'throttle':130,'turnspeed':30,'turn':65,'radius':0.3,'range':99}))

So both 65.

Gazea2 · « **Reply #612 on:** May 31, 2010, 11:26:19 AM »

When my rammer was swishing from side to side the top speed was too high.

JoeBlo · « **Reply #613 on:** May 31, 2010, 11:27:43 AM »

An issue is the 'turnspeed':30 its massively overkill. should be about 2.5

the robot is trying to correct itself by straightening up but keeps over shooting as it turns to fast

G.K. · « **Reply #614 on:** May 31, 2010, 11:28:41 AM »

Ah ok, I'll try that.

Gazea2 · « **Reply #615 on:** May 31, 2010, 11:29:23 AM »

Ok. If that doesn't work, but it probably will work, then try my suggestion. :)

G.K. · « **Reply #616 on:** May 31, 2010, 11:34:54 AM »

It did work! Thanks a bunch Joe.

Gazea2 · « **Reply #617 on:** May 31, 2010, 11:36:09 AM »

I thought it would. Joe's help/advice always works.

JoeBlo · « **Reply #618 on:** May 31, 2010, 11:36:34 AM »

your welcome

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

30 is a turnspeed that should pretty much never be used

the default is 2.5 so always start there then tweak it out...

if the robot turns to slow bump it up to 3 or 4 (depending on the strength of the drive) but no more then 5 IMO

if it turns to fast like what you were experiencing reduce the number to 2 or 1.5

Naryar · « **Reply #619 on:** May 31, 2010, 12:07:54 PM »

30 is a decent value for 'turn', not 'turnspeed'.

My favorite is 50 turn, 3.5 turnspeed.