HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...
Bug #824102
Pathfinding: Fuel map does not support move cost of over 255
Start date:
Due date:
% Done:
0%
Estimated time:
Description
Split from Bug #824099.
cost_to_here[] is unsigned char array, meaning the maximum value that fits to elements is 255. Since costs placed there have +2 added, the maximum real cost is 253. This is rather low for large maps.
History
#1
Updated by Marko Lindqvist over 1 year ago
- File 0051-PF-Support-move-costs-of-bigger-than-253-in-fuel-map.patch 0051-PF-Support-move-costs-of-bigger-than-253-in-fuel-map.patch added
- Status changed from In Progress to Resolved
- Sprint/Milestone set to 2.6.1
#2
Updated by Marko Lindqvist over 1 year ago
- Status changed from Resolved to Rejected
- Assignee set to Marko Lindqvist
Only cost of one move is stored there, not cumulative.
#3
Updated by Marko Lindqvist over 1 year ago
- Status changed from Rejected to Resolved
As seen by a failing assert in a autogame, even for single amphibious move the cost can exceed 253 as "We therefore scale up the movement rates (and the corresponding movement consts) to the product of the two rates."
#4
Updated by Marko Lindqvist over 1 year ago
- Status changed from Resolved to Closed