Here is a note that may save someone who is searching this thread later a bit of trouble: If your map loads fine in MapView 2 but looks distorted when loaded in OpenXcom.
Check your ufo: entry for that craft's map and make sure the mapDataSets: contains BLANKS before the rest of your tile sets.
good pt. For the technically minded: BLANKS.MCD contains 2 tileparts and they are automatically inserted into every missionsite's terrainset. Hence Mv2 regards them as redundant and silently accounts for them. (Those 2 tileparts are the reason that the maximum tilepartID on a Map is limited to #253 instead of Byte.MaxValue=255. That could have been treated redundantly also, btw /sigh)
The Whirligig map is one I made.
I looked more closely at the Whirligig -- nice Map! But the RMP nodes have nothing to do with what I see in the tileset ... so i don't know where you (or Mapview) got that routefile from ...
A thought that crossed my mind is that since you're on Linux the filesystem is case sensitive; iirc, Mv2 sometimes respects case sensitivity and sometimes not ... iirc I couldn't quite make my mind up as to whether or not that should be respected, since Windows filesystem typically doesn't care about the case sensitivity of paths and/or filenames ... so whether you're on Linux or Windows (or whatever) it's GoodPolicy[tm] to follow the case sensitivity conventions that the original games used -- basically use UPPER case for the relevant subdirectories and filenames/extensions.
So maybe, just maybe, you had two RMP files with the same name but in different cases that created a conflict for Mapview ...
(avoid spaces also -- in fact just use alphanumeric and underscore characters)
I mean, lots of things will work with more than that, but the original map-related resources appear to be firmly based in ASCII Uppercase characters.
have been looking through the load-routines (in Mv2) and don't see anything that's blatantly restrictive ... it pretty much assumes that user "knows what's going on" ...
I'm guessing this is not the case but would the map and route files having a dash then number before the file extension cause this problem?
I've been saving map versions like this as I work on them:
Maybe. ( see my opinion above )
So far I have not encountered the route problem again. I've been working around it by keeping a backup of the .MAP / .RMP files in a separate folder just in case I need to revert the .RMP if it corrupts.
good to hear. I figure that once you get a hang of things and follow basic conventions, Mapview will work fine for ya
If you have a .CHM helpfile reader on Linux i suggest taking an extended browse through MapView.chm .....