Difference between revisions of "CPU shot misprediction"
From Worms Knowledge Base
m |
m |
||
| Line 1: | Line 1: | ||
{{ParentArticle|[[Tricks and glitches]]}} | {{ParentArticle|[[Tricks and glitches]]}} | ||
| − | {{ReplayBox| | + | {{ReplayBox|CPU-miss.WAgame|Demonstration}} |
When calculating the trajectories for projectiles (e.g. [[Bazooka]] shots) the AI players (CPU 1 to 5) use a quicker, rougher method to trace the projectile's path than used for the actual projectile. This sometimes causes the CPU players to miss - usually hit land that was closely intersecting the intended trajectory, or hit some stray pixels along the path. | When calculating the trajectories for projectiles (e.g. [[Bazooka]] shots) the AI players (CPU 1 to 5) use a quicker, rougher method to trace the projectile's path than used for the actual projectile. This sometimes causes the CPU players to miss - usually hit land that was closely intersecting the intended trajectory, or hit some stray pixels along the path. | ||
{{stub}} | {{stub}} | ||
Revision as of 14:30, 28 June 2008
(Up to Tricks and glitches)
|
W:A replay: Demonstration |
| Download · Info |
When calculating the trajectories for projectiles (e.g. Bazooka shots) the AI players (CPU 1 to 5) use a quicker, rougher method to trace the projectile's path than used for the actual projectile. This sometimes causes the CPU players to miss - usually hit land that was closely intersecting the intended trajectory, or hit some stray pixels along the path.
