BigJ62
Posts: 1800
Joined: 12/28/2002 From: Alpharetta, Georgia Status: offline
|
quote:
ORIGINAL: Andrew Brown quote:
ORIGINAL: BigJ62 Will you be using any tools to look for errors such as my editor and witpchk? Also an officially corrected Pwhex.dat file would be nice. I suspect that map corrections are not part of pry's review, but if you are aware of any errors in the stock pwhex.dat file, can you please let me know about them? I can add them to my stock map data fixes. Thanks, Andrew Unfortunately I've made corrections to my original so I can not give you a complete list. However you can d/l my editor and check for yourself. The routine looks for: 1. Checking for hexside mismatches. 2. Checking for land hexes adjacent to ocean. This is an error according Mike Wood, quote "Hello...I have noticed on some maps, that one hex will be ocean and the adjacent hex will be land. Just want to make sure you folk know that if you make a map, you must place a shore hex between an ocean hex and a land hex or the path finding routine will become very confused. Bye...Michael Wood" 3. Checking for hex type / terrain incompatibilities. 4. Checking for coastal atoll without a base/beach, most if not all Ca type hexes are base/beach hexes. It's been reported several times on the forum about troops unloading into seemingly ocean hexes only to discover that they have been mistyped as Ca.(while technically this may not be an error, everyone that I found turned out to be an error, 11 of these IIRC). One error that it does not check for is coastal behind other coastal hexes when it should have been land, not sure if it matters that much but, I have found a few of these only by looking at the map. Some of the errors the routine found can be corrected in more than one way so, that's why I was hoping for for an offically corrected version. Hope this can be of some use. Thanks
_____________________________
Witp-AE AeAi…AeAi …AeAi…Long live AeAi.
|