Page 2 of 5
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 04 May 2011, 04:11
by sofax222
More questions about .dist files !
How to generate the .dist files ?
Automaticly in starting the openkore (makeDistMap of src/Utils.pm) ?
PS: Auctually, it should be the makeDistMap of src/auto/XSTools/misc/fastutils.xs ?
So, could I delete the .dist files ?
And, how to correct the .fld files to mapping to the .dist files ?
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 04 May 2011, 11:13
by kLabMouse
sofax222 wrote:More questions about .dist files !
How to generate the .dist files ?
Automaticly in starting the openkore (makeDistMap of src/Utils.pm) ?
PS: Auctually, it should be the makeDistMap of src/auto/XSTools/misc/fastutils.xs ?
So, could I delete the .dist files ?
And, how to correct the .fld files to mapping to the .dist files ?
.dist files are generated automatically if there is none for .fld file using makeDistMap function from XSTools.
Actually .dist file contain penalty values for each point in map.
And there is an old problem with them, about bridge.
The best way it to edit them by hand. (May-be Somebody will make a tool??? )
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 04 May 2011, 11:48
by sofax222
What is the penalty value ?
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 04 May 2011, 11:51
by kLabMouse
sofax222 wrote:What is the penalty value ?
it's used by A* Algo to avoid walls.
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 04 May 2011, 22:29
by sofax222
kLabMouse wrote:sofax222 wrote:What is the penalty value ?
it's used by A* Algo to avoid walls.
Sorry, more confused !
What is "A* Algo" ?
Is there any formula or algorithm ?
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 05 May 2011, 05:11
by EternalHarvest
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 05 May 2011, 06:42
by sofax222
Wow, It is a path searching algorithm.
I will google it to find more papers for reading.
Thank you very much !
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 24 May 2011, 03:45
by setsunaseiei
Here's the hex map of mosk_dun01.dist (near NPC)
Code: Select all
196 197 198 199 200 201 202 203 204 205 206
275 14319 1431A
274 141ED 141EE
273 140B8 140B9 140BA 140BB 140BC 140BD 140BE 140BF 140C0 140C1 140C2
272 13F8C 13F8D 13F8E 13F8F 13F90 13F91 13F92 13F93 13F94 13F95 13F96
271 13E60 13E61 13E62 13E63 13E64 13E65 13E66 13E67 13E68 13E69 13E6A
270 13D34 13D35 13D36 13D37 13D38 13D39 13D3A 13D3B 13D3C 13D3D 13D3E
269 13C08 13C09 13C0A 13C0B 13C0C 13C0D 13C0E 13C0F 13C10 13C11 13C12
268 13ADC 13ADD 13ADE 13ADF 13AE0 13AE1 13AE2 13AE3 13AE4 13AE5 13AE6
267 139B0 139B1 139B2 139B3 139B4 139B5 139B6 139B7 139B8 139B9 139BA
266 13884 13885 13886 13887 13888 13889 1388A 1388B 1388C 1388D 1388E
265 13758 13759 1375A 1375B 1375C 1375D 1375E 1375F 13760 13761 13762
*The top 4 address should at the last two columns* code seems to distort the table.
NPC is at
Hexed path to 207 276 walkable.
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 24 May 2011, 12:08
by sofax222
OK, I am sorry, I don't what you mean !
1. The value of each position (coordinate) should be one byte only !
2. My original question is the routing between mosk_dun02 and mosk_dun03.
not between mosk_dun01 and mosk_dun02.
3. The .dist file is the "penalty" values of every position, the .fld file is "walkable" values of every position.
Re: Routing between mosk_dun02 and mosk_dun03
Posted: 24 May 2011, 15:01
by kLabMouse
sofax222 wrote:3. The .dist file is the "penalty" values of every position, the .fld file is "walkable" values of every position.
well. I'll try to Explain.
the .dist file is used to calculate the route. It's build automatically from .fld file.
To Edit the walkable/non-walkable area, it's better to use a tool called BrowEdit and edit the original map. then generate the .fld file.
.fld and .dist files cannot be edited. (There was an editor of .fld files in our repos, but nobody can compile it).