Lol another AI post

[Jet-speed]

Delving back into the world of AI'ing, having not been near it in a good few years, having a strange issue.
 
list.append(("Stuck on hold","Omni",{'nose':math.pi*2,'radius':0.1,'topspeed':100,'throttle':130,'turn':60,'turnspeed':4,'weapons':(13,14,16,17,18,19,20,21)}))
 
I've got a feeling it's a Nose value issue, but i've never encountered this before, so I don't understand it/know how to remedy it. The issue being it will very sluggishly crawl forwards, not caring for hazards/walls or other bots (I know the radius is configured to be aggressive but this isn't what I mean) and will eventually just keep driving into a wall until the countdown starts, at which point it'll back off full speed to avoid being counted out, then just continue crawling forward. My controls are configured correctly, and the bot faces the right away upon match start.
 
Other than that, just a side question for anyone who'd care to help. It's been a while (as I said) since I AI'd, and this is the first time i've done so in DSL. What does 'turn' address? It's the first time i've seen it.
 
Thanks, and apologies for another post on the vast subject that AI'ing is. :P

[JoeBlo]

Can we get some robot pics too?

[Jet-speed]

Sorry for the large size, but I figured since it's in tech support and not a showcase...

Bear in mind it started at the other end of the arena, this is about 15 seconds in. It just drove straight forward, hit the wall and continued to drive into it. The weapon spins just fine. Just found out the same issue is happening to my Rammer. Same thing, my rammer's controls are fine and there are no glaring issues with how I AI'd it; to me atleast. If you need specific pictures please do ask.

[JoeBlo]

sounds like a turning issue to me..

your motors wired as

Left Motor - Counter Clockwise (A) / Clockwise (D)
Right Motor - Clockwise (A) / Counter Clockwise (D)

Because AI will only use it one way where as users can get robots to move multiple ways..

[Jet-speed]

Checking my wiring, it's all fine. My bots that work properly use identical wiring.

[JoeBlo]

Is that the 2 motors in your robot ?

If so it can only drive straight..

[Jet-speed]

"If so" it'd only be able to turn...
     Confused now. :P That's the typical turning set up unless i'm being incredibly dumb. Obviously forward is set up like this:

And that does indeed drive it forward, just as much as my turning controls turn it for me. As does it turn it for the bots I have AI'd which don't have an issue.
     99% sure this isn't a control/wiring issue.

[JoeBlo]

oh right.. I have the two around the wrong way..

well thats what happens when im doing this between a pile of other work..

your forwards actually backwards to how most do it but it relies on how you build your chassis on the grid so no biggie there..

Try tiding up your bindings first since some stuff doesn't make sense..

Code: [Select]

list.append(("Stuck on   hold","Omni",{'nose':math.pi*2,'radius':0.1,'topspeed':100,'throttle':130,'turn':60,'turnspeed':2.5,'weapons':(1,)}))
Just try it and see if it makes any difference..

[Jet-speed]

Tried it, makes absolutely no difference. :P
 
+ Sorry for raising more questions while I still have a question to answer but:
 
1) What does 'turn' define?
2) What's the actual purpose of 'weapons'? Is that to say how many weapon components it has to lose before it enters 'ram-mode'?
 
Been a while, forgotten some stuffz.

[JoeBlo]

Look at the top of the bindings file for definitions

Weapon numbers are the ID's for what components it much loose before entering ram tactics, for a robot like yours no change is necessary so set the number to 1 (must be a base mounted component since its the first one you attach so you will never loose it)

form the pics/info you have provided I cannot come to any conclusion unless you send me over the robot to have a look at 

[Jet-speed]

Yeah, but what does it translate to in idiots terms? <-- Idiot. :P
 
Thanks for teh clear-up on Weapons.
 
Regarding the bot, i'll give it another go or two before perhaps sending you it (if it's convinient for you ofc). Already taken up enough of your time with this. :P
 
Edit: Weird. Just tried it... twice, with RED ALERT'S bindings, obviously changing the name but nothing else (not even Poker). It's still refusing to act properly, still just crawling forward and not turning. Same with my rammer.

[Jet-speed]

DP: Will just double post so you know to check it, Joe. :P
 
After multiple re-exports and redoing the bindings, both rammer and spinner are working perfectly. No idea why, no changes were made; perhaps it was just a freak thing.
 
Thanks for your help, regardless. ^^
 
Questionz though. Where would I go about downloading teh Meltybrain.py? (assuming it's downloadable. o.O)

[JoeBlo]

its actuality FBS.py that you want..

Dont get them confused though

FBS.py = Melty Brain tactics
FBS_1.py = SnS/ Sheck Spinner tactics 
FBS_2.py = SnS tactics

get the low lag versions here...

https://gametechmods.com/forums/index.php/topic,3986.msg154355.html#msg154355

[Jet-speed]

Much love. :3

[Clickbeetle]

It's hard to tell because the picture is small, but it looks like the 'i' in "LeftRight" is capitalized, like you held down Shift too long.  That would certainly cause the problem you are describing.


Glad to see you fixed it, but just for future reference.