View source for Talk:EvBot

From Robowiki
Jump to navigation Jump to search

Contents

Thread titleRepliesLast modified
Evbot Version History117:39, 24 May 2014
Outperforming apc.Caan 1.0 in melee217:18, 29 November 2013
Did any one noticed the FPS drop in robocode >1.7.3.0?605:50, 19 November 2013
Giving preference in bot sampling for a given bot in the rumble client105:46, 18 November 2013

Evbot Version History

Why Cant You Make An Evbot Version History

Tmservo (talk)05:26, 24 May 2014

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:EvBot/Evbot Version History/reply.

 

Outperforming apc.Caan 1.0 in melee

For some strange reason my EvBot is drastically outperforming apc.Caan 1.0 in melee EvBot v4.5.2 stats

I find it quite strange. Why apc.Caan is so different from its neighbors? I do not have any special algorithm against a particular bot. In fact, I fire circular gun at everyone until I survive to 1on1 situation.

Any hints?

Beaming (talk)17:01, 29 November 2013

Not aware of anything in particular, but I'd suggest you try running a meleerumble-like match on your local computer involving both EvBot and apc.Caan, and watch the battle. Maybe apc.Caan is crashing or something? Not sure.

Rednaxela (talk)17:07, 29 November 2013

Looks like it get disabled right away. But how did it get to the 194th place in the melerumble with such behavior? Why my bot get an edge on it?

For example abc.Shadow and Diamond are actually under perform for this bot.

Beaming (talk)17:18, 29 November 2013
 
 

Did any one noticed the FPS drop in robocode >1.7.3.0?

I see that my FPS is much smaller for robocode newer than 1.7.3.0. It is actually as slow as 15 FPS, while in robocode v1.7.3.0 on the same machine I was getting close to 50FPS. This make graphical debug quite painful, and forces me to use old robocode 1.7.3.0 which is suboptimal, since rumbles run with 1.8.2 and 1.8.3.

Beaming (talk)18:39, 17 November 2013

What system are you running on? I know some of the OpenJDK stuff needs to have the OpenGL manually inserted into the startup scripts, and this was causing crashes on some systems so it was removed.

Skilgannon (talk)06:20, 18 November 2013

I am running Linux debian stable. Is it possible to put OpenGL back via config file edits or similar?

Beaming (talk)07:12, 18 November 2013

If you copy the robocode.sh file from 1.7.3.0 it should have the opengl arguments in it.

Skilgannon (talk)07:25, 18 November 2013

it seems that these files are identical

#!/bin/sh
pwd=`pwd`
cd "${0%/*}"
java -Xmx512M -cp libs/robocode.jar robocode.Robocode $*
cd "${pwd}"

so it something else

Beaming (talk)15:16, 18 November 2013

Check here and here. It seems that the openGL was used in 1.7.4.0, not 1.7.3.0.

Skilgannon (talk)17:45, 18 November 2013
 
 
 
 
 

Giving preference in bot sampling for a given bot in the rumble client

I am running rumble clients on several of my machines, but I would like my bot to be sampled a bit more often than the rest. Can I tweak something in my configs to achieve it, without breaking the ratings? Currently, I am most interested in meleerumble.

Beaming (talk)18:34, 17 November 2013

I don't think so. You can block other bots which are getting priority battles a lot, but that also means you won't get any battles against them. This is fine in 1v1 but in melee it isn't that good for the accuracy.

Skilgannon (talk)05:46, 18 November 2013