[Bug 3226] New: Bots don't work properly on high timescales

bugzilla-daemon at icculus.org bugzilla-daemon at icculus.org
Wed Jun 13 10:18:03 EDT 2007


http://bugzilla.icculus.org/show_bug.cgi?id=3226

           Summary: Bots don't work properly on high timescales
           Product: Quake 3
           Version: 1.33 SVN
          Platform: All
               URL: http://svn.icculus.org/quake3?rev=870&view=rev
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P3
         Component: Misc
        AssignedTo: zakk at icculus.org
        ReportedBy: gijskruitbosch at gmail.com
         QAContact: quake3-bugzilla at icculus.org


Steps to reproduce:

1. Run ioquake3
2. Open a multiplayer server with some empty slots
3. Open the console, use /devmap Q3DM17 to load a map with a bunch of jumppads
and empty space to commit suicide in.
4. Add some bots. The skill level doesn't really matter.
5. Use "/timescale 15" in the console to increase the timescale.

Actual results:
Now everything will go really quickly. If you look at the scores (and the
output at the top-left), this will show all the bots are busy killing
themselves by jumping into the abyss.

Expected results:
The bots should fight "properly" ;-)

I looked into this for some time, and I think that the code that causes this
was committed as revision 870. Backing out the changes to sv_snapshot.c and
sv_main.c outlined in the URL field of this bug fixes the issue. I'm not
familiar enough with the ioquake3 code to figure out what would be the better
way to fix this - I'm assuming there is a better way than backing out the
patch, as I'm pretty sure there was a purpose for the patch in question... :-)

I'd like to CC Thilo, since this was his patch (as far as I can tell), but
bugzilla isn't giving me any matches for that nickname.

Useless background info on why I need a higher timescale:
I'm working on a university project where we use ioquake3 and some genetic
algorithms to evolve bots and look into co-evolution and other fun things.
Obviously running rounds faster will mean we can run experiments faster, which
means we can get more data faster, which means we get better results faster -
which is why we use the timescale directive.

If there's anything I missed in this report, please ask, and I'll try to be as
responsive as possible.


-- 
Configure bugmail: http://bugzilla.icculus.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.



More information about the quake3-bugzilla mailing list