Tested this since i haven’t had that problem and it’s actually a resolution bug. I’ve been playing in 800x600 and it’s been working fine. Changing to 1024x768 is always causing the obstacles and the related blockmaps to be placed on different places on the battlefield. same with 1024x600 of course.
#36 Another problem with obstacles which I don’t think is caused by obstacle.txt either (Quite likely the same resolution problem) is that objects seems to not be placed correctly inside the hexes. They’re like pushed outside the hex. Sometimes to the right sometimes to the left (Not whole hexes either it’s like a third of a hex, which makes me think it’s not a blockmap problem). The problem is probably that only the blockmap gets placed at certain hexes while the actual obstacles doesn’t get “locked” to those hexes.
As you can see here: i40.tinypic.com/2ii9vsj.jpg H3C obstacles is always placed perfectly inside each hex in the grid while VCMI obstacles is placed in between hexes and pushed outside hexes and such. This pic was taken when playing in resolution 800x600.
I’m currently checking obstacles.txt from time to time and actually I don’t think it’s that much to fix. If the bug that caused obstacles to appear on wrong terrains was fixed in changeset 789 (stating: “* possibly fixed problems with handling obstacles info”) Then I think most of obstacle.txt is correct. There’s one bug with blockmaps which can be seen in the image above and that is that the ribs there (ID:#1 in ERM help and obstacle.txt) should have one more blocked hex in the top right but that’s actually wrong even in the ERM help files. I’ll keep checking it for bugs tho.
Log number added (Zamolxis)
