Opened 10 years ago

Closed 4 years ago

#115 closed bug (fixed (in master))

Movement by mouse doesn't work very well.

Reported by: pmac Owned by:
Milestone: 3.4.0 Keywords: mouse
Cc:

Description (last modified by takkaria)

All of the following apply for uniluminated, unvisited grid points.

  • Route finding fails with magic mapping.
  • Routefinding fails for monsters otherwise targetable with 'f'/'t'.
  • Route-finding should simply cause movement in the direction of a gridpoint when a real route cannot otherwise be computed.

Change History (11)

comment:1 Changed 10 years ago by anonymous

What about replacing it with something like the A* algorithm:
http://www.policyalmanac.org/games/aStarTutorial.htm

comment:2 Changed 10 years ago by takkaria

  • Description modified (diff)
  • Milestone set to 3.0.8

comment:3 Changed 10 years ago by takkaria

  • Description modified (diff)
  • Milestone changed from 3.0.8 to 3.0.9

comment:4 Changed 10 years ago by takkaria

  • Keywords mouse added

comment:5 Changed 9 years ago by takkaria

  • Milestone changed from 3.2.0 to 3.1.0

comment:6 Changed 9 years ago by ajps

  • Description modified (diff)
  • Summary changed from Movement/targeting by mouse doesn't work very well. to Movement by mouse doesn't work very well.

Targetting with mouse should work OK now (see [759005f] (SVN r819)), altered the bug to mouse movement only.

comment:7 Changed 9 years ago by morth

A* really isn't needed for the narrow passages in Angband, a breadth first search should be fast enough on practically all machines (though A* with a really simple weight, such as distance to goal, might be worth it). It isn't really clear from the bug description that this is the problem though, maybe it simply doesn't understand the unilluminated paths are traversable.

comment:8 Changed 9 years ago by takkaria

  • Milestone changed from 3.1.0 to 3.2.0

This isn't making 3.1.

comment:9 Changed 6 years ago by takkaria

  • Status changed from new to confirmed

comment:10 Changed 5 years ago by magnate

  • Milestone changed from 4.0 to 3.5.0

Uncontroversial and suitable for V.

comment:11 Changed 4 years ago by takkaria

  • Description modified (diff)
  • Milestone changed from 3.5.0 to 3.4.0
  • Resolution set to fixed (in master)
  • Status changed from confirmed to closed

Pathfinding works a lot better now, fixed at some point in the last couple of years.

Note: See TracTickets for help on using tickets.