So here's the deal with the problems reported with bosparser not showing the map properly:
The simulation seems to have modified its log output. Previously, you would get entries such as these for player position updates (in single player missions):
T:5255 AType:17 ID:712703 POS(138963.594,4706.224,245079.203) T:5956 AType:17 ID:712703 POS(138136.188,4704.223,246332.203) T:6672 AType:17 ID:712703 POS(137388.313,4731.542,247632.875)
But starting from some patch released around 23rd of february, these position entries are just not there anymore. That causes the map rendering to fail. It should still be possible to plot where stuff were destroyed, but the route info was used for some other stuff too such as centering the map over the approximate mission area. With route info missing the map rendering fails.
I see no new entries in startup.cfg to include position logging again. For now, bosparser seems to be able to parse hits/kills etc. OK but the map mode is plain broken until we get positional log entries back or I do some workaround to make map mode work without pos data.
Edited by Lupson, 18 May 2015 - 19:41.