[http://sourceforge.net/p/ufoai/bugs/1958 Item 1958] imported from sourceforge.net tracker on 2013-01-28 19:14:56

For a given map, the csv-files created by ufo2map and the debug_croute cmd comprise slightly different xy-ranges.
In order to compare the csvs for the excavation map with WinMerge, I had to adjust them a bit:

void Grid_DumpClientRoutes_f (void)
{
ipos3_t wpMins, wpMaxs;
VecToPos(map_min, wpMins);
VecToPos(map_max, wpMaxs);
wpMins[0] += 1;
wpMins[1] += 1;
wpMaxs[0] -= 3;
wpMaxs[1] -= 3;
RT_WriteCSVFiles(clMap, "ufoaiclient", wpMins, wpMaxs);
}

Of course, this is not a fix, just a workaround. But it illustrates that ufo and ufo2map have a different 'understanding' of the mins and maxs, which is potentially dangerous.

map_min and map_max are calculated in RT_GetMapSize() with a long series of boxtraces. Right before I started to look for a bug in that function, a question came to my mind:
We have the mins and maxs for every bsp (at the very beginning of the routing table) we add to a map, and we know the offset where we add it. With this data we could easily calculate the new map_mins and _maxs with a few additions.
Should be more exact and much faster.

Or did I miss something ?
===== Comments Ported from Sourceforge =====

====== geever (2008-12-25 21:06:20) ======

Doubleposted: https://sourceforge.net/tracker/index.php?func=detail&aid=2465137&group_id=157793&atid=805242

-geever