Results 1 to 30 of 141

Thread: Investigation of AI reassessment upon reload

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #6

    Default Re: Investigation of AI reassessment upon reload

    Another avenue for testing: can we predict when the "periodic re-assessment by the AI" will happen?

    If we could, then we could remember to save only at those points (say, every 5 turns, or whatever). This would minimise the effect of the re-assessment on re-load (since the assessment would have happenned even if we didn't reload).

    Problem 1: how do we tell whether there has been a re-assessment? Using broken sieges as our best indicator for re-evaluation, how about: turn FoW off and watch the map like a hawk for broken sieges on every end-turn, log such events, including the AI involved, over a large number of reasonably long (50 turns?) campaigns, and look at statistical patterns (it will have to be statistical, because sometimes there won't be a siege in progress when the re-eval happens, and sometimes the siege won't be broken).

    Problem 2: it is quite possible be that (absent re-loads) AI re-assessment is staggered through the turns (AI#1 assesses on turns 1, 11, 21, etc; AI#2 on 2, 12, 22; ... AI#10 on 10, 20, 30 etc.) so there is never a "good" time to save. The test above should show this as separate repeating patterns for the various AIs.

    Thoughts, anyone?

    Also, we should standardise unit size as well: Britons/M/M/Normal?
    Last edited by mishad; 04-06-2005 at 16:50.
    R:TW should be patched so that AI strategy re-evaluation on loading a savegame doesn't cripple AI expansion...

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Single Sign On provided by vBSSO